{"vulnerability": "cve-2025-3781", "sightings": [{"uuid": "2a4d87af-19cc-472a-a693-a220d89af0b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37816", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqkbaj2e", "content": "", "creation_timestamp": "2025-05-08T08:31:35.135172Z"}, {"uuid": "1c842eb0-8a1d-4112-ac19-c5fb580b3b53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37818", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqtvxp2h", "content": "", "creation_timestamp": "2025-05-08T08:31:35.709763Z"}, {"uuid": "50f3119d-ad6d-4495-94e7-36602beb4076", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37819", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqxfmz2r", "content": "", "creation_timestamp": "2025-05-08T08:31:36.489652Z"}, {"uuid": "64a63007-45d7-4d68-87fe-8a79c963d940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37817", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqr33wi2l", "content": "", "creation_timestamp": "2025-05-08T08:31:37.027797Z"}, {"uuid": "818f24a5-34a6-4767-b9e8-c7e989ee5b72", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37817", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15492", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37817\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmcb: fix a double free bug in chameleon_parse_gdd()\n\nIn chameleon_parse_gdd(), if mcb_device_register() fails, 'mdev'\nwould be released in mcb_device_register() via put_device().\nThus, goto 'err' label and free 'mdev' again causes a double free.\nJust return if mcb_device_register() fails.\n\ud83d\udccf Published: 2025-05-08T06:26:12.683Z\n\ud83d\udccf Modified: 2025-05-08T06:26:12.683Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d70184958b0ea8c0fd52e2b456654b503e769fc8\n2. https://git.kernel.org/stable/c/4ffe8c9fb561e4427dd1a3056cd5b3685b74f78d\n3. https://git.kernel.org/stable/c/59f993cd36b6e28a394ba3d977e8ffe5c9884e3b\n4. https://git.kernel.org/stable/c/c5b8a549ef1fcc6066b037a3962c79d60465ba0b\n5. https://git.kernel.org/stable/c/96838eb1836fd372e42be5db84f0b333b65146a6\n6. https://git.kernel.org/stable/c/df1a5d5c6134224f9298e5189230f9d29ae50cac\n7. https://git.kernel.org/stable/c/bcc7d58ee5173e34306026bd01e1fbf75e169d37\n8. https://git.kernel.org/stable/c/7c7f1bfdb2249f854a736d9b79778c7e5a29a150", "creation_timestamp": "2025-05-08T07:23:20.000000Z"}, {"uuid": "d3896b10-c5be-4e06-90ea-24ddb2d03400", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37812", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15496", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37812\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: Fix deadlock when using NCM gadget\n\nThe cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit\n58f2fcb3a845 (\"usb: cdnsp: Fix deadlock issue during using NCM gadget\").\n\nUnder PREEMPT_RT the deadlock can be readily triggered by heavy network\ntraffic, for example using \"iperf --bidir\" over NCM ethernet link.\n\nThe deadlock occurs because the threaded interrupt handler gets\npreempted by a softirq, but both are protected by the same spinlock.\nPrevent deadlock by disabling softirq during threaded irq handler.\n\ud83d\udccf Published: 2025-05-08T06:26:09.355Z\n\ud83d\udccf Modified: 2025-05-08T06:26:09.355Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/eebfb64c624fc738b669100173344fb441c5e719\n2. https://git.kernel.org/stable/c/59a760e4796a3cd88d8b9d7706e0a638de677751\n3. https://git.kernel.org/stable/c/b96239582531775f2fdcb14de29bdb6870fd4c8c\n4. https://git.kernel.org/stable/c/c27db84ed44e50ff90d9e3a2a25fae2e0a0fa015\n5. https://git.kernel.org/stable/c/48a62deb857f0694f611949015e70ad194d97159\n6. https://git.kernel.org/stable/c/74cd6e408a4c010e404832f0e4609d29bf1d0c41\n7. https://git.kernel.org/stable/c/09e90a9689a4aac7a2f726dc2aa472b0b37937b7\n8. https://git.kernel.org/stable/c/a1059896f2bfdcebcdc7153c3be2307ea319501f", "creation_timestamp": "2025-05-08T07:23:24.000000Z"}, {"uuid": "7edfa7ef-4243-4383-ab90-b19690f4af72", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37813", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15495", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37813\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Fix invalid pointer dereference in Etron workaround\n\nThis check is performed before prepare_transfer() and prepare_ring(), so\nenqueue can already point at the final link TRB of a segment. And indeed\nit will, some 0.4% of times this code is called.\n\nThen enqueue + 1 is an invalid pointer. It will crash the kernel right\naway or load some junk which may look like a link TRB and cause the real\nlink TRB to be replaced with a NOOP. This wouldn't end well.\n\nUse a functionally equivalent test which doesn't dereference the pointer\nand always gives correct result.\n\nSomething has crashed my machine twice in recent days while playing with\nan Etron HC, and a control transfer stress test ran for confirmation has\njust crashed it again. The same test passes with this patch applied.\n\ud83d\udccf Published: 2025-05-08T06:26:10.000Z\n\ud83d\udccf Modified: 2025-05-08T06:26:10.000Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/142273a49f2c315eabdbdf5a71c15e479b75ca91\n2. https://git.kernel.org/stable/c/bce3055b08e303e28a8751f6073066f5c33a0744\n3. https://git.kernel.org/stable/c/0624e29c595b05e7a0e6d1c368f0a05799928e30\n4. https://git.kernel.org/stable/c/1ea050da5562af9b930d17cbbe9632d30f5df43a", "creation_timestamp": "2025-05-08T07:23:23.000000Z"}, {"uuid": "db26d3a0-05d5-4b40-b0af-9e7e65bdf3cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37815", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15494", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37815\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration\n\nResolve kernel panic while accessing IRQ handler associated with the\ngenerated IRQ. This is done by acquiring the spinlock and storing the\ncurrent interrupt state before handling the interrupt request using\ngeneric_handle_irq.\n\nA previous fix patch was submitted where 'generic_handle_irq' was\nreplaced with 'handle_nested_irq'. However, this change also causes\nthe kernel panic where after determining which GPIO triggered the\ninterrupt and attempting to call handle_nested_irq with the mapped\nIRQ number, leads to a failure in locating the registered handler.\n\ud83d\udccf Published: 2025-05-08T06:26:11.402Z\n\ud83d\udccf Modified: 2025-05-08T06:26:11.402Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1263d5f581908602c618c6665e683c4436383a09\n2. https://git.kernel.org/stable/c/62957f58ab3aa7fa792dc6ff3575624062539a4d\n3. https://git.kernel.org/stable/c/12cc2193f2b9548e8ea5fbce8201b44158222edf\n4. https://git.kernel.org/stable/c/4e02059dc91068bc5017b8546f9ec3b930f6d6a6\n5. https://git.kernel.org/stable/c/18eb77c75ed01439f96ae5c0f33461eb5134b907", "creation_timestamp": "2025-05-08T07:23:22.000000Z"}, {"uuid": "4203b9e5-d8bd-493e-ad66-780ad7f56d8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37816", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15493", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37816\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmei: vsc: Fix fortify-panic caused by invalid counted_by() use\n\ngcc 15 honors the __counted_by(len) attribute on vsc_tp_packet.buf[]\nand the vsc-tp.c code is using this in a wrong way. len does not contain\nthe available size in the buffer, it contains the actual packet length\n*without* the crc. So as soon as vsc_tp_xfer() tries to add the crc to\nbuf[] the fortify-panic handler gets triggered:\n\n[   80.842193] memcpy: detected buffer overflow: 4 byte write of buffer size 0\n[   80.842243] WARNING: CPU: 4 PID: 272 at lib/string_helpers.c:1032 __fortify_report+0x45/0x50\n...\n[   80.843175]  __fortify_panic+0x9/0xb\n[   80.843186]  vsc_tp_xfer.cold+0x67/0x67 [mei_vsc_hw]\n[   80.843210]  ? seqcount_lockdep_reader_access.constprop.0+0x82/0x90\n[   80.843229]  ? lockdep_hardirqs_on+0x7c/0x110\n[   80.843250]  mei_vsc_hw_start+0x98/0x120 [mei_vsc]\n[   80.843270]  mei_reset+0x11d/0x420 [mei]\n\nThe easiest fix would be to just drop the counted-by but with the exception\nof the ack buffer in vsc_tp_xfer_helper() which only contains enough room\nfor the packet-header, all other uses of vsc_tp_packet always use a buffer\nof VSC_TP_MAX_XFER_SIZE bytes for the packet.\n\nInstead of just dropping the counted-by, split the vsc_tp_packet struct\ndefinition into a header and a full-packet definition and use a fixed\nsize buf[] in the packet definition, this way fortify-source buffer\noverrun checking still works when enabled.\n\ud83d\udccf Published: 2025-05-08T06:26:12.063Z\n\ud83d\udccf Modified: 2025-05-08T06:26:12.063Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3e243378f27cc7d11682a3ad720228b0723affa5\n2. https://git.kernel.org/stable/c/ac04663c67f244810b3492e9ecd9f7cdbefeca2d\n3. https://git.kernel.org/stable/c/00f1cc14da0f06d2897b8c528df7c7dcf1b8da50", "creation_timestamp": "2025-05-08T07:23:21.000000Z"}, {"uuid": "d19c2ce4-dbfa-47a0-a967-6367fe99d926", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37818", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15491", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37818\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Return NULL from huge_pte_offset() for invalid PMD\n\nLoongArch's huge_pte_offset() currently returns a pointer to a PMD slot\neven if the underlying entry points to invalid_pte_table (indicating no\nmapping). Callers like smaps_hugetlb_range() fetch this invalid entry\nvalue (the address of invalid_pte_table) via this pointer.\n\nThe generic is_swap_pte() check then incorrectly identifies this address\nas a swap entry on LoongArch, because it satisfies the \"!pte_present()\n&& !pte_none()\" conditions. This misinterpretation, combined with a\ncoincidental match by is_migration_entry() on the address bits, leads to\nkernel crashes in pfn_swap_entry_to_page().\n\nFix this at the architecture level by modifying huge_pte_offset() to\ncheck the PMD entry's content using pmd_none() before returning. If the\nentry is invalid (i.e., it points to invalid_pte_table), return NULL\ninstead of the pointer to the slot.\n\ud83d\udccf Published: 2025-05-08T06:26:13.322Z\n\ud83d\udccf Modified: 2025-05-08T06:26:13.322Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/34256805720993e37adf6127371a1265aea8376a\n2. https://git.kernel.org/stable/c/2ca9380b12711afe95b3589bd82b59623b3c96b3\n3. https://git.kernel.org/stable/c/51424fd171cee6a33f01f7c66b8eb23ac42289d4\n4. https://git.kernel.org/stable/c/b49f085cd671addbda4802d6b9382513f7dd0f30\n5. https://git.kernel.org/stable/c/bd51834d1cf65a2c801295d230c220aeebf87a73", "creation_timestamp": "2025-05-08T07:23:16.000000Z"}, {"uuid": "a81cebb4-7c9e-48a7-8ca2-d78ba880f526", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37819", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15490", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37819\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()\n\nWith ACPI in place, gicv2m_get_fwnode() is registered with the pci\nsubsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime\nduring a PCI host bridge probe. But, the call back is wrongly marked as\n__init, causing it to be freed, while being registered with the PCI\nsubsystem and could trigger:\n\n Unable to handle kernel paging request at virtual address ffff8000816c0400\n  gicv2m_get_fwnode+0x0/0x58 (P)\n  pci_set_bus_msi_domain+0x74/0x88\n  pci_register_host_bridge+0x194/0x548\n\nThis is easily reproducible on a Juno board with ACPI boot.\n\nRetain the function for later use.\n\ud83d\udccf Published: 2025-05-08T06:26:13.975Z\n\ud83d\udccf Modified: 2025-05-08T06:26:13.975Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2f2803e4b5e4df2b08d378deaab78b1681ef9b30\n2. https://git.kernel.org/stable/c/3939d6f29d34cdb60e3f68b76e39e00a964a1d51\n3. https://git.kernel.org/stable/c/47bee0081b483b077c7560bc5358ad101f89c8ef\n4. https://git.kernel.org/stable/c/3318dc299b072a0511d6dfd8367f3304fb6d9827", "creation_timestamp": "2025-05-08T07:23:15.000000Z"}, {"uuid": "d9a4f55f-c614-4b9d-b35d-0d72abca093a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37818", "type": "seen", "source": "https://t.me/cvedetector/24804", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37818 - LoongArch Linux Kernel Invalid PMD Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37818 \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  \nLoongArch: Return NULL from huge_pte_offset() for invalid PMD  \n  \nLoongArch's huge_pte_offset() currently returns a pointer to a PMD slot  \neven if the underlying entry points to invalid_pte_table (indicating no  \nmapping). Callers like smaps_hugetlb_range() fetch this invalid entry  \nvalue (the address of invalid_pte_table) via this pointer.  \n  \nThe generic is_swap_pte() check then incorrectly identifies this address  \nas a swap entry on LoongArch, because it satisfies the \"!pte_present()  \n&& !pte_none()\" conditions. This misinterpretation, combined with a  \ncoincidental match by is_migration_entry() on the address bits, leads to  \nkernel crashes in pfn_swap_entry_to_page().  \n  \nFix this at the architecture level by modifying huge_pte_offset() to  \ncheck the PMD entry's content using pmd_none() before returning. If the  \nentry is invalid (i.e., it points to invalid_pte_table), return NULL  \ninstead of the pointer to the slot. \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": "2ebe0f7a-be4a-4698-982a-1f4e74932c02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37819", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/24806", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37819 - \"Linux Kernel GICv2m Use After Free Vulnerability in irqchip\"\", \n  \"Content\": \"CVE ID : CVE-2025-37819 \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  \nirqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()  \n  \nWith ACPI in place, gicv2m_get_fwnode() is registered with the pci  \nsubsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime  \nduring a PCI host bridge probe. But, the call back is wrongly marked as  \n__init, causing it to be freed, while being registered with the PCI  \nsubsystem and could trigger:  \n  \n Unable to handle kernel paging request at virtual address ffff8000816c0400  \n  gicv2m_get_fwnode+0x0/0x58 (P)  \n  pci_set_bus_msi_domain+0x74/0x88  \n  pci_register_host_bridge+0x194/0x548  \n  \nThis is easily reproducible on a Juno board with ACPI boot.  \n  \nRetain the function for later use. \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:06.000000Z"}, {"uuid": "66b76c01-e516-4954-9ced-3000f64c7bc3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37812", "type": "seen", "source": "https://t.me/cvedetector/24810", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37812 - Linux Kernel USB cdns3 NCM Gadget Deadlock\", \n  \"Content\": \"CVE ID : CVE-2025-37812 \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  \nusb: cdns3: Fix deadlock when using NCM gadget  \n  \nThe cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit  \n58f2fcb3a845 (\"usb: cdnsp: Fix deadlock issue during using NCM gadget\").  \n  \nUnder PREEMPT_RT the deadlock can be readily triggered by heavy network  \ntraffic, for example using \"iperf --bidir\" over NCM ethernet link.  \n  \nThe deadlock occurs because the threaded interrupt handler gets  \npreempted by a softirq, but both are protected by the same spinlock.  \nPrevent deadlock by disabling softirq during threaded irq handler. \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:45.000000Z"}, {"uuid": "39a1bd71-3da9-4670-ab5e-85592dda02a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37811", "type": "seen", "source": "https://t.me/cvedetector/24811", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37811 - \"Qualcomm Chipidea USB Driver Null Pointer Dereference\"\", \n  \"Content\": \"CVE ID : CVE-2025-37811 \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  \nusb: chipidea: ci_hdrc_imx: fix usbmisc handling  \n  \nusbmisc is an optional device property so it is totally valid for the  \ncorresponding data->usbmisc_data to have a NULL value.  \n  \nCheck that before dereferencing the pointer.  \n  \nFound by Linux Verification Center (linuxtesting.org) with Svace static  \nanalysis tool. \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:46.000000Z"}]}