https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Mon, 15 Jun 2026 08:06:54 +0000 https://vulnerability.circl.lu/sighting/4785ed82-8236-4237-b9e3-ec33b03e3973/export {"uuid": "4785ed82-8236-4237-b9e3-ec33b03e3973", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22014", "type": "seen", "source": "https://t.me/cvedetector/22451", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22014 - Linux Kernel Qcom PDR Deadlock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-22014 \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 \nsoc: qcom: pdr: Fix the potential deadlock \n \nWhen some client process A call pdr_add_lookup() to add the look up for \nthe service and does schedule locator work, later a process B got a new \nserver packet indicating locator is up and call pdr_locator_new_server() \nwhich eventually sets pdr->locator_init_complete to true which process A \nsees and takes list lock and queries domain list but it will timeout due \nto deadlock as the response will queued to the same qmi->wq and it is \nordered workqueue and process B is not able to complete new server \nrequest work due to deadlock on list lock. \n \nFix it by removing the unnecessary list iteration as the list iteration \nis already being done inside locator work, so avoid it here and just \ncall schedule_work() here. \n \n Process A Process B \n \n process_scheduled_works() \npdr_add_lookup() qmi_data_ready_work() \n process_scheduled_works() pdr_locator_new_server() \n pdr->locator_init_complete=true; \n pdr_locator_work() \n mutex_lock(&pdr->list_lock); \n \n pdr_locate_service() mutex_lock(&pdr->list_lock); \n \n pdr_get_domain_list() \n pr_err(\"PDR: %s get domain list \n txn wait failed: %d\\n\", \n req->service_name, \n ret); \n \nTimeout error log due to deadlock: \n \n\" \n PDR: tms/servreg get domain list txn wait failed: -110 \n PDR: service lookup for msm/adsp/sensor_pd:tms/servreg failed: -110 \n\" \n \nThanks to Bjorn and Johan for letting me know that this commit also fixes \nan audio regression when using the in-kernel pd-mapper as that makes it \neasier to hit this race. [1] \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:03.000000Z"} {"uuid": "4785ed82-8236-4237-b9e3-ec33b03e3973", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22014", "type": "seen", "source": "https://t.me/cvedetector/22451", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22014 - Linux Kernel Qcom PDR Deadlock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-22014 \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 \nsoc: qcom: pdr: Fix the potential deadlock \n \nWhen some client process A call pdr_add_lookup() to add the look up for \nthe service and does schedule locator work, later a process B got a new \nserver packet indicating locator is up and call pdr_locator_new_server() \nwhich eventually sets pdr->locator_init_complete to true which process A \nsees and takes list lock and queries domain list but it will timeout due \nto deadlock as the response will queued to the same qmi->wq and it is \nordered workqueue and process B is not able to complete new server \nrequest work due to deadlock on list lock. \n \nFix it by removing the unnecessary list iteration as the list iteration \nis already being done inside locator work, so avoid it here and just \ncall schedule_work() here. \n \n Process A Process B \n \n process_scheduled_works() \npdr_add_lookup() qmi_data_ready_work() \n process_scheduled_works() pdr_locator_new_server() \n pdr->locator_init_complete=true; \n pdr_locator_work() \n mutex_lock(&pdr->list_lock); \n \n pdr_locate_service() mutex_lock(&pdr->list_lock); \n \n pdr_get_domain_list() \n pr_err(\"PDR: %s get domain list \n txn wait failed: %d\\n\", \n req->service_name, \n ret); \n \nTimeout error log due to deadlock: \n \n\" \n PDR: tms/servreg get domain list txn wait failed: -110 \n PDR: service lookup for msm/adsp/sensor_pd:tms/servreg failed: -110 \n\" \n \nThanks to Bjorn and Johan for letting me know that this commit also fixes \nan audio regression when using the in-kernel pd-mapper as that makes it \neasier to hit this race. [1] \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:03.000000Z"} https://vulnerability.circl.lu/sighting/4785ed82-8236-4237-b9e3-ec33b03e3973/export Tue, 08 Apr 2025 14:00:03 +0000 https://vulnerability.circl.lu/sighting/ccd416a3-8186-4534-8425-eb83771bb7ae/export {"uuid": "ccd416a3-8186-4534-8425-eb83771bb7ae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22017", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3lmnyh2gblc2h", "content": "", "creation_timestamp": "2025-04-13T02:22:10.101543Z"} {"uuid": "ccd416a3-8186-4534-8425-eb83771bb7ae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22017", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3lmnyh2gblc2h", "content": "", "creation_timestamp": "2025-04-13T02:22:10.101543Z"} https://vulnerability.circl.lu/sighting/ccd416a3-8186-4534-8425-eb83771bb7ae/export Sun, 13 Apr 2025 02:22:10 +0000 https://vulnerability.circl.lu/sighting/fa2f3f01-43aa-4f10-85ab-95009894a088/export {"uuid": "fa2f3f01-43aa-4f10-85ab-95009894a088", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22018", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lmvyq6oj6e2a", "content": "", "creation_timestamp": "2025-04-16T06:48:30.845784Z"} {"uuid": "fa2f3f01-43aa-4f10-85ab-95009894a088", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22018", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lmvyq6oj6e2a", "content": "", "creation_timestamp": "2025-04-16T06:48:30.845784Z"} https://vulnerability.circl.lu/sighting/fa2f3f01-43aa-4f10-85ab-95009894a088/export Wed, 16 Apr 2025 06:48:30 +0000 https://vulnerability.circl.lu/sighting/806433d5-b834-412e-a30a-e9c8e38cba0f/export {"uuid": "806433d5-b834-412e-a30a-e9c8e38cba0f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22018", "type": "seen", "source": "https://t.me/cvedetector/23055", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22018 - Linux ATM NULL Pointer Dereference Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-22018 \nPublished : April 16, 2025, 5:15 a.m. | 2\u00a0hours, 12\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \natm: Fix NULL pointer dereference \n \nWhen MPOA_cache_impos_rcvd() receives the msg, it can trigger \nNull Pointer Dereference Vulnerability if both entry and \nholding_time are NULL. Because there is only for the situation \nwhere entry is NULL and holding_time exists, it can be passed \nwhen both entry and holding_time are NULL. If these are NULL, \nthe entry will be passd to eg_cache_put() as parameter and \nit is referenced by entry->use code in it. \n \nkasan log: \n \n[ 3.316691] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006:I \n[ 3.317568] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] \n[ 3.318188] CPU: 3 UID: 0 PID: 79 Comm: ex Not tainted 6.14.0-rc2 #102 \n[ 3.318601] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 \n[ 3.319298] RIP: 0010:eg_cache_remove_entry+0xa5/0x470 \n[ 3.319677] Code: c1 f7 6e fd 48 c7 c7 00 7e 38 b2 e8 95 64 54 fd 48 c7 c7 40 7e 38 b2 48 89 ee e80 \n[ 3.321220] RSP: 0018:ffff88800583f8a8 EFLAGS: 00010006 \n[ 3.321596] RAX: 0000000000000006 RBX: ffff888005989000 RCX: ffffffffaecc2d8e \n[ 3.322112] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000030 \n[ 3.322643] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff6558b88 \n[ 3.323181] R10: 0000000000000003 R11: 203a207972746e65 R12: 1ffff11000b07f15 \n[ 3.323707] R13: dffffc0000000000 R14: ffff888005989000 R15: ffff888005989068 \n[ 3.324185] FS: 000000001b6313c0(0000) GS:ffff88806d380000(0000) knlGS:0000000000000000 \n[ 3.325042] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n[ 3.325545] CR2: 00000000004b4b40 CR3: 000000000248e000 CR4: 00000000000006f0 \n[ 3.326430] Call Trace: \n[ 3.326725] \n[ 3.326927] ? die_addr+0x3c/0xa0 \n[ 3.327330] ? exc_general_protection+0x161/0x2a0 \n[ 3.327662] ? asm_exc_general_protection+0x26/0x30 \n[ 3.328214] ? vprintk_emit+0x15e/0x420 \n[ 3.328543] ? eg_cache_remove_entry+0xa5/0x470 \n[ 3.328910] ? eg_cache_remove_entry+0x9a/0x470 \n[ 3.329294] ? __pfx_eg_cache_remove_entry+0x10/0x10 \n[ 3.329664] ? console_unlock+0x107/0x1d0 \n[ 3.329946] ? __pfx_console_unlock+0x10/0x10 \n[ 3.330283] ? do_syscall_64+0xa6/0x1a0 \n[ 3.330584] ? entry_SYSCALL_64_after_hwframe+0x47/0x7f \n[ 3.331090] ? __pfx_prb_read_valid+0x10/0x10 \n[ 3.331395] ? down_trylock+0x52/0x80 \n[ 3.331703] ? vprintk_emit+0x15e/0x420 \n[ 3.331986] ? __pfx_vprintk_emit+0x10/0x10 \n[ 3.332279] ? down_trylock+0x52/0x80 \n[ 3.332527] ? _printk+0xbf/0x100 \n[ 3.332762] ? __pfx__printk+0x10/0x10 \n[ 3.333007] ? _raw_write_lock_irq+0x81/0xe0 \n[ 3.333284] ? __pfx__raw_write_lock_irq+0x10/0x10 \n[ 3.333614] msg_from_mpoad+0x1185/0x2750 \n[ 3.333893] ? __build_skb_around+0x27b/0x3a0 \n[ 3.334183] ? __pfx_msg_from_mpoad+0x10/0x10 \n[ 3.334501] ? __alloc_skb+0x1c0/0x310 \n[ 3.334809] ? __pfx___alloc_skb+0x10/0x10 \n[ 3.335283] ? _raw_spin_lock+0xe0/0xe0 \n[ 3.335632] ? finish_wait+0x8d/0x1e0 \n[ 3.335975] vcc_sendmsg+0x684/0xba0 \n[ 3.336250] ? __pfx_vcc_sendmsg+0x10/0x10 \n[ 3.336587] ? __pfx_autoremove_wake_function+0x10/0x10 \n[ 3.337056] ? fdget+0x176/0x3e0 \n[ 3.337348] __sys_sendto+0x4a2/0x510 \n[ 3.337663] ? __pfx___sys_sendto+0x10/0x10 \n[ 3.337969] ? ioctl_has_perm.constprop.0.isra.0+0x284/0x400 \n[ 3.338364] ? sock_ioctl+0x1bb/0x5a0 \n[ 3.338653] ? __rseq_handle_notify_resume+0x825/0xd20 \n[ 3.339017] ? __pfx_sock_ioctl+0x10/0x10 \n[ 3.339316] ? __pfx___rseq_handle_notify_resume+0x10/0x10 \n[ 3.339727] ? selinux_file_ioctl+0xa4/0x260 \n[ 3.340166] __x64_sys_sendto+0xe0/0x1c0 \n[[...]", "creation_timestamp": "2025-04-16T10:10:34.000000Z"} {"uuid": "806433d5-b834-412e-a30a-e9c8e38cba0f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22018", "type": "seen", "source": "https://t.me/cvedetector/23055", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22018 - Linux ATM NULL Pointer Dereference Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-22018 \nPublished : April 16, 2025, 5:15 a.m. | 2\u00a0hours, 12\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \natm: Fix NULL pointer dereference \n \nWhen MPOA_cache_impos_rcvd() receives the msg, it can trigger \nNull Pointer Dereference Vulnerability if both entry and \nholding_time are NULL. Because there is only for the situation \nwhere entry is NULL and holding_time exists, it can be passed \nwhen both entry and holding_time are NULL. If these are NULL, \nthe entry will be passd to eg_cache_put() as parameter and \nit is referenced by entry->use code in it. \n \nkasan log: \n \n[ 3.316691] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006:I \n[ 3.317568] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] \n[ 3.318188] CPU: 3 UID: 0 PID: 79 Comm: ex Not tainted 6.14.0-rc2 #102 \n[ 3.318601] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 \n[ 3.319298] RIP: 0010:eg_cache_remove_entry+0xa5/0x470 \n[ 3.319677] Code: c1 f7 6e fd 48 c7 c7 00 7e 38 b2 e8 95 64 54 fd 48 c7 c7 40 7e 38 b2 48 89 ee e80 \n[ 3.321220] RSP: 0018:ffff88800583f8a8 EFLAGS: 00010006 \n[ 3.321596] RAX: 0000000000000006 RBX: ffff888005989000 RCX: ffffffffaecc2d8e \n[ 3.322112] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000030 \n[ 3.322643] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff6558b88 \n[ 3.323181] R10: 0000000000000003 R11: 203a207972746e65 R12: 1ffff11000b07f15 \n[ 3.323707] R13: dffffc0000000000 R14: ffff888005989000 R15: ffff888005989068 \n[ 3.324185] FS: 000000001b6313c0(0000) GS:ffff88806d380000(0000) knlGS:0000000000000000 \n[ 3.325042] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n[ 3.325545] CR2: 00000000004b4b40 CR3: 000000000248e000 CR4: 00000000000006f0 \n[ 3.326430] Call Trace: \n[ 3.326725] \n[ 3.326927] ? die_addr+0x3c/0xa0 \n[ 3.327330] ? exc_general_protection+0x161/0x2a0 \n[ 3.327662] ? asm_exc_general_protection+0x26/0x30 \n[ 3.328214] ? vprintk_emit+0x15e/0x420 \n[ 3.328543] ? eg_cache_remove_entry+0xa5/0x470 \n[ 3.328910] ? eg_cache_remove_entry+0x9a/0x470 \n[ 3.329294] ? __pfx_eg_cache_remove_entry+0x10/0x10 \n[ 3.329664] ? console_unlock+0x107/0x1d0 \n[ 3.329946] ? __pfx_console_unlock+0x10/0x10 \n[ 3.330283] ? do_syscall_64+0xa6/0x1a0 \n[ 3.330584] ? entry_SYSCALL_64_after_hwframe+0x47/0x7f \n[ 3.331090] ? __pfx_prb_read_valid+0x10/0x10 \n[ 3.331395] ? down_trylock+0x52/0x80 \n[ 3.331703] ? vprintk_emit+0x15e/0x420 \n[ 3.331986] ? __pfx_vprintk_emit+0x10/0x10 \n[ 3.332279] ? down_trylock+0x52/0x80 \n[ 3.332527] ? _printk+0xbf/0x100 \n[ 3.332762] ? __pfx__printk+0x10/0x10 \n[ 3.333007] ? _raw_write_lock_irq+0x81/0xe0 \n[ 3.333284] ? __pfx__raw_write_lock_irq+0x10/0x10 \n[ 3.333614] msg_from_mpoad+0x1185/0x2750 \n[ 3.333893] ? __build_skb_around+0x27b/0x3a0 \n[ 3.334183] ? __pfx_msg_from_mpoad+0x10/0x10 \n[ 3.334501] ? __alloc_skb+0x1c0/0x310 \n[ 3.334809] ? __pfx___alloc_skb+0x10/0x10 \n[ 3.335283] ? _raw_spin_lock+0xe0/0xe0 \n[ 3.335632] ? finish_wait+0x8d/0x1e0 \n[ 3.335975] vcc_sendmsg+0x684/0xba0 \n[ 3.336250] ? __pfx_vcc_sendmsg+0x10/0x10 \n[ 3.336587] ? __pfx_autoremove_wake_function+0x10/0x10 \n[ 3.337056] ? fdget+0x176/0x3e0 \n[ 3.337348] __sys_sendto+0x4a2/0x510 \n[ 3.337663] ? __pfx___sys_sendto+0x10/0x10 \n[ 3.337969] ? ioctl_has_perm.constprop.0.isra.0+0x284/0x400 \n[ 3.338364] ? sock_ioctl+0x1bb/0x5a0 \n[ 3.338653] ? __rseq_handle_notify_resume+0x825/0xd20 \n[ 3.339017] ? __pfx_sock_ioctl+0x10/0x10 \n[ 3.339316] ? __pfx___rseq_handle_notify_resume+0x10/0x10 \n[ 3.339727] ? selinux_file_ioctl+0xa4/0x260 \n[ 3.340166] __x64_sys_sendto+0xe0/0x1c0 \n[[...]", "creation_timestamp": "2025-04-16T10:10:34.000000Z"} https://vulnerability.circl.lu/sighting/806433d5-b834-412e-a30a-e9c8e38cba0f/export Wed, 16 Apr 2025 10:10:34 +0000 https://vulnerability.circl.lu/sighting/b5314974-021e-4d01-b4b6-eb08a4d876a3/export {"uuid": "b5314974-021e-4d01-b4b6-eb08a4d876a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22019", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12010", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22019\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbcachefs: bch2_ioctl_subvolume_destroy() fixes\n\nbch2_evict_subvolume_inodes() was getting stuck - due to incorrectly\npruning the dcache.\n\nAlso, fix missing permissions checks.\n\ud83d\udccf Published: 2025-04-16T10:20:36.342Z\n\ud83d\udccf Modified: 2025-04-16T10:20:36.342Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/9e6e83e1e2d01b99e70cd7812d7f758a8def9fc8\n2. https://git.kernel.org/stable/c/82383abd39abd635511b8956284a5cc8134c4dc1\n3. https://git.kernel.org/stable/c/558317a5c61045d460a37372181e7b43c0c002bb\n4. https://git.kernel.org/stable/c/707549600c4a012ed71c0204a7992a679880bf33", "creation_timestamp": "2025-04-16T10:55:57.000000Z"} {"uuid": "b5314974-021e-4d01-b4b6-eb08a4d876a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22019", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12010", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22019\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbcachefs: bch2_ioctl_subvolume_destroy() fixes\n\nbch2_evict_subvolume_inodes() was getting stuck - due to incorrectly\npruning the dcache.\n\nAlso, fix missing permissions checks.\n\ud83d\udccf Published: 2025-04-16T10:20:36.342Z\n\ud83d\udccf Modified: 2025-04-16T10:20:36.342Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/9e6e83e1e2d01b99e70cd7812d7f758a8def9fc8\n2. https://git.kernel.org/stable/c/82383abd39abd635511b8956284a5cc8134c4dc1\n3. https://git.kernel.org/stable/c/558317a5c61045d460a37372181e7b43c0c002bb\n4. https://git.kernel.org/stable/c/707549600c4a012ed71c0204a7992a679880bf33", "creation_timestamp": "2025-04-16T10:55:57.000000Z"} https://vulnerability.circl.lu/sighting/b5314974-021e-4d01-b4b6-eb08a4d876a3/export Wed, 16 Apr 2025 10:55:57 +0000 https://vulnerability.circl.lu/sighting/d1c5e6bc-1a1a-412e-802f-d60b4258d6ba/export {"uuid": "d1c5e6bc-1a1a-412e-802f-d60b4258d6ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22019", "type": "seen", "source": "https://t.me/cvedetector/23071", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22019 - bcachefs Denial of Service and Privilege Escalation\", \n \"Content\": \"CVE ID : CVE-2025-22019 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbcachefs: bch2_ioctl_subvolume_destroy() fixes \n \nbch2_evict_subvolume_inodes() was getting stuck - due to incorrectly \npruning the dcache. \n \nAlso, fix missing permissions checks. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T13:31:22.000000Z"} {"uuid": "d1c5e6bc-1a1a-412e-802f-d60b4258d6ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22019", "type": "seen", "source": "https://t.me/cvedetector/23071", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-22019 - bcachefs Denial of Service and Privilege Escalation\", \n \"Content\": \"CVE ID : CVE-2025-22019 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbcachefs: bch2_ioctl_subvolume_destroy() fixes \n \nbch2_evict_subvolume_inodes() was getting stuck - due to incorrectly \npruning the dcache. \n \nAlso, fix missing permissions checks. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T13:31:22.000000Z"} https://vulnerability.circl.lu/sighting/d1c5e6bc-1a1a-412e-802f-d60b4258d6ba/export Wed, 16 Apr 2025 13:31:22 +0000 https://vulnerability.circl.lu/sighting/98716010-d3bf-48c0-bdd2-4ade3271ac25/export {"uuid": "98716010-d3bf-48c0-bdd2-4ade3271ac25", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22018", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3lnafpwdvic2b", "content": "", "creation_timestamp": "2025-04-20T10:07:40.437384Z"} {"uuid": "98716010-d3bf-48c0-bdd2-4ade3271ac25", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22018", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3lnafpwdvic2b", "content": "", "creation_timestamp": "2025-04-20T10:07:40.437384Z"} https://vulnerability.circl.lu/sighting/98716010-d3bf-48c0-bdd2-4ade3271ac25/export Sun, 20 Apr 2025 10:07:40 +0000 https://vulnerability.circl.lu/sighting/40cfe290-4bd4-4736-9736-117c0cf4e9bc/export {"uuid": "40cfe290-4bd4-4736-9736-117c0cf4e9bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2201", "type": "seen", "source": "MISP/682bdba3-46b7-4a8f-b7be-c6bf4b4f9868", "content": "", "creation_timestamp": "2025-08-13T13:26:35.000000Z"} {"uuid": "40cfe290-4bd4-4736-9736-117c0cf4e9bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2201", "type": "seen", "source": "MISP/682bdba3-46b7-4a8f-b7be-c6bf4b4f9868", "content": "", "creation_timestamp": "2025-08-13T13:26:35.000000Z"} https://vulnerability.circl.lu/sighting/40cfe290-4bd4-4736-9736-117c0cf4e9bc/export Wed, 13 Aug 2025 13:26:35 +0000 https://vulnerability.circl.lu/sighting/ac7e7ff9-d01b-4b25-aa5b-301b293d15de/export {"uuid": "ac7e7ff9-d01b-4b25-aa5b-301b293d15de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-22010", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "ac7e7ff9-d01b-4b25-aa5b-301b293d15de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-22010", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://vulnerability.circl.lu/sighting/ac7e7ff9-d01b-4b25-aa5b-301b293d15de/export Wed, 03 Dec 2025 14:14:49 +0000 https://vulnerability.circl.lu/sighting/f944d3e0-d1f4-496b-8334-0f3007414ae1/export {"uuid": "f944d3e0-d1f4-496b-8334-0f3007414ae1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22019", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "f944d3e0-d1f4-496b-8334-0f3007414ae1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22019", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://vulnerability.circl.lu/sighting/f944d3e0-d1f4-496b-8334-0f3007414ae1/export Thu, 19 Mar 2026 00:00:00 +0000