Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
rnel.org/stable/c/55e06850c7894f00d41b767c5f5665459f83f58f - https://git.kernel.org/stable/c/84c6aa0ae5c4dc121f9996bb8fed46c80909d80e - https://git.kernel.org/stable/c/217efe32a45249eb07dcd7197e8403de98345e66 - https://git.kernel.org/stable/c/becf5c147198f4345243c5df0c4f035415491640 - https://git.kernel.org/stable/c/f990874b1c98fe8e57ee9385669f501822979258
CVE ID: CVE-2023-52511 State: PUBLISHED Published: 2024-03-02T21:52:23.277Z Last Updated: 2025-05-04T07:38:18.916Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: reduce DMA RX transfer width to single byte Through empirical testing it has been determined that sometimes RX SPI transfers with DMA enabled return corrupted data. This is down to single or even multiple bytes lost during DMA transfer from SPI peripheral to memory. It seems the RX FIFO within the SPI peripheral can become confused when performing bus read accesses wider than a single byte to it during an active SPI transfer. This patch reduces the width of
rforming bus read accesses wider than a single byte to it during an active SPI transfer. This patch reduces the width of individual DMA read accesses to the RX FIFO to a single byte to mitigate that issue. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/ff05ed4ae214011464a0156f05cac1b0b46b5fbc - https://git.kernel.org/stable/c/e15bb292b24630ee832bfc7fd616bd72c7682bbb - https://git.kernel.org/stable/c/b3c21c9c7289692f4019f163c3b06d8bdf78b355 - https://git.kernel.org/stable/c/171f8a49f212e87a8b04087568e1b3d132e36a18
CVE ID: CVE-2023-52512 State: PUBLISHED Published: 2024-03-02T21:52:23.932Z Last Updated: 2025-05-04T07:38:20.046Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pinctrl: nuvoton: wpcm450: fix out of bounds write Write into 'pctrl->gpio_bank' happens before the check for GPIO index validity, so out of bounds write may happen. Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/6c18c386fd13dbb3ff31a1086dabb526780d9bda - https://git.kernel.org/stable/c/c9d7cac0fd27c74dd368e80dc4b5d0f9f2e13cf8 - h
/6c18c386fd13dbb3ff31a1086dabb526780d9bda - https://git.kernel.org/stable/c/c9d7cac0fd27c74dd368e80dc4b5d0f9f2e13cf8 - https://git.kernel.org/stable/c/87d315a34133edcb29c4cadbf196ec6c30dfd47b
CVE ID: CVE-2023-52513 State: PUBLISHED Published: 2024-03-02T21:52:24.587Z Last Updated: 2025-05-04T07:38:21.171Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix connection failure handling In case immediate MPA request processing fails, the newly created endpoint unlinks the listening endpoint and is ready to be dropped. This special case was not handled correctly by the code handling the later TCP socket close, causing a NULL dereference crash in siw_cm_work_handler() when dereferencing a NULL listener. We now also cancel the useless MPA timeout, if immediate MPA request processing fails. This patch furthermore
listener. We now also cancel the useless MPA timeout, if immediate MPA request processing fails. This patch furthermore simplifies MPA processing in general: Scheduling a useless TCP socket read in sk_data_ready() upcall is now surpressed, if the socket is already moved out of TCP_ESTABLISHED state. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/6e26812e289b374c17677d238164a5a8f5770594 - https://git.kernel.org/stable/c/0d520cdb0cd095eac5d00078dfd318408c9b5eed - https://git.kernel.org/stable/c/81b7bf367eea795d259d0261710c6a89f548844d - https://git.kernel.org/stable/c/5cf38e638e5d01b68f9133968a85e8b3fd1ecf2f - https://g
67eea795d259d0261710c6a89f548844d - https://git.kernel.org/stable/c/5cf38e638e5d01b68f9133968a85e8b3fd1ecf2f - https://git.kernel.org/stable/c/eeafc50a77f6a783c2c44e7ec3674a7b693e06f8 - https://git.kernel.org/stable/c/53a3f777049771496f791504e7dc8ef017cba590
CVE ID: CVE-2023-52514 State: REJECTED Published: 2024-03-02T21:52:25.221Z Last Updated: 2024-03-11T16:11:44.266Z Description: No description available.
CVE ID: CVE-2023-52515 State: PUBLISHED Published: 2024-03-02T21:52:25.863Z Last Updated: 2025-05-04T12:49:08.091Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/srp: Do not call scsi_done() from srp_abort() After scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler callback, it performs one of the following actions: * Call scsi_queue_insert(). * Call scsi_finish_command(). * Call scsi_eh_scmd_add(). Hence, SCSI abort handlers must not call scsi_done(). Otherwise all the above actions would trigger a use-after-free. Hence remove the scsi_done() call from srp_abort(). Keep the srp_free_req() call before returnin
igger a use-after-free. Hence remove the scsi_done() call from srp_abort(). Keep the srp_free_req() call before returning SUCCESS because we may not see the command again if SUCCESS is returned. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/26788a5b48d9d5cd3283d777d238631c8cd7495a - https://git.kernel.org/stable/c/b9bdffb3f9aaeff8379c83f5449c6b42cb71c2b5 - https://git.kernel.org/stable/c/2b298f9181582270d5e95774e5a6c7a7fb5b1206 - https://git.kernel.org/stable/c/05a10b316adaac1f322007ca9a0383b410d759cc - https://git.kernel.org/stable/c/e193b7955dfad68035b983a0011f4ef3590c85eb
CVE ID: CVE-2023-52516 State: PUBLISHED Published: 2024-03-02T21:52:26.517Z Last Updated: 2025-05-04T07:38:23.724Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dma-debug: don't call __dma_entry_alloc_check_leak() under free_entries_lock __dma_entry_alloc_check_leak() calls into printk -> serial console output (qcom geni) and grabs port->lock under free_entries_lock spin lock, which is a reverse locking dependency chain as qcom_geni IRQ handler can call into dma-debug code and grab free_entries_lock under port->lock. Move __dma_entry_alloc_check_leak() call out of free_entries_lock scope so that we don't acquire serial console
t->lock. Move __dma_entry_alloc_check_leak() call out of free_entries_lock scope so that we don't acquire serial console's port->lock under it. Trimmed-down lockdep splat: The existing dependency chain (in reverse order) is: -> #2 (free_entries_lock){-.-.}-{2:2}: _raw_spin_lock_irqsave+0x60/0x80 dma_entry_alloc+0x38/0x110 debug_dma_map_page+0x60/0xf8 dma_map_page_attrs+0x1e0/0x230 dma_map_single_attrs.constprop.0+0x6c/0xc8 geni_se_rx_dma_prep+0x40/0xcc qcom_geni_serial_isr+0x310/0x510 __handle_irq_event_percpu+0x110/0x244 handle_irq_event_percpu+0x20/0x54 handle_irq_event+0x50/0x88 handle_fasteoi_irq+0xa4/0xcc handle_irq_desc+0x28/0x40 generic_handle_domain_irq+0x24/0x30 gic_handle_irq+0xc4/
x50/0x88 handle_fasteoi_irq+0xa4/0xcc handle_irq_desc+0x28/0x40 generic_handle_domain_irq+0x24/0x30 gic_handle_irq+0xc4/0x148 do_interrupt_handler+0xa4/0xb0 el1_interrupt+0x34/0x64 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x64/0x68 arch_local_irq_enable+0x4/0x8 ____do_softirq+0x18/0x24 ... -> #1 (&port_lock_key){-.-.}-{2:2}: _raw_spin_lock_irqsave+0x60/0x80 qcom_geni_serial_console_write+0x184/0x1dc console_flush_all+0x344/0x454 console_unlock+0x94/0xf0 vprintk_emit+0x238/0x24c vprintk_default+0x3c/0x48 vprintk+0xb4/0xbc _printk+0x68/0x90 register_console+0x230/0x38c uart_add_one_port+0x338/0x494 qcom_geni_serial_probe+0x390/0x424 platform_probe+0x70/0xc0 really_probe+0x148/0x280 __driver_p
add_one_port+0x338/0x494 qcom_geni_serial_probe+0x390/0x424 platform_probe+0x70/0xc0 really_probe+0x148/0x280 __driver_probe_device+0xfc/0x114 driver_probe_device+0x44/0x100 __device_attach_driver+0x64/0xdc bus_for_each_drv+0xb0/0xd8 __device_attach+0xe4/0x140 device_initial_probe+0x1c/0x28 bus_probe_device+0x44/0xb0 device_add+0x538/0x668 of_device_add+0x44/0x50 of_platform_device_create_pdata+0x94/0xc8 of_platform_bus_create+0x270/0x304 of_platform_populate+0xac/0xc4 devm_of_platform_populate+0x60/0xac geni_se_probe+0x154/0x160 platform_probe+0x70/0xc0 ... -> #0 (console_owner){-...}-{0:0}: __lock_acquire+0xdf8/0x109c lock_acquire+0x234/0x284 console_flush_all+0x330/0x454 console_unlock+0x
owner){-...}-{0:0}: __lock_acquire+0xdf8/0x109c lock_acquire+0x234/0x284 console_flush_all+0x330/0x454 console_unlock+0x94/0xf0 vprintk_emit+0x238/0x24c vprintk_default+0x3c/0x48 vprintk+0xb4/0xbc _printk+0x68/0x90 dma_entry_alloc+0xb4/0x110 debug_dma_map_sg+0xdc/0x2f8 __dma_map_sg_attrs+0xac/0xe4 dma_map_sgtable+0x30/0x4c get_pages+0x1d4/0x1e4 [msm] msm_gem_pin_pages_locked+0x38/0xac [msm] msm_gem_pin_vma_locked+0x58/0x88 [msm] msm_ioctl_gem_submit+0xde4/0x13ac [msm] drm_ioctl_kernel+0xe0/0x15c drm_ioctl+0x2e8/0x3f4 vfs_ioctl+0x30/0x50 ... Chain exists of: console_owner --> &port_lock_key --> free_entries_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(free_entries_lock); lo
> &port_lock_key --> free_entries_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(free_entries_lock); lock(&port_lock_key); lock(free_entries_lock); lock(console_owner); *** DEADLOCK *** Call trace: dump_backtrace+0xb4/0xf0 show_stack+0x20/0x30 dump_stack_lvl+0x60/0x84 dump_stack+0x18/0x24 print_circular_bug+0x1cc/0x234 check_noncircular+0x78/0xac __lock_acquire+0xdf8/0x109c lock_acquire+0x234/0x284 console_flush_all+0x330/0x454 consol ---truncated--- Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c79300599923daaa30f417c75555d5566b3d31ae - https://git.kernel.org/stable/c/ac0d068099349cbca3d93f2e3b15bb3
.org/stable/c/c79300599923daaa30f417c75555d5566b3d31ae - https://git.kernel.org/stable/c/ac0d068099349cbca3d93f2e3b15bb329364b08c - https://git.kernel.org/stable/c/be8f49029eca3efbad0d74dbff3cb9129994ffab - https://git.kernel.org/stable/c/fe2b811a02c3244ebf6059039e4a9e715e26a9e3 - https://git.kernel.org/stable/c/fb5a4315591dae307a65fc246ca80b5159d296e1
CVE ID: CVE-2023-52517 State: PUBLISHED Published: 2024-03-02T21:52:27.152Z Last Updated: 2025-05-04T07:38:25.175Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain Previously the transfer complete IRQ immediately drained to RX FIFO to read any data remaining in FIFO to the RX buffer. This behaviour is correct when dealing with SPI in interrupt mode. However in DMA mode the transfer complete interrupt still fires as soon as all bytes to be transferred have been stored in the FIFO. At that point data in the FIFO still needs to be picked up by the DMA engine.
transferred have been stored in the FIFO. At that point data in the FIFO still needs to be picked up by the DMA engine. Thus the drain procedure and DMA engine end up racing to read from RX FIFO, corrupting any data read. Additionally the RX buffer pointer is never adjusted according to DMA progress in DMA mode, thus calling the RX FIFO drain procedure in DMA mode is a bug. Fix corruptions in DMA RX mode by draining RX FIFO only in interrupt mode. Also wait for completion of RX DMA when in DMA mode before returning to ensure all data has been copied to the supplied memory buffer. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/
uffer. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/bd1ec7f9983b5cd3c77e0f7cda3fa8aed041af2f - https://git.kernel.org/stable/c/36b29974a7ad2ff604c24ad348f940506c7b1209 - https://git.kernel.org/stable/c/4e149d524678431638ff378ef6025e4e89b71097 - https://git.kernel.org/stable/c/1f11f4202caf5710204d334fe63392052783876d
CVE ID: CVE-2023-52518 State: PUBLISHED Published: 2024-03-02T21:54:47.826Z Last Updated: 2025-05-04T07:38:26.511Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_codec: Fix leaking content of local_codecs The following memory leak can be observed when the controller supports codecs which are stored in local_codecs list but the elements are never freed: unreferenced object 0xffff88800221d840 (size 32): comm "kworker/u3:0", pid 36, jiffies 4294898739 (age 127.060s) hex dump (first 32 bytes): f8 d3 02 03 80 88 ff ff 80 d8 21 02 80 88 ff ff ..........!..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ............
02 03 80 88 ff ff 80 d8 21 02 80 88 ff ff ..........!..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffffb324f557>] __kmalloc+0x47/0x120 [<ffffffffb39ef37d>] hci_codec_list_add.isra.0+0x2d/0x160 [<ffffffffb39ef643>] hci_read_codec_capabilities+0x183/0x270 [<ffffffffb39ef9ab>] hci_read_supported_codecs+0x1bb/0x2d0 [<ffffffffb39f162e>] hci_read_local_codecs_sync+0x3e/0x60 [<ffffffffb39ff1b3>] hci_dev_open_sync+0x943/0x11e0 [<ffffffffb396d55d>] hci_power_on+0x10d/0x3f0 [<ffffffffb30c99b4>] process_one_work+0x404/0x800 [<ffffffffb30ca134>] worker_thread+0x374/0x670 [<ffffffffb30d9108>] kthread+0x188/0x1c0 [<ffffffffb304db6b>] ret_from_fork+0x2b/0x50 [<fff
>] worker_thread+0x374/0x670 [<ffffffffb30d9108>] kthread+0x188/0x1c0 [<ffffffffb304db6b>] ret_from_fork+0x2b/0x50 [<ffffffffb300206a>] ret_from_fork_asm+0x1a/0x30 Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/626535077ba9dc110787540d1fe24881094c15a1 - https://git.kernel.org/stable/c/eea5a8f0c3b7c884d2351e75fbdd0a3d7def5ae1 - https://git.kernel.org/stable/c/b938790e70540bf4f2e653dcd74b232494d06c8f
CVE ID: CVE-2023-52519 State: PUBLISHED Published: 2024-03-02T21:52:27.816Z Last Updated: 2025-05-04T07:38:27.799Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit The EHL (Elkhart Lake) based platforms provide a OOB (Out of band) service, which allows to wakup device when the system is in S5 (Soft-Off state). This OOB service can be enabled/disabled from BIOS settings. When enabled, the ISH device gets PME wake capability. To enable PME wakeup, driver also needs to enable ACPI GPE bit. On resume, BIOS will clear the wakeup bit. So driver need to re-enable it in resume fu
lso needs to enable ACPI GPE bit. On resume, BIOS will clear the wakeup bit. So driver need to re-enable it in resume function to keep the next wakeup capability. But this BIOS clearing of wakeup bit doesn't decrement internal OS GPE reference count, so this reenabling on every resume will cause reference count to overflow. So first disable and reenable ACPI GPE bit using acpi_disable_gpe(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8781fe259dd5a178fdd1069401bbd1437f9491c5 - https://git.kernel.org/stable/c/cdcc04e844a2d22d9d25cef1e8e504a174ea9f8f - https://git.kernel.org/stable/c/60fb3f054c99608ddb1f2466c07108da6
rg/stable/c/cdcc04e844a2d22d9d25cef1e8e504a174ea9f8f - https://git.kernel.org/stable/c/60fb3f054c99608ddb1f2466c07108da6292951e - https://git.kernel.org/stable/c/8f02139ad9a7e6e5c05712f8c1501eebed8eacfd
CVE ID: CVE-2023-52520 State: PUBLISHED Published: 2024-03-02T21:52:28.434Z Last Updated: 2025-05-04T07:38:29.020Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: platform/x86: think-lmi: Fix reference leak If a duplicate attribute is found using kset_find_obj(), a reference to that attribute is returned which needs to be disposed accordingly using kobject_put(). Move the setting name validation into a separate function to allow for this change without having to duplicate the cleanup code for this setting. As a side note, a very similar bug was fixed in commit 7295a996fdab ("platform/x86: dell-sysman: Fix reference leak"), so it
side note, a very similar bug was fixed in commit 7295a996fdab ("platform/x86: dell-sysman: Fix reference leak"), so it seems that the bug was copied from that driver. Compile-tested only. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/124cf0ea4b82e1444ec8c7420af4e7db5558c293 - https://git.kernel.org/stable/c/af21c9119a37cecb7ff27ce0c2f3cf721e9d0ec4 - https://git.kernel.org/stable/c/c6e3023579de8d33256771ac0745239029e81106 - https://git.kernel.org/stable/c/528ab3e605cabf2f9c9bd5944d3bfe15f6e94f81
CVE ID: CVE-2023-52521 State: REJECTED Published: 2024-03-02T21:52:29.058Z Last Updated: 2024-03-05T22:23:15.078Z Description: No description available.
CVE ID: CVE-2023-52522 State: PUBLISHED Published: 2024-03-02T21:52:29.710Z Last Updated: 2025-05-04T07:38:30.383Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: fix possible store tearing in neigh_periodic_work() While looking at a related syzbot report involving neigh_periodic_work(), I found that I forgot to add an annotation when deleting an RCU protected item from a list. Readers use rcu_deference(*np), we need to use either rcu_assign_pointer() or WRITE_ONCE() on writer side to prevent store tearing. I use rcu_assign_pointer() to have lockdep support, this was the choice made in neigh_flush_dev(). Additional Analyst
. I use rcu_assign_pointer() to have lockdep support, this was the choice made in neigh_flush_dev(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af - https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0 - https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa - https://git.kernel.org/stable/c/f82aac8162871e87027692b36af335a2375d4580 - https://git.kernel.org/stable/c/a75152d233370362eebedb2643592e7c883cc9fc - https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd
CVE ID: CVE-2023-52523 State: PUBLISHED Published: 2024-03-02T21:52:30.351Z Last Updated: 2025-05-04T07:38:31.613Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets With a SOCKMAP/SOCKHASH map and an sk_msg program user can steer messages sent from one TCP socket (s1) to actually egress from another TCP socket (s2): tcp_bpf_sendmsg(s1) // = sk_prot->sendmsg tcp_bpf_send_verdict(s1) // __SK_REDIRECT case tcp_bpf_sendmsg_redir(s2) tcp_bpf_push_locked(s2) tcp_bpf_push(s2) tcp_rate_check_app_limited(s2) // expects tcp_sock tcp_sendmsg_locked(s2) // ditto There is a hard-c
2) tcp_bpf_push(s2) tcp_rate_check_app_limited(s2) // expects tcp_sock tcp_sendmsg_locked(s2) // ditto There is a hard-coded assumption in the call-chain, that the egress socket (s2) is a TCP socket. However in commit 122e6c79efe1 ("sock_map: Update sock type checks for UDP") we have enabled redirects to non-TCP sockets. This was done for the sake of BPF sk_skb programs. There was no indention to support sk_msg send-to-egress use case. As a result, attempts to send-to-egress through a non-TCP socket lead to a crash due to invalid downcast from sock to tcp_sock: BUG: kernel NULL pointer dereference, address: 000000000000002f ... Call Trace: <TASK> ? show_regs+0x60/0x70 ? __die+0x1f/0x70 ? pag
NULL pointer dereference, address: 000000000000002f ... Call Trace: <TASK> ? show_regs+0x60/0x70 ? __die+0x1f/0x70 ? page_fault_oops+0x80/0x160 ? do_user_addr_fault+0x2d7/0x800 ? rcu_is_watching+0x11/0x50 ? exc_page_fault+0x70/0x1c0 ? asm_exc_page_fault+0x27/0x30 ? tcp_tso_segs+0x14/0xa0 tcp_write_xmit+0x67/0xce0 __tcp_push_pending_frames+0x32/0xf0 tcp_push+0x107/0x140 tcp_sendmsg_locked+0x99f/0xbb0 tcp_bpf_push+0x19d/0x3a0 tcp_bpf_sendmsg_redir+0x55/0xd0 tcp_bpf_send_verdict+0x407/0x550 tcp_bpf_sendmsg+0x1a1/0x390 inet_sendmsg+0x6a/0x70 sock_sendmsg+0x9d/0xc0 ? sockfd_lookup_light+0x12/0x80 __sys_sendto+0x10e/0x160 ? syscall_enter_from_user_mode+0x20/0x60 ? __this_cpu_preempt_check+0x13/0x2
up_light+0x12/0x80 __sys_sendto+0x10e/0x160 ? syscall_enter_from_user_mode+0x20/0x60 ? __this_cpu_preempt_check+0x13/0x20 ? lockdep_hardirqs_on+0x82/0x110 __x64_sys_sendto+0x1f/0x30 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd Reject selecting a non-TCP sockets as redirect target from a BPF sk_msg program to prevent the crash. When attempted, user will receive an EACCES error from send/sendto/sendmsg() syscall. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/bc8b89b6963803a123f64aa9494155a037b3d728 - https://git.kernel.org/stable/c/b8f97e47b6fb84fcf2f5a22e725eefb6cf5070c2 - https://git.kernel.org/st
9494155a037b3d728 - https://git.kernel.org/stable/c/b8f97e47b6fb84fcf2f5a22e725eefb6cf5070c2 - https://git.kernel.org/stable/c/ded6e448028f0f91b6af35985afca01fa02a9089 - https://git.kernel.org/stable/c/b80e31baa43614e086a9d29dc1151932b1bd7fc5
CVE ID: CVE-2023-52524 State: PUBLISHED Published: 2024-03-02T21:52:30.995Z Last Updated: 2025-05-04T12:49:09.323Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: nfc: llcp: Add lock when modifying device list The device list needs its associated lock held when modifying it, or the list could become corrupted, as syzbot discovered. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/191d87a19cf1005ecf41e1ae08d74e17379e8391 - https://git.kernel.org/stable/c/dba849cc98113b145c6e720122942c00b8012bdb - https://git.kernel.org/stable/c/4837a192f6d06d5bb2f3f47d6
kernel.org/stable/c/dba849cc98113b145c6e720122942c00b8012bdb - https://git.kernel.org/stable/c/4837a192f6d06d5bb2f3f47d6ce5353ab69bf86b - https://git.kernel.org/stable/c/7562780e32b84196731d57dd24563546fcf6d082 - https://git.kernel.org/stable/c/29c16c2bf5866326d5fbc4a537b3997fcac23391 - https://git.kernel.org/stable/c/dfc7f7a988dad34c3bf4c053124fb26aa6c5f916
CVE ID: CVE-2023-52525 State: PUBLISHED Published: 2024-03-02T21:52:31.638Z Last Updated: 2025-05-04T12:49:10.564Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet Only skip the code path trying to access the rfc1042 headers when the buffer is too small, so the driver can still process packets without rfc1042 headers. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/71b1d2b57f145c8469aa9346f0fd57bf59b2b89c - https://git.kernel.org/stable/c/16cc18b9080892d1a0200a38e36ae52e464bc555 - https://g
57f145c8469aa9346f0fd57bf59b2b89c - https://git.kernel.org/stable/c/16cc18b9080892d1a0200a38e36ae52e464bc555 - https://git.kernel.org/stable/c/b8e260654a29de872e7cb85387d8ab8974694e8e - https://git.kernel.org/stable/c/10a18c8bac7f60d32b7af22da03b66f350beee38 - https://git.kernel.org/stable/c/5afb996349cb6d1f14d6ba9aaa7aed3bd82534f6 - https://git.kernel.org/stable/c/6b706286473db4fd54b5f869faa67f4a8cb18e99 - https://git.kernel.org/stable/c/be2ff39b1504c5359f4a083c1cfcad21d666e216 - https://git.kernel.org/stable/c/aef7a0300047e7b4707ea0411dc9597cba108fc8
CVE ID: CVE-2023-52526 State: PUBLISHED Published: 2024-03-02T21:52:32.261Z Last Updated: 2025-05-04T07:38:36.326Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: erofs: fix memory leak of LZMA global compressed deduplication When stressing microLZMA EROFS images with the new global compressed deduplication feature enabled (`-Ededupe`), I found some short-lived temporary pages weren't properly released, which could slowly cause unexpected OOMs hours later. Let's fix it now (LZ4 and DEFLATE don't have this issue.) Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stab