{"vulnerability": "CVE-2024-4225", "sightings": [{"uuid": "0b0c02c0-6910-49ed-a08c-48db0f4888fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-42252", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "084b55f4-5805-4af3-a687-c761cd3a4ffc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-42253", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "b3e1e63d-ddf4-4dee-b463-056d59b5bd53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42257", "type": "seen", "source": "https://t.me/cvedetector/2771", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42257 - Linux Kernel - ext4 Memory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42257 \nPublished : Aug. 8, 2024, 9:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \next4: use memtostr_pad() for s_volume_name  \n  \nAs with the other strings in struct ext4_super_block, s_volume_name is  \nnot NUL terminated. The other strings were marked in commit 072ebb3bffe6  \n(\"ext4: add nonstring annotations to ext4.h\"). Using strscpy() isn't  \nthe right replacement for strncpy(); it should use memtostr_pad()  \ninstead. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T12:13:04.000000Z"}, {"uuid": "3e4157b3-f41e-48a6-90dc-1485147a2b5f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42258", "type": "seen", "source": "https://t.me/cvedetector/2852", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42258 - Linux kernel x86_32 Huge Page Alignment Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42258 \nPublished : Aug. 12, 2024, 3:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines  \n  \nYves-Alexis Perez reported commit 4ef9ad19e176 (\"mm: huge_memory: don't  \nforce huge page alignment on 32 bit\") didn't work for x86_32 [1].  It is  \nbecause x86_32 uses CONFIG_X86_32 instead of CONFIG_32BIT.  \n  \n!CONFIG_64BIT should cover all 32 bit machines.  \n  \n[1]  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"12 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-12T18:27:21.000000Z"}, {"uuid": "fe66483c-4d0e-4579-b8a8-4135f119725a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-42253", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "4f24515d-96ed-4c41-8e13-4403890f849e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42259", "type": "seen", "source": "https://t.me/cvedetector/3154", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42259 - Intel DRM Virtual Memory Mapping Boundary Calculation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42259 \nPublished : Aug. 14, 2024, 3:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/i915/gem: Fix Virtual Memory mapping boundaries calculation  \n  \nCalculating the size of the mapped area as the lesser value  \nbetween the requested size and the actual size does not consider  \nthe partial mapping offset. This can cause page fault access.  \n  \nFix the calculation of the starting and ending addresses, the  \ntotal size is now deduced from the difference between the end and  \nstart addresses.  \n  \nAdditionally, the calculations have been rewritten in a clearer  \nand more understandable form.  \n  \n[Joonas: Add Requires: tag]  \nRequires: 60a2066c5005 (\"drm/i915/gem: Adjust vma offset for framebuffer mmap offset\")  \n(cherry picked from commit 97b6784753da06d9d40232328efc5c5367e53417) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"14 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-14T18:13:30.000000Z"}, {"uuid": "3fa41ae0-9703-465b-985a-20c68e83d624", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42256", "type": "seen", "source": "https://t.me/cvedetector/2767", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42256 - \"CIFS Server Misaccounting Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-42256 \nPublished : Aug. 8, 2024, 9:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncifs: Fix server re-repick on subrequest retry  \n  \nWhen a subrequest is marked for needing retry, netfs will call  \ncifs_prepare_write() which will make cifs repick the server for the op  \nbefore renegotiating credits; it then calls cifs_issue_write() which  \ninvokes smb2_async_writev() - which re-repicks the server.  \n  \nIf a different server is then selected, this causes the increment of  \nserver->in_flight to happen against one record and the decrement to happen  \nagainst another, leading to misaccounting.  \n  \nFix this by just removing the repick code in smb2_async_writev().  As this  \nis only called from netfslib-driven code, cifs_prepare_write() should  \nalways have been called first, and so server should never be NULL and the  \npreparatory step is repeated in the event that we do a retry.  \n  \nThe problem manifests as a warning looking something like:  \n  \n WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs]  \n ...  \n RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs]  \n ...  \n  smb2_writev_callback+0x334/0x560 [cifs]  \n  cifs_demultiplex_thread+0x77a/0x11b0 [cifs]  \n  kthread+0x187/0x1d0  \n  ret_from_fork+0x34/0x60  \n  ret_from_fork_asm+0x1a/0x30  \n  \nWhich may be triggered by a number of different xfstests running against an  \nAzure server in multichannel mode.  generic/249 seems the most repeatable,  \nbut generic/215, generic/249 and generic/308 may also show it. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T12:12:57.000000Z"}, {"uuid": "32f04da8-ecf8-40da-a519-66fc82c317a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42251", "type": "seen", "source": "https://t.me/cvedetector/2765", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42251 - QEMU Linux kernel folio reference count CreateLogFile exploit\", \n  \"Content\": \"CVE ID : CVE-2024-42251 \nPublished : Aug. 8, 2024, 9:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm: page_ref: remove folio_try_get_rcu()  \n  \nThe below bug was reported on a non-SMP kernel:  \n  \n[  275.267158][ T4335] ------------[ cut here ]------------  \n[  275.267949][ T4335] kernel BUG at include/linux/page_ref.h:275!  \n[  275.268526][ T4335] invalid opcode: 0000 [#1] KASAN PTI  \n[  275.269001][ T4335] CPU: 0 PID: 4335 Comm: trinity-c3 Not tainted 6.7.0-rc4-00061-gefa7df3e3bb5 #1  \n[  275.269787][ T4335] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014  \n[  275.270679][ T4335] RIP: 0010:try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))  \n[  275.272813][ T4335] RSP: 0018:ffffc90005dcf650 EFLAGS: 00010202  \n[  275.273346][ T4335] RAX: 0000000000000246 RBX: ffffea00066e0000 RCX: 0000000000000000  \n[  275.274032][ T4335] RDX: fffff94000cdc007 RSI: 0000000000000004 RDI: ffffea00066e0034  \n[  275.274719][ T4335] RBP: ffffea00066e0000 R08: 0000000000000000 R09: fffff94000cdc006  \n[  275.275404][ T4335] R10: ffffea00066e0037 R11: 0000000000000000 R12: 0000000000000136  \n[  275.276106][ T4335] R13: ffffea00066e0034 R14: dffffc0000000000 R15: ffffea00066e0008  \n[  275.276790][ T4335] FS:  00007fa2f9b61740(0000) GS:ffffffff89d0d000(0000) knlGS:0000000000000000  \n[  275.277570][ T4335] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n[  275.278143][ T4335] CR2: 00007fa2f6c00000 CR3: 0000000134b04000 CR4: 00000000000406f0  \n[  275.278833][ T4335] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \n[  275.279521][ T4335] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \n[  275.280201][ T4335] Call Trace:  \n[  275.280499][ T4335]    \n[ 275.280751][ T4335] ? die (arch/x86/kernel/dumpstack.c:421 arch/x86/kernel/dumpstack.c:434 arch/x86/kernel/dumpstack.c:447)  \n[ 275.281087][ T4335] ? do_trap (arch/x86/kernel/traps.c:112 arch/x86/kernel/traps.c:153)  \n[ 275.281463][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))  \n[ 275.281884][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))  \n[ 275.282300][ T4335] ? do_error_trap (arch/x86/kernel/traps.c:174)  \n[ 275.282711][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))  \n[ 275.283129][ T4335] ? handle_invalid_op (arch/x86/kernel/traps.c:212)  \n[ 275.283561][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))  \n[ 275.283990][ T4335] ? exc_invalid_op (arch/x86/kernel/traps.c:264)  \n[ 275.284415][ T4335] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:568)  \n[ 275.284859][ T4335] ? try_get_folio (include/linux/page_ref.h:275 (discriminator 3) mm/gup.c:79 (discriminator 3))  \n[ 275.285278][ T4335] try_grab_folio (mm/gup.c:148)  \n[ 275.285684][ T4335] __get_user_pages (mm/gup.c:1297 (discriminator 1))  \n[ 275.286111][ T4335] ? __pfx___get_user_pages (mm/gup.c:1188)  \n[ 275.286579][ T4335] ? __pfx_validate_chain (kernel/locking/lockdep.c:3825)  \n[ 275.287034][ T4335] ? mark_lock (kernel/locking/lockdep.c:4656 (discriminator 1))  \n[ 275.287416][ T4335] __gup_longterm_locked (mm/gup.c:1509 mm/gup.c:2209)  \n[ 275.288192][ T4335] ? __pfx___gup_longterm_locked (mm/gup.c:2204)  \n[ 275.288697][ T4335] ? __pfx_lock_acquire (kernel/locking/lockdep.c:5722)  \n[ 275.289135][ T4335] ? __pfx___might_resched (kernel/sched/core.c:10106)  \n[ 275.289595][ T4335] pin_user_pages_remote (mm/gup.c:3350)  \n[ 275.290041][ T4335] ? __pfx_pin_user_pages_remote (mm/gup.c:3350)  \n[ 275.290545][ T4335] ? find_held_lock (kernel/locking/lockdep.c:5244 (discriminator 1))  \n[ 275.290961][ T4335] ? mm_access (kernel/fork.c:1573)  \n[ 275.291353][ T4[...]", "creation_timestamp": "2024-08-08T12:12:52.000000Z"}, {"uuid": "26685fe5-0a03-42e8-80fd-957d46cbbcc7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42252", "type": "seen", "source": "https://t.me/cvedetector/2764", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42252 - Linux kernel Closure Bug\", \n  \"Content\": \"CVE ID : CVE-2024-42252 \nPublished : Aug. 8, 2024, 9:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nclosures: Change BUG_ON() to WARN_ON()  \n  \nIf a BUG_ON() can be hit in the wild, it shouldn't be a BUG_ON()  \n  \nFor reference, this has popped up once in the CI, and we'll need more  \ninfo to debug it:  \n  \n03240 ------------[ cut here ]------------  \n03240 kernel BUG at lib/closure.c:21!  \n03240 kernel BUG at lib/closure.c:21!  \n03240 Internal error: Oops - BUG: 00000000f2000800 [#1] SMP  \n03240 Modules linked in:  \n03240 CPU: 15 PID: 40534 Comm: kworker/u80:1 Not tainted 6.10.0-rc4-ktest-ga56da69799bd #25570  \n03240 Hardware name: linux,dummy-virt (DT)  \n03240 Workqueue: btree_update btree_interior_update_work  \n03240 pstate: 00001005 (nzcv daif -PAN -UAO -TCO -DIT +SSBS BTYPE=--)  \n03240 pc : closure_put+0x224/0x2a0  \n03240 lr : closure_put+0x24/0x2a0  \n03240 sp : ffff0000d12071c0  \n03240 x29: ffff0000d12071c0 x28: dfff800000000000 x27: ffff0000d1207360  \n03240 x26: 0000000000000040 x25: 0000000000000040 x24: 0000000000000040  \n03240 x23: ffff0000c1f20180 x22: 0000000000000000 x21: ffff0000c1f20168  \n03240 x20: 0000000040000000 x19: ffff0000c1f20140 x18: 0000000000000001  \n03240 x17: 0000000000003aa0 x16: 0000000000003ad0 x15: 1fffe0001c326974  \n03240 x14: 0000000000000a1e x13: 0000000000000000 x12: 1fffe000183e402d  \n03240 x11: ffff6000183e402d x10: dfff800000000000 x9 : ffff6000183e402e  \n03240 x8 : 0000000000000001 x7 : 00009fffe7c1bfd3 x6 : ffff0000c1f2016b  \n03240 x5 : ffff0000c1f20168 x4 : ffff6000183e402e x3 : ffff800081391954  \n03240 x2 : 0000000000000001 x1 : 0000000000000000 x0 : 00000000a8000000  \n03240 Call trace:  \n03240  closure_put+0x224/0x2a0  \n03240  bch2_check_for_deadlock+0x910/0x1028  \n03240  bch2_six_check_for_deadlock+0x1c/0x30  \n03240  six_lock_slowpath.isra.0+0x29c/0xed0  \n03240  six_lock_ip_waiter+0xa8/0xf8  \n03240  __bch2_btree_node_lock_write+0x14c/0x298  \n03240  bch2_trans_lock_write+0x6d4/0xb10  \n03240  __bch2_trans_commit+0x135c/0x5520  \n03240  btree_interior_update_work+0x1248/0x1c10  \n03240  process_scheduled_works+0x53c/0xd90  \n03240  worker_thread+0x370/0x8c8  \n03240  kthread+0x258/0x2e8  \n03240  ret_from_fork+0x10/0x20  \n03240 Code: aa1303e0 d63f0020 a94363f7 17ffff8c (d4210000)  \n03240 ---[ end trace 0000000000000000 ]---  \n03240 Kernel panic - not syncing: Oops - BUG: Fatal exception  \n03240 SMP: stopping secondary CPUs  \n03241 SMP: failed to stop secondary CPUs 13,15  \n03241 Kernel Offset: disabled  \n03241 CPU features: 0x00,00000003,80000008,4240500b  \n03241 Memory Limit: none  \n03241 ---[ end Kernel panic - not syncing: Oops - BUG: Fatal exception ]---  \n03246 ========= FAILED TIMEOUT copygc_torture_no_checksum in 7200s \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T12:12:51.000000Z"}, {"uuid": "35481490-6af6-4070-b7bd-8bc903ad9546", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42253", "type": "seen", "source": "https://t.me/cvedetector/2763", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42253 - NXP pca953x GPIO Interrupt Latching Protocol Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42253 \nPublished : Aug. 8, 2024, 9:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ngpio: pca953x: fix pca953x_irq_bus_sync_unlock race  \n  \nEnsure that `i2c_lock' is held when setting interrupt latch and mask in  \npca953x_irq_bus_sync_unlock() in order to avoid races.  \n  \nThe other (non-probe) call site pca953x_gpio_set_multiple() ensures the  \nlock is held before calling pca953x_write_regs().  \n  \nThe problem occurred when a request raced against irq_bus_sync_unlock()  \napproximately once per thousand reboots on an i.MX8MP based system.  \n  \n * Normal case  \n  \n   0-0022: write register AI|3a {03,02,00,00,01} Input latch P0  \n   0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0  \n   0-0022: write register AI|08 {ff,00,00,00,00} Output P3  \n   0-0022: write register AI|12 {fc,00,00,00,00} Config P3  \n  \n * Race case  \n  \n   0-0022: write register AI|08 {ff,00,00,00,00} Output P3  \n   0-0022: write register AI|08 {03,02,00,00,01} *** Wrong register ***  \n   0-0022: write register AI|12 {fc,00,00,00,00} Config P3  \n   0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T12:12:50.000000Z"}, {"uuid": "d492dfbf-7349-4730-bd82-5801cc4d9a41", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42255", "type": "seen", "source": "https://t.me/cvedetector/2762", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42255 - \"TPM NULL Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-42255 \nPublished : Aug. 8, 2024, 9:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntpm: Use auth only after NULL check in tpm_buf_check_hmac_response()  \n  \nDereference auth after NULL check in tpm_buf_check_hmac_response().  \nOtherwise, unless tpm2_sessions_init() was called, a call can cause NULL  \ndereference, when TCG_TPM2_HMAC is enabled.  \n  \n[jarkko: adjusted the commit message.] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T12:12:49.000000Z"}, {"uuid": "94a1d6fb-2205-4f4d-9fb2-d0d471940963", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42254", "type": "seen", "source": "https://t.me/cvedetector/2761", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42254 - Linux io_uring Null Pointer Dereference Denial of Service Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42254 \nPublished : Aug. 8, 2024, 9:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring: fix error pbuf checking  \n  \nSyz reports a problem, which boils down to NULL vs IS_ERR inconsistent  \nerror handling in io_alloc_pbuf_ring().  \n  \nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]  \nRIP: 0010:__io_remove_buffers+0xac/0x700 io_uring/kbuf.c:341  \nCall Trace:  \n   \n io_put_bl io_uring/kbuf.c:378 [inline]  \n io_destroy_buffers+0x14e/0x490 io_uring/kbuf.c:392  \n io_ring_ctx_free+0xa00/0x1070 io_uring/io_uring.c:2613  \n io_ring_exit_work+0x80f/0x8a0 io_uring/io_uring.c:2844  \n process_one_work kernel/workqueue.c:3231 [inline]  \n process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312  \n worker_thread+0x86d/0xd40 kernel/workqueue.c:3390  \n kthread+0x2f0/0x390 kernel/kthread.c:389  \n ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147  \n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T12:12:48.000000Z"}, {"uuid": "b805b460-7363-467b-a492-731aa86dde1c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-4225", "type": "seen", "source": "Telegram/pz7HydA40Np-_jUvgVr4aTlp-3PHM_xQ0C-Xyl-TvMGevQTM", "content": "", "creation_timestamp": "2024-04-30T13:41:51.000000Z"}, {"uuid": "67798c9c-d39b-4322-b9d2-b495d6b73e8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42250", "type": "seen", "source": "https://t.me/cvedetector/2699", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42250 - Apache Linux Kernel RCU Lock Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42250 \nPublished : Aug. 7, 2024, 4:15 p.m. | 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncachefiles: add missing lock protection when polling  \n  \nAdd missing lock protection in poll routine when iterating xarray,  \notherwise:  \n  \nEven with RCU read lock held, only the slot of the radix tree is  \nensured to be pinned there, while the data structure (e.g. struct  \ncachefiles_req) stored in the slot has no such guarantee.  The poll  \nroutine will iterate the radix tree and dereference cachefiles_req  \naccordingly.  Thus RCU read lock is not adequate in this case and  \nspinlock is needed here. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-07T18:38:34.000000Z"}]}