{"vulnerability": "CVE-2025-3782", "sightings": [{"uuid": "901416c6-0ea9-462c-be25-8ae54a302577", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3782", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/35814", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1aPoC for CVE-2025-2011 - SQLi in Depicter plugin <= 3.6.1\nURL\uff1ahttps://github.com/datagoboom/CVE-2025-3782\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-05-06T20:18:23.000000Z"}, {"uuid": "19f1d80f-59c8-4a79-818b-970a659fe275", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15486", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37823\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too\n\nSimilarly to the previous patch, we need to safe guard hfsc_dequeue()\ntoo. But for this one, we don't have a reliable reproducer.\n\ud83d\udccf Published: 2025-05-08T06:26:16.839Z\n\ud83d\udccf Modified: 2025-05-08T06:26:16.839Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/68f256305ceb426d545a0dc31f83c2ab1d211a1e\n2. https://git.kernel.org/stable/c/2f46d14919c39528c6e540ebc43f90055993eedc\n3. https://git.kernel.org/stable/c/da7936518996d290e2fcfcaf6cd7e15bfd87804a\n4. https://git.kernel.org/stable/c/11bccb054c1462fb069219f8e98e97a5a730758e\n5. https://git.kernel.org/stable/c/76c4c22c2437d3d3880efc0f62eca06ef078d290\n6. https://git.kernel.org/stable/c/c6f035044104c6ff656f4565cd22938dc892528c\n7. https://git.kernel.org/stable/c/c6936266f8bf98a53f28ef9a820e6a501e946d09\n8. https://git.kernel.org/stable/c/6ccbda44e2cc3d26fd22af54c650d6d5d801addf", "creation_timestamp": "2025-05-08T07:23:11.000000Z"}, {"uuid": "67dbbe53-6913-4f88-9f5f-dc3d2f5350d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37828", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15483", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37828\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: mcq: Add NULL check in ufshcd_mcq_abort()\n\nA race can occur between the MCQ completion path and the abort handler:\nonce a request completes, __blk_mq_free_request() sets rq->mq_hctx to\nNULL, meaning the subsequent ufshcd_mcq_req_to_hwq() call in\nufshcd_mcq_abort() can return a NULL pointer. If this NULL pointer is\ndereferenced, the kernel will crash.\n\nAdd a NULL check for the returned hwq pointer. If hwq is NULL, log an\nerror and return FAILED, preventing a potential NULL-pointer\ndereference.  As suggested by Bart, the ufshcd_cmd_inflight() check is\nremoved.\n\nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix\nufshcd_abort_one racing issue\").\n\nThis is found by our static analysis tool KNighter.\n\ud83d\udccf Published: 2025-05-08T06:26:20.135Z\n\ud83d\udccf Modified: 2025-05-08T06:26:20.135Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d6979fabe812a168d5053e5a41d5a2e9b8afd7bf\n2. https://git.kernel.org/stable/c/7d002f591486f5ef4bc02eb02025a53f931f0eb5\n3. https://git.kernel.org/stable/c/47eec518aef3814f64a5da43df81bdd74d8c0041\n4. https://git.kernel.org/stable/c/4c324085062919d4e21c69e5e78456dcec0052fe", "creation_timestamp": "2025-05-08T07:23:08.000000Z"}, {"uuid": "c7f8631f-7e16-4884-a0c3-5c809f7768b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37829", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15482", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37829\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: scpi: Fix null-ptr-deref in scpi_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy->cpus mask. scpi_cpufreq_get_rate() does not check for\nthis case, which results in a NULL pointer dereference.\n\ud83d\udccf Published: 2025-05-08T06:26:21.061Z\n\ud83d\udccf Modified: 2025-05-08T06:26:21.061Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ad4796f2da495b2cbbd0fccccbcbf63f2aeee613\n2. https://git.kernel.org/stable/c/fdf035d9c5436536ffcfea0ac6adeb5dda3c3a23\n3. https://git.kernel.org/stable/c/8fbaa76690f67a7cbad315f89d607b46e3e06ede\n4. https://git.kernel.org/stable/c/da8ee91e532486055ecf88478d38c2f3dc234182\n5. https://git.kernel.org/stable/c/19e0eaa62e8831f2bc0285fef3bf8faaa7f3e09b\n6. https://git.kernel.org/stable/c/28fbd7b13b4d3074b16db913aedc9d8d37ab41e7\n7. https://git.kernel.org/stable/c/124bddf123311cd1f18bffd63a5d974468d59c67\n8. https://git.kernel.org/stable/c/73b24dc731731edf762f9454552cb3a5b7224949", "creation_timestamp": "2025-05-08T07:23:07.000000Z"}, {"uuid": "edb823a0-89e4-4a7b-8ff4-28dcc0e59370", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37821", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15488", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37821\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsched/eevdf: Fix se->slice being set to U64_MAX and resulting crash\n\nThere is a code path in dequeue_entities() that can set the slice of a\nsched_entity to U64_MAX, which sometimes results in a crash.\n\nThe offending case is when dequeue_entities() is called to dequeue a\ndelayed group entity, and then the entity's parent's dequeue is delayed.\nIn that case:\n\n1. In the if (entity_is_task(se)) else block at the beginning of\n   dequeue_entities(), slice is set to\n   cfs_rq_min_slice(group_cfs_rq(se)). If the entity was delayed, then\n   it has no queued tasks, so cfs_rq_min_slice() returns U64_MAX.\n2. The first for_each_sched_entity() loop dequeues the entity.\n3. If the entity was its parent's only child, then the next iteration\n   tries to dequeue the parent.\n4. If the parent's dequeue needs to be delayed, then it breaks from the\n   first for_each_sched_entity() loop _without updating slice_.\n5. The second for_each_sched_entity() loop sets the parent's ->slice to\n   the saved slice, which is still U64_MAX.\n\nThis throws off subsequent calculations with potentially catastrophic\nresults. A manifestation we saw in production was:\n\n6. In update_entity_lag(), se->slice is used to calculate limit, which\n   ends up as a huge negative number.\n7. limit is used in se->vlag = clamp(vlag, -limit, limit). Because limit\n   is negative, vlag > limit, so se->vlag is set to the same huge\n   negative number.\n8. In place_entity(), se->vlag is scaled, which overflows and results in\n   another huge (positive or negative) number.\n9. The adjusted lag is subtracted from se->vruntime, which increases or\n   decreases se->vruntime by a huge number.\n10. pick_eevdf() calls entity_eligible()/vruntime_eligible(), which\n    incorrectly returns false because the vruntime is so far from the\n    other vruntimes on the queue, causing the\n    (vruntime - cfs_rq->min_vruntime) * load calulation to overflow.\n11. Nothing appears to be eligible, so pick_eevdf() returns NULL.\n12. pick_next_entity() tries to dereference the return value of\n    pick_eevdf() and crashes.\n\nDumping the cfs_rq states from the core dumps with drgn showed tell-tale\nhuge vruntime ranges and bogus vlag values, and I also traced se->slice\nbeing set to U64_MAX on live systems (which was usually \"benign\" since\nthe rest of the runqueue needed to be in a particular state to crash).\n\nFix it in dequeue_entities() by always setting slice from the first\nnon-empty cfs_rq.\n\ud83d\udccf Published: 2025-05-08T06:26:15.535Z\n\ud83d\udccf Modified: 2025-05-08T06:26:15.535Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/50a665496881262519f115f1bfe5822f30580eb0\n2. https://git.kernel.org/stable/c/bbce3de72be56e4b5f68924b7da9630cc89aa1a8", "creation_timestamp": "2025-05-08T07:23:13.000000Z"}, {"uuid": "0f5f4104-e3d7-484b-8a14-4640331c12f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37822", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15487", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37822\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: uprobes: Add missing fence.i after building the XOL buffer\n\nThe XOL (execute out-of-line) buffer is used to single-step the\nreplaced instruction(s) for uprobes. The RISC-V port was missing a\nproper fence.i (i$ flushing) after constructing the XOL buffer, which\ncan result in incorrect execution of stale/broken instructions.\n\nThis was found running the BPF selftests \"test_progs:\nuprobe_autoattach, attach_probe\" on the Spacemit K1/X60, where the\nuprobes tests randomly blew up.\n\ud83d\udccf Published: 2025-05-08T06:26:16.209Z\n\ud83d\udccf Modified: 2025-05-08T06:26:16.209Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/bcf6d3158c5902d92b6d62335af4422b7bf7c4e2\n2. https://git.kernel.org/stable/c/1dbb95a36499374c51b47ee8ae258a8862c20978\n3. https://git.kernel.org/stable/c/7d1d19a11cfbfd8bae1d89cc010b2cc397cd0c48", "creation_timestamp": "2025-05-08T07:23:12.000000Z"}, {"uuid": "6783f321-3956-4649-94f0-77e8c71b0198", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37825", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15485", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37825\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix out-of-bounds access in nvmet_enable_port\n\nWhen trying to enable a port that has no transport configured yet,\nnvmet_enable_port() uses NVMF_TRTYPE_MAX (255) to query the transports\narray, causing an out-of-bounds access:\n\n[  106.058694] BUG: KASAN: global-out-of-bounds in nvmet_enable_port+0x42/0x1da\n[  106.058719] Read of size 8 at addr ffffffff89dafa58 by task ln/632\n[...]\n[  106.076026] nvmet: transport type 255 not supported\n\nSince commit 200adac75888, NVMF_TRTYPE_MAX is the default state as configured by\nnvmet_ports_make().\nAvoid this by checking for NVMF_TRTYPE_MAX before proceeding.\n\ud83d\udccf Published: 2025-05-08T06:26:18.094Z\n\ud83d\udccf Modified: 2025-05-08T06:26:18.094Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/83c00860a37b3fcba8026cb344101f1b8af547cf\n2. https://git.kernel.org/stable/c/3d7aa0c7b4e96cd460826d932e44710cdeb3378b", "creation_timestamp": "2025-05-08T07:23:10.000000Z"}, {"uuid": "6c3d425f-ff56-4d6d-90c2-932016b6d586", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37826", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15484", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37826\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: Add NULL check in ufshcd_mcq_compl_pending_transfer()\n\nAdd a NULL check for the returned hwq pointer by ufshcd_mcq_req_to_hwq().\n\nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix\nufshcd_abort_one racing issue\").\n\ud83d\udccf Published: 2025-05-08T06:26:18.694Z\n\ud83d\udccf Modified: 2025-05-08T06:26:18.694Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/eeab6618037be84e438e9d6ed5d9a53502faf81f\n2. https://git.kernel.org/stable/c/700128d67d57bb1de4251e563ab85202def36c50\n3. https://git.kernel.org/stable/c/08a966a917fe3d92150fa3cc15793ad5e57051eb", "creation_timestamp": "2025-05-08T07:23:09.000000Z"}, {"uuid": "f1f53f49-9639-4f6d-8ee5-67f9c73f44b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37820", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15489", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37820\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nxen-netfront: handle NULL returned by xdp_convert_buff_to_frame()\n\nThe function xdp_convert_buff_to_frame() may return NULL if it fails\nto correctly convert the XDP buffer into an XDP frame due to memory\nconstraints, internal errors, or invalid data. Failing to check for NULL\nmay lead to a NULL pointer dereference if the result is used later in\nprocessing, potentially causing crashes, data corruption, or undefined\nbehavior.\n\nOn XDP redirect failure, the associated page must be released explicitly\nif it was previously retained via get_page(). Failing to do so may result\nin a memory leak, as the pages reference count is not decremented.\n\ud83d\udccf Published: 2025-05-08T06:26:14.602Z\n\ud83d\udccf Modified: 2025-05-08T06:26:14.602Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/5b83d30c63f9964acb1bc63eb8e670b9e0d2c240\n2. https://git.kernel.org/stable/c/cefd8a2e2de46209ce66e6d30c237eb59b6c5bfa\n3. https://git.kernel.org/stable/c/d6a9c4e6f9b3ec3ad98468c950ad214af8a2efb9\n4. https://git.kernel.org/stable/c/eefccd889df3b49d92e7349d94c4aa7e1ba19f6c\n5. https://git.kernel.org/stable/c/cc3628dcd851ddd8d418bf0c897024b4621ddc92", "creation_timestamp": "2025-05-08T07:23:14.000000Z"}, {"uuid": "2a45e28a-d2b2-4dbc-b64e-af1e6eb20e95", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://t.me/cvedetector/24803", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37826 - Linux Kernel UFS SCSI Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37826 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: ufs: core: Add NULL check in ufshcd_mcq_compl_pending_transfer()  \n  \nAdd a NULL check for the returned hwq pointer by ufshcd_mcq_req_to_hwq().  \n  \nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix  \nufshcd_abort_one racing issue\"). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:01.000000Z"}, {"uuid": "fc94ef0e-8b1a-4339-ab66-f9f3e8a4cff2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37821", "type": "seen", "source": "https://t.me/cvedetector/24798", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37821 - Linux Kernel Sched Eevdf Crash\", \n  \"Content\": \"CVE ID : CVE-2025-37821 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsched/eevdf: Fix se->slice being set to U64_MAX and resulting crash  \n  \nThere is a code path in dequeue_entities() that can set the slice of a  \nsched_entity to U64_MAX, which sometimes results in a crash.  \n  \nThe offending case is when dequeue_entities() is called to dequeue a  \ndelayed group entity, and then the entity's parent's dequeue is delayed.  \nIn that case:  \n  \n1. In the if (entity_is_task(se)) else block at the beginning of  \n   dequeue_entities(), slice is set to  \n   cfs_rq_min_slice(group_cfs_rq(se)). If the entity was delayed, then  \n   it has no queued tasks, so cfs_rq_min_slice() returns U64_MAX.  \n2. The first for_each_sched_entity() loop dequeues the entity.  \n3. If the entity was its parent's only child, then the next iteration  \n   tries to dequeue the parent.  \n4. If the parent's dequeue needs to be delayed, then it breaks from the  \n   first for_each_sched_entity() loop _without updating slice_.  \n5. The second for_each_sched_entity() loop sets the parent's ->slice to  \n   the saved slice, which is still U64_MAX.  \n  \nThis throws off subsequent calculations with potentially catastrophic  \nresults. A manifestation we saw in production was:  \n  \n6. In update_entity_lag(), se->slice is used to calculate limit, which  \n   ends up as a huge negative number.  \n7. limit is used in se->vlag = clamp(vlag, -limit, limit). Because limit  \n   is negative, vlag > limit, so se->vlag is set to the same huge  \n   negative number.  \n8. In place_entity(), se->vlag is scaled, which overflows and results in  \n   another huge (positive or negative) number.  \n9. The adjusted lag is subtracted from se->vruntime, which increases or  \n   decreases se->vruntime by a huge number.  \n10. pick_eevdf() calls entity_eligible()/vruntime_eligible(), which  \n    incorrectly returns false because the vruntime is so far from the  \n    other vruntimes on the queue, causing the  \n    (vruntime - cfs_rq->min_vruntime) * load calulation to overflow.  \n11. Nothing appears to be eligible, so pick_eevdf() returns NULL.  \n12. pick_next_entity() tries to dereference the return value of  \n    pick_eevdf() and crashes.  \n  \nDumping the cfs_rq states from the core dumps with drgn showed tell-tale  \nhuge vruntime ranges and bogus vlag values, and I also traced se->slice  \nbeing set to U64_MAX on live systems (which was usually \"benign\" since  \nthe rest of the runqueue needed to be in a particular state to crash).  \n  \nFix it in dequeue_entities() by always setting slice from the first  \nnon-empty cfs_rq. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:53.000000Z"}, {"uuid": "7df2eb40-4bbe-4123-ba03-064428c171b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://t.me/cvedetector/24799", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37822 - RISC-V Linux Kernel Uprobes Fence Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37822 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nriscv: uprobes: Add missing fence.i after building the XOL buffer  \n  \nThe XOL (execute out-of-line) buffer is used to single-step the  \nreplaced instruction(s) for uprobes. The RISC-V port was missing a  \nproper fence.i (i$ flushing) after constructing the XOL buffer, which  \ncan result in incorrect execution of stale/broken instructions.  \n  \nThis was found running the BPF selftests \"test_progs:  \nuprobe_autoattach, attach_probe\" on the Spacemit K1/X60, where the  \nuprobes tests randomly blew up. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:54.000000Z"}, {"uuid": "a28dc8bd-5f26-417f-b1fe-4d98cffc0e42", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37825", "type": "seen", "source": "https://t.me/cvedetector/24802", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37825 - \"Nvidia Nvmet Out-of-Bounds Access Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37825 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvmet: fix out-of-bounds access in nvmet_enable_port  \n  \nWhen trying to enable a port that has no transport configured yet,  \nnvmet_enable_port() uses NVMF_TRTYPE_MAX (255) to query the transports  \narray, causing an out-of-bounds access:  \n  \n[  106.058694] BUG: KASAN: global-out-of-bounds in nvmet_enable_port+0x42/0x1da  \n[  106.058719] Read of size 8 at addr ffffffff89dafa58 by task ln/632  \n[...]  \n[  106.076026] nvmet: transport type 255 not supported  \n  \nSince commit 200adac75888, NVMF_TRTYPE_MAX is the default state as configured by  \nnvmet_ports_make().  \nAvoid this by checking for NVMF_TRTYPE_MAX before proceeding. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:00.000000Z"}, {"uuid": "ba0426ff-6d89-44e5-88ca-f0f27112bd2f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37828", "type": "seen", "source": "https://t.me/cvedetector/24790", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37828 - \"ufs Linux Kernel NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37828 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: ufs: mcq: Add NULL check in ufshcd_mcq_abort()  \n  \nA race can occur between the MCQ completion path and the abort handler:  \nonce a request completes, __blk_mq_free_request() sets rq->mq_hctx to  \nNULL, meaning the subsequent ufshcd_mcq_req_to_hwq() call in  \nufshcd_mcq_abort() can return a NULL pointer. If this NULL pointer is  \ndereferenced, the kernel will crash.  \n  \nAdd a NULL check for the returned hwq pointer. If hwq is NULL, log an  \nerror and return FAILED, preventing a potential NULL-pointer  \ndereference.  As suggested by Bart, the ufshcd_cmd_inflight() check is  \nremoved.  \n  \nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix  \nufshcd_abort_one racing issue\").  \n  \nThis is found by our static analysis tool KNighter. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:44.000000Z"}, {"uuid": "2c2bac23-cdd9-4896-a5dc-e7183bb25572", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37824", "type": "seen", "source": "https://t.me/cvedetector/24800", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37824 - Linux Kernel Tipc NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37824 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntipc: fix NULL pointer dereference in tipc_mon_reinit_self()  \n  \nsyzbot reported:  \n  \ntipc: Node number set to 1055423674  \nOops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI  \nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]  \nCPU: 3 UID: 0 PID: 6017 Comm: kworker/3:5 Not tainted 6.15.0-rc1-syzkaller-00246-g900241a5cc15 #0 PREEMPT(full)  \nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014  \nWorkqueue: events tipc_net_finalize_work  \nRIP: 0010:tipc_mon_reinit_self+0x11c/0x210 net/tipc/monitor.c:719  \n...  \nRSP: 0018:ffffc9000356fb68 EFLAGS: 00010246  \nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000003ee87cba  \nRDX: 0000000000000000 RSI: ffffffff8dbc56a7 RDI: ffff88804c2cc010  \nRBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000  \nR10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000007  \nR13: fffffbfff2111097 R14: ffff88804ead8000 R15: ffff88804ead9010  \nFS:  0000000000000000(0000) GS:ffff888097ab9000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00000000f720eb00 CR3: 000000000e182000 CR4: 0000000000352ef0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \nCall Trace:  \n   \n tipc_net_finalize+0x10b/0x180 net/tipc/net.c:140  \n process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3238  \n process_scheduled_works kernel/workqueue.c:3319 [inline]  \n worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400  \n kthread+0x3c2/0x780 kernel/kthread.c:464  \n ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:153  \n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245  \n   \n...  \nRIP: 0010:tipc_mon_reinit_self+0x11c/0x210 net/tipc/monitor.c:719  \n...  \nRSP: 0018:ffffc9000356fb68 EFLAGS: 00010246  \nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000003ee87cba  \nRDX: 0000000000000000 RSI: ffffffff8dbc56a7 RDI: ffff88804c2cc010  \nRBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000  \nR10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000007  \nR13: fffffbfff2111097 R14: ffff88804ead8000 R15: ffff88804ead9010  \nFS:  0000000000000000(0000) GS:ffff888097ab9000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00000000f720eb00 CR3: 000000000e182000 CR4: 0000000000352ef0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \n  \nThere is a racing condition between workqueue created when enabling  \nbearer and another thread created when disabling bearer right after  \nthat as follow:  \n  \nenabling_bearer                          | disabling_bearer  \n---------------                          | ----------------  \ntipc_disc_timeout()                      |  \n{                                        | bearer_disable()  \n ...                                     | {  \n schedule_work(&tn->work);               |  tipc_mon_delete()  \n ...                                     |  {  \n}                                        |   ...  \n                                         |   write_lock_bh(&mon->lock);  \n                                         |   mon->self = NULL;  \n                                         |   write_unlock_bh(&mon->lock);  \n                                         |   ...  \n                                         |  }  \ntipc_net_finalize_work()                 | }  \n{                                        |  \n ...                                     |  \n tipc_net_finalize()                     |  \n {                                       |  \n  ...                     [...]", "creation_timestamp": "2025-05-08T11:44:58.000000Z"}, {"uuid": "584f0ef1-9edd-4c52-a166-c91880fd3026", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37820", "type": "seen", "source": "https://t.me/cvedetector/24805", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37820 - Xen-netfront NULL Pointer Dereference and Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37820 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nxen-netfront: handle NULL returned by xdp_convert_buff_to_frame()  \n  \nThe function xdp_convert_buff_to_frame() may return NULL if it fails  \nto correctly convert the XDP buffer into an XDP frame due to memory  \nconstraints, internal errors, or invalid data. Failing to check for NULL  \nmay lead to a NULL pointer dereference if the result is used later in  \nprocessing, potentially causing crashes, data corruption, or undefined  \nbehavior.  \n  \nOn XDP redirect failure, the associated page must be released explicitly  \nif it was previously retained via get_page(). Failing to do so may result  \nin a memory leak, as the pages reference count is not decremented. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:05.000000Z"}, {"uuid": "c544b0b3-ae46-4d5e-93fd-9b82f683ae0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37827", "type": "seen", "source": "https://t.me/cvedetector/24807", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37827 - Here is a title for the vulnerability: \"btrfs: RAID1 Profile Write Pointer Offset Mismatch NULL Pointer Dereference\"\", \n  \"Content\": \"CVE ID : CVE-2025-37827 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: zoned: return EIO on RAID1 block group write pointer mismatch  \n  \nThere was a bug report about a NULL pointer dereference in  \n__btrfs_add_free_space_zoned() that ultimately happens because a  \nconversion from the default metadata profile DUP to a RAID1 profile on two  \ndisks.  \n  \nThe stack trace has the following signature:  \n  \n  BTRFS error (device sdc): zoned: write pointer offset mismatch of zones in raid1 profile  \n  BUG: kernel NULL pointer dereference, address: 0000000000000058  \n  #PF: supervisor read access in kernel mode  \n  #PF: error_code(0x0000) - not-present page  \n  PGD 0 P4D 0  \n  Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI  \n  RIP: 0010:__btrfs_add_free_space_zoned.isra.0+0x61/0x1a0  \n  RSP: 0018:ffffa236b6f3f6d0 EFLAGS: 00010246  \n  RAX: 0000000000000000 RBX: ffff96c8132f3400 RCX: 0000000000000001  \n  RDX: 0000000010000000 RSI: 0000000000000000 RDI: ffff96c8132f3410  \n  RBP: 0000000010000000 R08: 0000000000000003 R09: 0000000000000000  \n  R10: 0000000000000000 R11: 00000000ffffffff R12: 0000000000000000  \n  R13: ffff96c758f65a40 R14: 0000000000000001 R15: 000011aac0000000  \n  FS: 00007fdab1cb2900(0000) GS:ffff96e60ca00000(0000) knlGS:0000000000000000  \n  CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n  CR2: 0000000000000058 CR3: 00000001a05ae000 CR4: 0000000000350ef0  \n  Call Trace:  \n    \n  ? __die_body.cold+0x19/0x27  \n  ? page_fault_oops+0x15c/0x2f0  \n  ? exc_page_fault+0x7e/0x180  \n  ? asm_exc_page_fault+0x26/0x30  \n  ? __btrfs_add_free_space_zoned.isra.0+0x61/0x1a0  \n  btrfs_add_free_space_async_trimmed+0x34/0x40  \n  btrfs_add_new_free_space+0x107/0x120  \n  btrfs_make_block_group+0x104/0x2b0  \n  btrfs_create_chunk+0x977/0xf20  \n  btrfs_chunk_alloc+0x174/0x510  \n  ? srso_return_thunk+0x5/0x5f  \n  btrfs_inc_block_group_ro+0x1b1/0x230  \n  btrfs_relocate_block_group+0x9e/0x410  \n  btrfs_relocate_chunk+0x3f/0x130  \n  btrfs_balance+0x8ac/0x12b0  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? __kmalloc_cache_noprof+0x14c/0x3e0  \n  btrfs_ioctl+0x2686/0x2a80  \n  ? srso_return_thunk+0x5/0x5f  \n  ? ioctl_has_perm.constprop.0.isra.0+0xd2/0x120  \n  __x64_sys_ioctl+0x97/0xc0  \n  do_syscall_64+0x82/0x160  \n  ? srso_return_thunk+0x5/0x5f  \n  ? __memcg_slab_free_hook+0x11a/0x170  \n  ? srso_return_thunk+0x5/0x5f  \n  ? kmem_cache_free+0x3f0/0x450  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? syscall_exit_to_user_mode+0x10/0x210  \n  ? srso_return_thunk+0x5/0x5f  \n  ? do_syscall_64+0x8e/0x160  \n  ? sysfs_emit+0xaf/0xc0  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? seq_read_iter+0x207/0x460  \n  ? srso_return_thunk+0x5/0x5f  \n  ? vfs_read+0x29c/0x370  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? syscall_exit_to_user_mode+0x10/0x210  \n  ? srso_return_thunk+0x5/0x5f  \n  ? do_syscall_64+0x8e/0x160  \n  ? srso_return_thunk+0x5/0x5f  \n  ? exc_page_fault+0x7e/0x180  \n  entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  RIP: 0033:0x7fdab1e0ca6d  \n  RSP: 002b:00007ffeb2b60c80 EFLAGS: 00000246 ORIG_RAX: 0000000000000010  \n  RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fdab1e0ca6d  \n  RDX: 00007ffeb2b60d80 RSI: 00000000c4009420 RDI: 0000000000000003  \n  RBP: 00007ffeb2b60cd0 R08: 0000000000000000 R09: 0000000000000013  \n  R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000  \n  R13: 00007ffeb2b6343b R14: 00007ffeb2b60d80 R15: 0000000000000001  \n    \n  CR2: 0000000000000058  \n  ---[ end trace 0000000000000000 ]---  \n  \nThe 1st line is the most interesting here:  \n  \n BTRFS error (device sdc): zoned: write pointer offset mismatch of zones in raid1 profile  \n  \nWhen a RAID1 block-group is created and a writ[...]", "creation_timestamp": "2025-05-08T11:45:07.000000Z"}, {"uuid": "b1226fb9-353b-44e7-ad43-bb8661ba1675", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://t.me/cvedetector/24809", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37823 - Linux Kernel Net-Sched HFSC Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37823 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too  \n  \nSimilarly to the previous patch, we need to safe guard hfsc_dequeue()  \ntoo. But for this one, we don't have a reliable reproducer. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:09.000000Z"}, {"uuid": "a794d955-2054-49b5-9076-8973df06f194", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37828", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebjyfse32", "content": "", "creation_timestamp": "2025-05-08T07:11:40.520257Z"}, {"uuid": "5dd7f0c1-764e-4ca1-8930-051eaa310358", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37829", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebphnbqx2", "content": "", "creation_timestamp": "2025-05-08T07:11:41.273666Z"}, {"uuid": "72b9bbb5-4d80-411c-afcc-7f3a1924fe29", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebwerh6c2", "content": "", "creation_timestamp": "2025-05-08T07:11:51.179643Z"}, {"uuid": "2aef7889-160f-4f43-b038-9ef4b36251ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37827", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebx2sjxj2", "content": "", "creation_timestamp": "2025-05-08T07:11:51.709538Z"}, {"uuid": "d28fa0d6-8038-4b94-8ccf-718534080347", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://bsky.app/profile/potato.software/post/3lonid7trt72z", "content": "", "creation_timestamp": "2025-05-08T08:24:01.112834Z"}, {"uuid": "5333f12d-e873-4d89-a7f7-2fdf68c2d4c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37821", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqr6q3o2o", "content": "", "creation_timestamp": "2025-05-08T08:31:37.564602Z"}, {"uuid": "73be9877-d319-413c-a74b-19ccaeb91ded", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrcggp22", "content": "", "creation_timestamp": "2025-05-08T08:31:38.087146Z"}, {"uuid": "dc30947a-5a06-475f-9cb6-7a9bbae8e9ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37820", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrg3wy2h", "content": "", "creation_timestamp": "2025-05-08T08:31:38.689181Z"}, {"uuid": "6bf86505-526b-4817-b1e4-6d65e73f4858", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37825", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrjp5z2p", "content": "", "creation_timestamp": "2025-05-08T08:31:39.191519Z"}, {"uuid": "6e5efd5d-258a-4934-bce9-2bc61e763b9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37829", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrn25i2l", "content": "", "creation_timestamp": "2025-05-08T08:31:39.669075Z"}, {"uuid": "b44d4e3d-a4fb-46a7-b531-5dbcadecb2bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37827", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrqh2h2h", "content": "", "creation_timestamp": "2025-05-08T08:31:40.154806Z"}, {"uuid": "31595995-fbe7-4674-aff7-59deeab9ab6b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqru2pg2o", "content": "", "creation_timestamp": "2025-05-08T08:31:40.645476Z"}, {"uuid": "04f62978-084c-4fb3-8a4a-0820e2a832fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37824", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrxhtt2n", "content": "", "creation_timestamp": "2025-05-08T08:31:41.168443Z"}, {"uuid": "ec6623ce-9d77-4ba8-bbfa-695b7b80cdc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37828", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqsbwmp2h", "content": "", "creation_timestamp": "2025-05-08T08:31:42.891250Z"}, {"uuid": "e6cd46e6-610d-4650-967b-d4ffd57924c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqst5bj2e", "content": "", "creation_timestamp": "2025-05-08T08:31:45.752102Z"}, {"uuid": "ddbc7f52-492f-4915-8289-e63b2245f6aa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "643cbd6d-99c9-4350-9b25-73ca387f12f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260316", "content": "", "creation_timestamp": "2026-03-16T03:00:00.000000Z"}, {"uuid": "93a84e9e-fe4b-4ad9-892b-26a41e665acb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3782", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15083", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3782\n\ud83d\udd25 CVSS Score: 6.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Cision Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018id\u2019 parameter in all versions up to, and including, 4.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\ud83d\udccf Published: 2025-05-06T09:21:49.867Z\n\ud83d\udccf Modified: 2025-05-06T09:21:49.867Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/c5b8268a-f3a3-4576-b235-962de37cc388?source=cve\n2. https://plugins.trac.wordpress.org/browser/cision-block/tags/4.3.0/src/Frontend/templates/cision-block.php#L51\n3. https://wordpress.org/plugins/cision-block/#developers\n4. https://plugins.trac.wordpress.org/changeset/3288041/", "creation_timestamp": "2025-05-06T10:21:03.000000Z"}, {"uuid": "8db1646a-d7b2-4375-accb-0a43bbf97da4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37829", "type": "seen", "source": "https://t.me/cvedetector/24793", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37829 - \"Linux cpufreq: NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37829 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncpufreq: scpi: Fix null-ptr-deref in scpi_cpufreq_get_rate()  \n  \ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present  \nin the policy->cpus mask. scpi_cpufreq_get_rate() does not check for  \nthis case, which results in a NULL pointer dereference. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:46.000000Z"}, {"uuid": "fe2ed12f-eda7-4418-8fd4-1d6373f53f23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3782", "type": "seen", "source": "https://t.me/cvedetector/24600", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3782 - Cision Block Stored Cross-Site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3782 \nPublished : May 6, 2025, 10:15 a.m. | 1\u00a0hour, 45\u00a0minutes ago \nDescription : The Cision Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018id\u2019 parameter in all versions up to, and including, 4.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-06T14:29:08.000000Z"}, {"uuid": "b869bfbf-71cf-4eab-a4fb-9f68ee253e52", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114473653498479043", "content": "", "creation_timestamp": "2025-05-08T18:35:33.067803Z"}, {"uuid": "7ad39980-b67c-4c39-8d5a-bdad36a753e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0291/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "93973e4a-3255-486c-825f-bddff1c56311", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37820", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}]}