{"vulnerability": "CVE-2025-2200", "sightings": [{"uuid": "ac1bd9a6-5213-4ec6-9180-7cd7dec45903", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2200", "type": "seen", "source": "https://bsky.app/profile/cyberalerts.bsky.social/post/3lkl325bka52u", "content": "", "creation_timestamp": "2025-03-17T11:40:12.162271Z"}, {"uuid": "e0ca6bb8-2448-4d67-bd59-397bd1907f15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2200", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lklcf3rd3a2l", "content": "", "creation_timestamp": "2025-03-17T13:51:36.717031Z"}, {"uuid": "3a67dbf7-586a-4c6d-9276-c11fa5c0f6cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22008", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3lmnyh2gblc2h", "content": "", "creation_timestamp": "2025-04-13T02:22:10.017461Z"}, {"uuid": "f11bcb49-b1de-4b3f-9f99-123262e827d4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2200", "type": "seen", "source": "Telegram/GZuMtE7t_vqUUXxVbM6zfoPB-Bc-Xdm5Sf6zYaWo4RQQHsE", "content": "", "creation_timestamp": "2025-03-17T12:01:12.000000Z"}, {"uuid": "f00b7f21-a817-4390-8e21-974372393892", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22004", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114272971915717743", "content": "", "creation_timestamp": "2025-04-03T07:59:34.340228Z"}, {"uuid": "62a5d6bf-1af9-49c7-a66b-24a6c95e9279", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22004", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114272971915717743", "content": "", "creation_timestamp": "2025-04-03T07:59:34.343010Z"}, {"uuid": "f3e16c92-4f93-4795-8bae-ae3b7d42fda3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22002", "type": "seen", "source": "https://bsky.app/profile/potato.software/post/3llvguwq57s23", "content": "", "creation_timestamp": "2025-04-03T08:03:51.273357Z"}, {"uuid": "2aab679a-0d46-4ff9-854c-f45a708a979e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22000", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfcjr6j2b", "content": "", "creation_timestamp": "2025-04-03T11:11:58.202988Z"}, {"uuid": "f40aace9-64b9-4a25-843d-3ae5ddae36ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22003", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfd3dmb2h", "content": "", "creation_timestamp": "2025-04-03T11:12:01.205080Z"}, {"uuid": "7a92ad40-3b53-4bae-82dd-ec3a262ed448", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22004", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfdc4qs2r", "content": "", "creation_timestamp": "2025-04-03T11:12:02.345932Z"}, {"uuid": "dae2ed64-1727-445f-ba08-a6357d3f2b32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22007", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfdfjsl2z", "content": "", "creation_timestamp": "2025-04-03T11:12:02.934176Z"}, {"uuid": "09a00a2a-433d-4cdd-85c4-a6f0dae89316", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22006", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfdtiwd2c", "content": "", "creation_timestamp": "2025-04-03T11:12:05.251748Z"}, {"uuid": "97d2582b-8348-4b41-b4e5-8b4ecf413575", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22002", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfdx7av2f", "content": "", "creation_timestamp": "2025-04-03T11:12:05.876744Z"}, {"uuid": "67591175-186f-4ded-ad2c-a33ccf4131ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22001", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfe2pn62w", "content": "", "creation_timestamp": "2025-04-03T11:12:06.432810Z"}, {"uuid": "5b6900d7-5ac1-4787-a733-6d48b83fdbb4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22005", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfe6gl326", "content": "", "creation_timestamp": "2025-04-03T11:12:07.038591Z"}, {"uuid": "683be9b6-55b4-4750-b75a-fe545689b707", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22003", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3lmdnknr2sc2h", "content": "", "creation_timestamp": "2025-04-08T23:40:40.616272Z"}, {"uuid": "99fdc6cf-09c7-4965-aeb3-72eaee983c67", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2200", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/7752", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-2200\n\ud83d\udd25 CVSS Score: 9.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: QL injection vulnerability in the IcProgreso Innovaci\u00f3n y Cualificaci\u00f3n plugin. This vulnerability allows an attacker to obtain, update and delete data from the database by injecting an SQL query on the parameters user, id, idGroup, start_date and end_date in the endpoint /report/icprogreso/generar_blocks.php.\n\ud83d\udccf Published: 2025-03-17T10:09:49.433Z\n\ud83d\udccf Modified: 2025-03-17T10:15:43.811Z\n\ud83d\udd17 References:\n1. https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-moodle-innovacion-y-cualificacion-plugins", "creation_timestamp": "2025-03-17T10:54:23.000000Z"}, {"uuid": "402ee8b0-6419-4e6d-99f9-ed7aa5dd34cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22008", "type": "seen", "source": "https://t.me/cvedetector/22452", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22008 - Linux Kernel Regulator Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22008 \nPublished : April 8, 2025, 9:15 a.m. | 2\u00a0hours, 10\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nregulator: check that dummy regulator has been probed before using it  \n  \nDue to asynchronous driver probing there is a chance that the dummy  \nregulator hasn't already been probed when first accessing it. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-08T14:00:04.000000Z"}, {"uuid": "40444c38-7596-4d3e-8767-9bf2ca7e1a82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22009", "type": "seen", "source": "https://t.me/cvedetector/22453", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22009 - Linux Kernel Dummy Regulator Synchronous Probing Denial of Service Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22009 \nPublished : April 8, 2025, 9:15 a.m. | 2\u00a0hours, 10\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nregulator: dummy: force synchronous probing  \n  \nSometimes I get a NULL pointer dereference at boot time in kobject_get()  \nwith the following call stack:  \n  \nanatop_regulator_probe()  \n devm_regulator_register()  \n  regulator_register()  \n   regulator_resolve_supply()  \n    kobject_get()  \n  \nBy placing some extra BUG_ON() statements I could verify that this is  \nraised because probing of the 'dummy' regulator driver is not completed  \n('dummy_regulator_rdev' is still NULL).  \n  \nIn the JTAG debugger I can see that dummy_regulator_probe() and  \nanatop_regulator_probe() can be run by different kernel threads  \n(kworker/u4:*).  I haven't further investigated whether this can be  \nchanged or if there are other possibilities to force synchronization  \nbetween these two probe routines.  On the other hand I don't expect much  \nboot time penalty by probing the 'dummy' regulator synchronously. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-08T14:00:04.000000Z"}, {"uuid": "554c6822-f7a8-4ef7-83b3-05c302e387f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22004", "type": "seen", "source": "https://t.me/cvedetector/21963", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22004 - Linux Kernel Use After Free Vulnerability in ATM Net\", \n  \"Content\": \"CVE ID : CVE-2025-22004 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: atm: fix use after free in lec_send()  \n  \nThe ->send() operation frees skb so save the length before calling  \n->send() to avoid a use after free. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:22.000000Z"}, {"uuid": "6fa5a680-221f-452e-8b0c-f9c7fc86880a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22003", "type": "seen", "source": "https://t.me/cvedetector/21962", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22003 - Linux Kernel CAN Ucan Out-of-Bound Read Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22003 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncan: ucan: fix out of bound read in strscpy() source  \n  \nCommit 7fdaf8966aae (\"can: ucan: use strscpy() to instead of strncpy()\")  \nunintentionally introduced a one byte out of bound read on strscpy()'s  \nsource argument (which is kind of ironic knowing that strscpy() is meant  \nto be a more secure alternative :)).  \n  \nLet's consider below buffers:  \n  \n  dest[len + 1]; /* will be NUL terminated */  \n  src[len]; /* may not be NUL terminated */  \n  \nWhen doing:  \n  \n  strncpy(dest, src, len);  \n  dest[len] = '\\0';  \n  \nstrncpy() will read up to len bytes from src.  \n  \nOn the other hand:  \n  \n  strscpy(dest, src, len + 1);  \n  \nwill read up to len + 1 bytes from src, that is to say, an out of bound  \nread of one byte will occur on src if it is not NUL terminated. Note  \nthat the src[len] byte is never copied, but strscpy() still needs to  \nread it to check whether a truncation occurred or not.  \n  \nThis exact pattern happened in ucan.  \n  \nThe root cause is that the source is not NUL terminated. Instead of  \ndoing a copy in a local buffer, directly NUL terminate it as soon as  \nusb_control_msg() returns. With this, the local firmware_str[] variable  \ncan be removed.  \n  \nOn top of this do a couple refactors:  \n  \n  - ucan_ctl_payload->raw is only used for the firmware string, so  \n    rename it to ucan_ctl_payload->fw_str and change its type from u8 to  \n    char.  \n  \n  - ucan_device_request_in() is only used to retrieve the firmware  \n    string, so rename it to ucan_get_fw_str() and refactor it to make it  \n    directly handle all the string termination logic. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:21.000000Z"}, {"uuid": "0e05e942-1322-433e-8307-0a8887d0cf2b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22000", "type": "seen", "source": "https://t.me/cvedetector/21965", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22000 - Linux Kernel Memory Leak in Huge Memory Folios\", \n  \"Content\": \"CVE ID : CVE-2025-22000 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm/huge_memory: drop beyond-EOF folios with the right number of refs  \n  \nWhen an after-split folio is large and needs to be dropped due to EOF,  \nfolio_put_refs(folio, folio_nr_pages(folio)) should be used to drop all  \npage cache refs.  Otherwise, the folio will not be freed, causing memory  \nleak.  \n  \nThis leak would happen on a filesystem with blocksize > page_size and a  \ntruncate is performed, where the blocksize makes folios split to >0 order  \nones, causing truncated folios not being freed. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:26.000000Z"}, {"uuid": "4ae3586b-33b9-42b1-ba7b-ccb2b282ac57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22002", "type": "seen", "source": "https://t.me/cvedetector/21961", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22002 - HP Linux Kernel Netfs NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22002 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfs: Call `invalidate_cache` only if implemented  \n  \nMany filesystems such as NFS and Ceph do not implement the  \n`invalidate_cache` method.  On those filesystems, if writing to the  \ncache (`NETFS_WRITE_TO_CACHE`) fails for some reason, the kernel  \ncrashes like this:  \n  \n BUG: kernel NULL pointer dereference, address: 0000000000000000  \n #PF: supervisor instruction fetch in kernel mode  \n #PF: error_code(0x0010) - not-present page  \n PGD 0 P4D 0  \n Oops: Oops: 0010 [#1] SMP PTI  \n CPU: 9 UID: 0 PID: 3380 Comm: kworker/u193:11 Not tainted 6.13.3-cm4all1-hp #437  \n Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/17/2018  \n Workqueue: events_unbound netfs_write_collection_worker  \n RIP: 0010:0x0  \n Code: Unable to access opcode bytes at 0xffffffffffffffd6.  \n RSP: 0018:ffff9b86e2ca7dc0 EFLAGS: 00010202  \n RAX: 0000000000000000 RBX: 0000000000000000 RCX: 7fffffffffffffff  \n RDX: 0000000000000001 RSI: ffff89259d576a18 RDI: ffff89259d576900  \n RBP: ffff89259d5769b0 R08: ffff9b86e2ca7d28 R09: 0000000000000002  \n R10: ffff89258ceaca80 R11: 0000000000000001 R12: 0000000000000020  \n R13: ffff893d158b9338 R14: ffff89259d576900 R15: ffff89259d5769b0  \n FS:  0000000000000000(0000) GS:ffff893c9fa40000(0000) knlGS:0000000000000000  \n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n CR2: ffffffffffffffd6 CR3: 000000054442e003 CR4: 00000000001706f0  \n Call Trace:  \n    \n  ? __die+0x1f/0x60  \n  ? page_fault_oops+0x15c/0x460  \n  ? try_to_wake_up+0x2d2/0x530  \n  ? exc_page_fault+0x5e/0x100  \n  ? asm_exc_page_fault+0x22/0x30  \n  netfs_write_collection_worker+0xe9f/0x12b0  \n  ? xs_poll_check_readable+0x3f/0x80  \n  ? xs_stream_data_receive_workfn+0x8d/0x110  \n  process_one_work+0x134/0x2d0  \n  worker_thread+0x299/0x3a0  \n  ? __pfx_worker_thread+0x10/0x10  \n  kthread+0xba/0xe0  \n  ? __pfx_kthread+0x10/0x10  \n  ret_from_fork+0x30/0x50  \n  ? __pfx_kthread+0x10/0x10  \n  ret_from_fork_asm+0x1a/0x30  \n    \n Modules linked in:  \n CR2: 0000000000000000  \n  \nThis patch adds the missing `NULL` check. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:20.000000Z"}, {"uuid": "920a74fc-e915-4c4c-a7df-299b8d8b2010", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22001", "type": "seen", "source": "https://t.me/cvedetector/21960", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22001 - \"Qualcomm Accelerator Integer Overflow Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-22001 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \naccel/qaic: Fix integer overflow in qaic_validate_req()  \n  \nThese are u64 variables that come from the user via  \nqaic_attach_slice_bo_ioctl().  Use check_add_overflow() to ensure that  \nthe math doesn't have an integer wrapping bug. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:20.000000Z"}, {"uuid": "1bc3fcfc-5c47-4315-964b-28027f4cb7bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22007", "type": "seen", "source": "https://t.me/cvedetector/21953", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22007 - Linux Bluetooth NULL Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22007 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: Fix error code in chan_alloc_skb_cb()  \n  \nThe chan_alloc_skb_cb() function is supposed to return error pointers on  \nerror.  Returning NULL will lead to a NULL dereference. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:08.000000Z"}, {"uuid": "b20706f1-9323-4e0c-b9a6-8eb056be6038", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22006", "type": "seen", "source": "https://t.me/cvedetector/21952", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22006 - Cisco Ethernet Linux Kernel NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22006 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: ethernet: ti: am65-cpsw: Fix NAPI registration sequence  \n  \nRegistering the interrupts for TX or RX DMA Channels prior to registering  \ntheir respective NAPI callbacks can result in a NULL pointer dereference.  \nThis is seen in practice as a random occurrence since it depends on the  \nrandomness associated with the generation of traffic by Linux and the  \nreception of traffic from the wire. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:07.000000Z"}, {"uuid": "6007499f-d777-430f-a3c5-4a4eec2cd221", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22005", "type": "seen", "source": "https://t.me/cvedetector/21951", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22005 - Linux Kernel IPv6 Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22005 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().  \n  \nfib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything  \nwhen it fails.  \n  \nCommit 7dd73168e273 (\"ipv6: Always allocate pcpu memory in a fib6_nh\")  \nmoved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()  \nbut forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in  \ncase it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.  \n  \nLet's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the  \nerror path.  \n  \nNote that we can remove the fib6_nh_release() call in nh_create_ipv6()  \nlater in net-next.git. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:06.000000Z"}, {"uuid": "6fc9e27d-56e4-4b41-aaf0-905b01f0f247", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22004", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lpeuw76y422j", "content": "", "creation_timestamp": "2025-05-17T15:40:38.940330Z"}, {"uuid": "73e0a926-8210-41fe-b733-3bf67748df2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2200", "type": "seen", "source": "MISP/682bdba3-46b7-4a8f-b7be-c6bf4b4f9868", "content": "", "creation_timestamp": "2025-08-13T13:26:35.000000Z"}, {"uuid": "88aaee61-a346-46b5-87b7-d7719a0d9133", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22008", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "816b4a20-35e7-4051-85ab-5a4f15f959a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22001", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/10181", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22001\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\naccel/qaic: Fix integer overflow in qaic_validate_req()\n\nThese are u64 variables that come from the user via\nqaic_attach_slice_bo_ioctl().  Use check_add_overflow() to ensure that\nthe math doesn't have an integer wrapping bug.\n\ud83d\udccf Published: 2025-04-03T07:19:04.251Z\n\ud83d\udccf Modified: 2025-04-03T07:19:04.251Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4b2a170c25862ad116bd31be6b9841646b4862e8\n2. https://git.kernel.org/stable/c/b362fc904d264a88b4af20baae9e82491c285e9c\n3. https://git.kernel.org/stable/c/57fae0c505f49bb1e3d5660cd2cc49697ed85f7c\n4. https://git.kernel.org/stable/c/67d15c7aa0864dfd82325c7e7e7d8548b5224c7b", "creation_timestamp": "2025-04-03T07:34:15.000000Z"}, {"uuid": "4091b615-89b9-4826-aea9-5ec2828da133", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22003", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10180", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22003\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncan: ucan: fix out of bound read in strscpy() source\n\nCommit 7fdaf8966aae (\"can: ucan: use strscpy() to instead of strncpy()\")\nunintentionally introduced a one byte out of bound read on strscpy()'s\nsource argument (which is kind of ironic knowing that strscpy() is meant\nto be a more secure alternative :)).\n\nLet's consider below buffers:\n\n  dest[len + 1]; /* will be NUL terminated */\n  src[len]; /* may not be NUL terminated */\n\nWhen doing:\n\n  strncpy(dest, src, len);\n  dest[len] = '\\0';\n\nstrncpy() will read up to len bytes from src.\n\nOn the other hand:\n\n  strscpy(dest, src, len + 1);\n\nwill read up to len + 1 bytes from src, that is to say, an out of bound\nread of one byte will occur on src if it is not NUL terminated. Note\nthat the src[len] byte is never copied, but strscpy() still needs to\nread it to check whether a truncation occurred or not.\n\nThis exact pattern happened in ucan.\n\nThe root cause is that the source is not NUL terminated. Instead of\ndoing a copy in a local buffer, directly NUL terminate it as soon as\nusb_control_msg() returns. With this, the local firmware_str[] variable\ncan be removed.\n\nOn top of this do a couple refactors:\n\n  - ucan_ctl_payload->raw is only used for the firmware string, so\n    rename it to ucan_ctl_payload->fw_str and change its type from u8 to\n    char.\n\n  - ucan_device_request_in() is only used to retrieve the firmware\n    string, so rename it to ucan_get_fw_str() and refactor it to make it\n    directly handle all the string termination logic.\n\ud83d\udccf Published: 2025-04-03T07:19:05.403Z\n\ud83d\udccf Modified: 2025-04-03T07:19:05.403Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cc29775a8a72d7f3b56cc026796ad99bd65804a7\n2. https://git.kernel.org/stable/c/8cec9e314d3360fc1d8346297c41a6ee45cb45a9\n3. https://git.kernel.org/stable/c/a4994161a61bc8fd71d105c579d847cefee99262\n4. https://git.kernel.org/stable/c/1d22a122ffb116c3cf78053e812b8b21f8852ee9", "creation_timestamp": "2025-04-03T07:34:11.000000Z"}, {"uuid": "bfa35180-cc79-42ce-8414-0f0827758437", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22004", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/10179", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22004\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: atm: fix use after free in lec_send()\n\nThe ->send() operation frees skb so save the length before calling\n->send() to avoid a use after free.\n\ud83d\udccf Published: 2025-04-03T07:19:06.022Z\n\ud83d\udccf Modified: 2025-04-03T07:19:06.022Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/51e8be9578a2e74f9983d8fd8de8cafed191f30c\n2. https://git.kernel.org/stable/c/9566f6ee13b17a15d0a47667ad1b1893c539f730\n3. https://git.kernel.org/stable/c/326223182e4703cde99fdbd36d07d0b3de9980fb\n4. https://git.kernel.org/stable/c/f3271f7548385e0096739965961c7cbf7e6b4762\n5. https://git.kernel.org/stable/c/f3009d0d6ab78053117f8857b921a8237f4d17b3", "creation_timestamp": "2025-04-03T07:34:10.000000Z"}, {"uuid": "a045d18f-0e2a-4159-9fa7-70a397ac56b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22005", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10178", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22005\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().\n\nfib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything\nwhen it fails.\n\nCommit 7dd73168e273 (\"ipv6: Always allocate pcpu memory in a fib6_nh\")\nmoved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()\nbut forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in\ncase it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.\n\nLet's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the\nerror path.\n\nNote that we can remove the fib6_nh_release() call in nh_create_ipv6()\nlater in net-next.git.\n\ud83d\udccf Published: 2025-04-03T07:19:06.716Z\n\ud83d\udccf Modified: 2025-04-03T07:19:06.716Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/77c41cdbe6bce476e08d3251c0d501feaf10a9f3\n2. https://git.kernel.org/stable/c/119dcafe36795a15ae53351cbbd6177aaf94ffef\n3. https://git.kernel.org/stable/c/29d91820184d5cbc70f3246d4911d96eaeb930d6\n4. https://git.kernel.org/stable/c/d3d5b4b5ae263c3225db363ba08b937e2e2b0380\n5. https://git.kernel.org/stable/c/9740890ee20e01f99ff1dde84c63dcf089fabb98", "creation_timestamp": "2025-04-03T07:34:09.000000Z"}, {"uuid": "f384e380-841a-45a0-856c-8ed92face381", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22006", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/10177", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22006\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: ti: am65-cpsw: Fix NAPI registration sequence\n\nRegistering the interrupts for TX or RX DMA Channels prior to registering\ntheir respective NAPI callbacks can result in a NULL pointer dereference.\nThis is seen in practice as a random occurrence since it depends on the\nrandomness associated with the generation of traffic by Linux and the\nreception of traffic from the wire.\n\ud83d\udccf Published: 2025-04-03T07:19:07.407Z\n\ud83d\udccf Modified: 2025-04-03T07:19:07.407Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d4bf956547c38c04fad8d72a961ac4dc00bad000\n2. https://git.kernel.org/stable/c/942557abed7f38b77a47d77b92d448802eefe185\n3. https://git.kernel.org/stable/c/5f079290e5913a0060e059500b7d440990ac1066", "creation_timestamp": "2025-04-03T07:34:08.000000Z"}, {"uuid": "263ba912-2f26-4959-9c5e-966058badb2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22007", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/10176", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22007\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix error code in chan_alloc_skb_cb()\n\nThe chan_alloc_skb_cb() function is supposed to return error pointers on\nerror.  Returning NULL will lead to a NULL dereference.\n\ud83d\udccf Published: 2025-04-03T07:19:07.986Z\n\ud83d\udccf Modified: 2025-04-03T07:19:07.986Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/788ae2ae4cf484e248b5bc29211c7ac6510e3e92\n2. https://git.kernel.org/stable/c/ecd06ad0823a90b4420c377ef8917e44e23ee841\n3. https://git.kernel.org/stable/c/761b7c36addd22c7e6ceb05caaadc3b062d99faa\n4. https://git.kernel.org/stable/c/a78692ec0d1e17a96b09f2349a028878f5b305e4\n5. https://git.kernel.org/stable/c/72d061ee630d0dbb45c2920d8d19b3861c413e54", "creation_timestamp": "2025-04-03T07:34:07.000000Z"}, {"uuid": "16acd5de-df65-4b89-9ce6-c24ac9dbfe2f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22000", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10182", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22000\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: drop beyond-EOF folios with the right number of refs\n\nWhen an after-split folio is large and needs to be dropped due to EOF,\nfolio_put_refs(folio, folio_nr_pages(folio)) should be used to drop all\npage cache refs.  Otherwise, the folio will not be freed, causing memory\nleak.\n\nThis leak would happen on a filesystem with blocksize > page_size and a\ntruncate is performed, where the blocksize makes folios split to >0 order\nones, causing truncated folios not being freed.\n\ud83d\udccf Published: 2025-04-03T07:19:03.652Z\n\ud83d\udccf Modified: 2025-04-03T07:19:03.652Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/86368616a9ce51f6b41efa251b6e066893851d67\n2. https://git.kernel.org/stable/c/92ad820a1f2d95d5a8d6c2bd3f391bbb068a5f9e\n3. https://git.kernel.org/stable/c/14efb4793519d73fb2902bb0ece319b886e4b4b9", "creation_timestamp": "2025-04-03T07:34:16.000000Z"}, {"uuid": "a805383d-ff35-4425-b905-77b60d325219", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2200", "type": "seen", "source": "https://t.me/cvedetector/20452", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-2200 - IcProgress Innovaci\u00f3n y Cualificaci\u00f3n SQL Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-2200 \nPublished : March 17, 2025, 10:15 a.m. | 1\u00a0hour, 23\u00a0minutes ago \nDescription : QL injection vulnerability in the IcProgreso Innovaci\u00f3n y Cualificaci\u00f3n plugin. This vulnerability allows an attacker to obtain, update and delete data from the database by injecting an SQL query on the parameters user, id, idGroup, start_date and end_date in the endpoint /report/icprogreso/generar_blocks.php. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-17T13:17:05.000000Z"}]}