Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2024-43864 State: PUBLISHED Published: 2024-08-20T23:45:28.833Z Last Updated: 2025-05-04T09:27:58.553Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix CT entry update leaks of modify header context The cited commit allocates a new modify header to replace the old one when updating CT entry. But if failed to allocate a new one, eg. exceed the max number firmware can support, modify header will be an error pointer that will trigger a panic when deallocating it. And the old modify header point is copied to old attr. When the old attr is freed, the old modify header is lost. Fix it by restoring the old att
point is copied to old attr. When the old attr is freed, the old modify header is lost. Fix it by restoring the old attr to attr when failed to allocate a new modify header context. So when the CT entry is freed, the right modify header context will be freed. And the panic of accessing error pointer is also fixed. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/daab2cc17b6b6ab158566bba037e9551fd432b59 - https://git.kernel.org/stable/c/89064d09c56b44c668509bf793c410484f63f5ad - https://git.kernel.org/stable/c/025f2b85a5e5a46df14ecf162c3c80a957a36d0b
CVE ID: CVE-2024-43865 State: PUBLISHED Published: 2024-08-20T23:50:48.269Z Last Updated: 2025-05-04T09:27:59.832Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/fpu: Re-add exception handling in load_fpu_state() With the recent rewrite of the fpu code exception handling for the lfpc instruction within load_fpu_state() was erroneously removed. Add it again to prevent that loading invalid floating point register values cause an unhandled specification exception. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/494b14138201f07343e5488db6360c828fcc8cf6 - https://git.kernel.org/s
hment: References: - https://git.kernel.org/stable/c/494b14138201f07343e5488db6360c828fcc8cf6 - https://git.kernel.org/stable/c/4734406c39238cbeafe66f0060084caa3247ff53
CVE ID: CVE-2024-43866 State: PUBLISHED Published: 2024-08-20T23:50:49.364Z Last Updated: 2025-11-03T22:06:11.447Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Always drain health in shutdown callback There is no point in recovery during device shutdown. if health work started need to wait for it to avoid races and NULL pointer access. Hence, drain health WQ on shutdown callback. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/5005e2e159b300c1b8c6820a1e13a62eb0127b9b - https://git.kernel.org/stable/c/6b6c2ebd83f2bf97e8f221479372aaca97a4a9b2 -
c/5005e2e159b300c1b8c6820a1e13a62eb0127b9b - https://git.kernel.org/stable/c/6b6c2ebd83f2bf97e8f221479372aaca97a4a9b2 - https://git.kernel.org/stable/c/6048dec754554a1303d632be6042d3feb3295285 - https://git.kernel.org/stable/c/1b75da22ed1e6171e261bc9265370162553d5393
CVE ID: CVE-2024-43867 State: PUBLISHED Published: 2024-08-20T23:50:50.429Z Last Updated: 2025-11-03T22:06:14.480Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: prime: fix refcount underflow Calling nouveau_bo_ref() on a nouveau_bo without initializing it (and hence the backing ttm_bo) leads to a refcount underflow. Instead of calling nouveau_bo_ref() in the unwind path of drm_gem_object_init(), clean things up manually. (cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5) Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3bcb8
nal Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3bcb8bba72ce89667fa863054956267c450c47ef - https://git.kernel.org/stable/c/906372e753c5027a1dc88743843b6aa2ad1aaecf - https://git.kernel.org/stable/c/16998763c62bb465ebc409d0373b9cdcef1a61a6 - https://git.kernel.org/stable/c/ebebba4d357b6c67f96776a48ddbaf0060fa4c10 - https://git.kernel.org/stable/c/f23cd66933fe76b84d8e282e5606b4d99068c320 - https://git.kernel.org/stable/c/2a1b327d57a8ac080977633a18999f032d7e9e3f - https://git.kernel.org/stable/c/a9bf3efc33f1fbf88787a277f7349459283c9b95
CVE ID: CVE-2024-43868 State: PUBLISHED Published: 2024-08-20T23:50:51.464Z Last Updated: 2025-11-03T22:06:15.949Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: riscv/purgatory: align riscv_kernel_entry When alignment handling is delegated to the kernel, everything must be word-aligned in purgatory, since the trap handler is then set to the kexec one. Without the alignment, hitting the exception would ultimately crash. On other occasions, the kernel's handler would take care of exceptions. This has been tested on a JH7110 SoC with oreboot and its SBI delegating unaligned access exceptions and the kernel configured to handle th
d on a JH7110 SoC with oreboot and its SBI delegating unaligned access exceptions and the kernel configured to handle them. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/10ffafb456f293976c42f700578ef740467cb569 - https://git.kernel.org/stable/c/6e62dab357eea12db0fc62dea94c7a892888e6e8 - https://git.kernel.org/stable/c/5d4aaf16a8255f7c71790e211724ba029609c5ff - https://git.kernel.org/stable/c/fb197c5d2fd24b9af3d4697d0cf778645846d6d5
CVE ID: CVE-2024-43869 State: PUBLISHED Published: 2024-08-21T00:06:20.807Z Last Updated: 2025-11-03T22:06:17.395Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: perf: Fix event leak upon exec and file release The perf pending task work is never waited upon the matching event release. In the case of a child event, released via free_event() directly, this can potentially result in a leaked event, such as in the following scenario that doesn't even require a weak IRQ work implementation to trigger: schedule() prepare_task_switch() =======> <NMI> perf_event_overflow() event->pending_sigtrap = ... irq_work_queue(&event->pending_irq
epare_task_switch() =======> <NMI> perf_event_overflow() event->pending_sigtrap = ... irq_work_queue(&event->pending_irq) <======= </NMI> perf_event_task_sched_out() event_sched_out() event->pending_sigtrap = 0; atomic_long_inc_not_zero(&event->refcount) task_work_add(&event->pending_task) finish_lock_switch() =======> <IRQ> perf_pending_irq() //do nothing, rely on pending task work <======= </IRQ> begin_new_exec() perf_event_exit_task() perf_event_exit_event() // If is child event free_event() WARN(atomic_long_cmpxchg(&event->refcount, 1, 0) != 1) // event is leaked Similar scenarios can also happen with perf_event_remove_on_exec() or simply against concurrent perf_event_release(). Fix this
r scenarios can also happen with perf_event_remove_on_exec() or simply against concurrent perf_event_release(). Fix this with synchonizing against the possibly remaining pending task work while freeing the event, just like is done with remaining pending IRQ work. This means that the pending task callback neither need nor should hold a reference to the event, preventing it from ever beeing freed. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/9ad46f1fef421d43cdab3a7d1744b2f43b54dae0 - https://git.kernel.org/stable/c/ed2c202dac55423a52d7e2290f2888bf08b8ee99 - https://git.kernel.org/stable/c/104e258a004037bc7dba9f6085c71
el.org/stable/c/ed2c202dac55423a52d7e2290f2888bf08b8ee99 - https://git.kernel.org/stable/c/104e258a004037bc7dba9f6085c71dad6af57ad4 - https://git.kernel.org/stable/c/f34d8307a73a18de5320fcc6f40403146d061891 - https://git.kernel.org/stable/c/3a5465418f5fd970e86a86c7f4075be262682840
CVE ID: CVE-2024-43870 State: PUBLISHED Published: 2024-08-21T00:06:21.878Z Last Updated: 2025-11-03T22:06:18.842Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: perf: Fix event leak upon exit When a task is scheduled out, pending sigtrap deliveries are deferred to the target task upon resume to userspace via task_work. However failures while adding an event's callback to the task_work engine are ignored. And since the last call for events exit happen after task work is eventually closed, there is a small window during which pending sigtrap can be queued though ignored, leaking the event refcount addition such as in the followi
ow during which pending sigtrap can be queued though ignored, leaking the event refcount addition such as in the following scenario: TASK A ----- do_exit() exit_task_work(tsk); <IRQ> perf_event_overflow() event->pending_sigtrap = pending_id; irq_work_queue(&event->pending_irq); </IRQ> =========> PREEMPTION: TASK A -> TASK B event_sched_out() event->pending_sigtrap = 0; atomic_long_inc_not_zero(&event->refcount) // FAILS: task work has exited task_work_add(&event->pending_task) [...] <IRQ WORK> perf_pending_irq() // early return: event->oncpu = -1 </IRQ WORK> [...] =========> TASK B -> TASK A perf_event_exit_task(tsk) perf_event_exit_event() free_event() WARN(atomic_long_cmpxchg(&event->refco
> TASK B -> TASK A perf_event_exit_task(tsk) perf_event_exit_event() free_event() WARN(atomic_long_cmpxchg(&event->refcount, 1, 0) != 1) // leak event due to unexpected refcount == 2 As a result the event is never released while the task exits. Fix this with appropriate task_work_add()'s error handling. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/67fad724f1b568b356c1065d50df46e6b30eb2f7 - https://git.kernel.org/stable/c/70882d7fa74f0731492a0d493e8515a4f7131831 - https://git.kernel.org/stable/c/05d3fd599594abf79aad4484bccb2b26e1cb0b51 - https://git.kernel.org/stable/c/3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a - https
3fd599594abf79aad4484bccb2b26e1cb0b51 - https://git.kernel.org/stable/c/3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a - https://git.kernel.org/stable/c/2fd5ad3f310de22836cdacae919dd99d758a1f1b
CVE ID: CVE-2024-43871 State: PUBLISHED Published: 2024-08-21T00:06:22.964Z Last Updated: 2025-11-03T22:06:21.787Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: devres: Fix memory leakage caused by driver API devm_free_percpu() It will cause memory leakage when use driver API devm_free_percpu() to free memory allocated by devm_alloc_percpu(), fixed by using devres_release() instead of devres_destroy() within devm_free_percpu(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/700e8abd65b10792b2f179ce4e858f2ca2880f85 - https://git.kernel.org/stable/c/b0445
nces: - https://git.kernel.org/stable/c/700e8abd65b10792b2f179ce4e858f2ca2880f85 - https://git.kernel.org/stable/c/b044588a16a978cd891cb3d665dd7ae06850d5bf - https://git.kernel.org/stable/c/ef56dcdca8f2a53abc3a83d388b8336447533d85 - https://git.kernel.org/stable/c/3047f99caec240a88ccd06197af2868da1af6a96 - https://git.kernel.org/stable/c/3dcd0673e47664bc6c719ad47dadac6d55d5950d - https://git.kernel.org/stable/c/b67552d7c61f52f1271031adfa7834545ae99701 - https://git.kernel.org/stable/c/95065edb8ebb27771d5f1e898eef6ab43dc6c87c - https://git.kernel.org/stable/c/bd50a974097bb82d52a458bd3ee39fb723129a0c
CVE ID: CVE-2024-43872 State: PUBLISHED Published: 2024-08-21T00:06:24.041Z Last Updated: 2025-05-04T09:28:15.395Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix soft lockup under heavy CEQE load CEQEs are handled in interrupt handler currently. This may cause the CPU core staying in interrupt context too long and lead to soft lockup under heavy load. Handle CEQEs in BH workqueue and set an upper limit for the number of CEQE handled by a single call of work handler. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/06580b33c183c9f98e2a2ca96a86137179032c08 - https://gi
SA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/06580b33c183c9f98e2a2ca96a86137179032c08 - https://git.kernel.org/stable/c/2fdf34038369c0a27811e7b4680662a14ada1d6b
CVE ID: CVE-2024-43873 State: PUBLISHED Published: 2024-08-21T00:06:25.114Z Last Updated: 2025-11-03T22:06:23.270Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: vhost/vsock: always initialize seqpacket_allow There are two issues around seqpacket_allow: 1. seqpacket_allow is not initialized when socket is created. Thus if features are never set, it will be read uninitialized. 2. if VIRTIO_VSOCK_F_SEQPACKET is set and then cleared, then seqpacket_allow will not be cleared appropriately (existing apps I know about don't usually do this but it's legal and there's no way to be sure no one relies on this). To fix: - initialize seqpa
ut don't usually do this but it's legal and there's no way to be sure no one relies on this). To fix: - initialize seqpacket_allow after allocation - set it unconditionally in set_features Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c - https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb - https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 - https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b - https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22
CVE ID: CVE-2024-43874 State: PUBLISHED Published: 2024-08-21T00:06:26.153Z Last Updated: 2025-05-04T09:28:18.187Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix null pointer dereference in __sev_snp_shutdown_locked Fix a null pointer dereference induced by DEBUG_TEST_DRIVER_REMOVE. Return from __sev_snp_shutdown_locked() if the psp_device or the sev_device structs are not initialized. Without the fix, the driver will produce the following splat: ccp 0000:55:00.5: enabling device (0000 -> 0002) ccp 0000:55:00.5: sev enabled ccp 0000:55:00.5: psp enabled BUG: kernel NULL pointer dereference, address: 0000000000
2) ccp 0000:55:00.5: sev enabled ccp 0000:55:00.5: psp enabled BUG: kernel NULL pointer dereference, address: 00000000000000f0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC NOPTI CPU: 262 PID: 1 Comm: swapper/0 Not tainted 6.9.0-rc1+ #29 RIP: 0010:__sev_snp_shutdown_locked+0x2e/0x150 Code: 00 55 48 89 e5 41 57 41 56 41 54 53 48 83 ec 10 41 89 f7 49 89 fe 65 48 8b 04 25 28 00 00 00 48 89 45 d8 48 8b 05 6a 5a 7f 06 <4c> 8b a0 f0 00 00 00 41 0f b6 9c 24 a2 00 00 00 48 83 fb 02 0f 83 RSP: 0018:ffffb2ea4014b7b8 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff9e4acd2e0a28 RCX: 0000000000000000 RDX: 0000
RSP: 0018:ffffb2ea4014b7b8 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff9e4acd2e0a28 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2ea4014b808 RBP: ffffb2ea4014b7e8 R08: 0000000000000106 R09: 000000000003d9c0 R10: 0000000000000001 R11: ffffffffa39ff070 R12: ffff9e49d40590c8 R13: 0000000000000000 R14: ffffb2ea4014b808 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff9e58b1e00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000000000f0 CR3: 0000000418a3e001 CR4: 0000000000770ef0 PKRU: 55555554 Call Trace: <TASK> ? __die_body+0x6f/0xb0 ? __die+0xcc/0xf0 ? page_fault_oops+0x330/0x3a0 ? save_trace+0x2a5/0x360 ? do
Call Trace: <TASK> ? __die_body+0x6f/0xb0 ? __die+0xcc/0xf0 ? page_fault_oops+0x330/0x3a0 ? save_trace+0x2a5/0x360 ? do_user_addr_fault+0x583/0x630 ? exc_page_fault+0x81/0x120 ? asm_exc_page_fault+0x2b/0x30 ? __sev_snp_shutdown_locked+0x2e/0x150 __sev_firmware_shutdown+0x349/0x5b0 ? pm_runtime_barrier+0x66/0xe0 sev_dev_destroy+0x34/0xb0 psp_dev_destroy+0x27/0x60 sp_destroy+0x39/0x90 sp_pci_remove+0x22/0x60 pci_device_remove+0x4e/0x110 really_probe+0x271/0x4e0 __driver_probe_device+0x8f/0x160 driver_probe_device+0x24/0x120 __driver_attach+0xc7/0x280 ? driver_attach+0x30/0x30 bus_for_each_dev+0x10d/0x130 driver_attach+0x22/0x30 bus_add_driver+0x171/0x2b0 ? unaccepted_memory_init_kdump+0x20/0x
0 bus_for_each_dev+0x10d/0x130 driver_attach+0x22/0x30 bus_add_driver+0x171/0x2b0 ? unaccepted_memory_init_kdump+0x20/0x20 driver_register+0x67/0x100 __pci_register_driver+0x83/0x90 sp_pci_init+0x22/0x30 sp_mod_init+0x13/0x30 do_one_initcall+0xb8/0x290 ? sched_clock_noinstr+0xd/0x10 ? local_clock_noinstr+0x3e/0x100 ? stack_depot_save_flags+0x21e/0x6a0 ? local_clock+0x1c/0x60 ? stack_depot_save_flags+0x21e/0x6a0 ? sched_clock_noinstr+0xd/0x10 ? local_clock_noinstr+0x3e/0x100 ? __lock_acquire+0xd90/0xe30 ? sched_clock_noinstr+0xd/0x10 ? local_clock_noinstr+0x3e/0x100 ? __create_object+0x66/0x100 ? local_clock+0x1c/0x60 ? __create_object+0x66/0x100 ? parameq+0x1b/0x90 ? parse_one+0x6d/0x1d0 ? p
te_object+0x66/0x100 ? local_clock+0x1c/0x60 ? __create_object+0x66/0x100 ? parameq+0x1b/0x90 ? parse_one+0x6d/0x1d0 ? parse_args+0xd7/0x1f0 ? do_initcall_level+0x180/0x180 do_initcall_level+0xb0/0x180 do_initcalls+0x60/0xa0 ? kernel_init+0x1f/0x1d0 do_basic_setup+0x41/0x50 kernel_init_freeable+0x1ac/0x230 ? rest_init+0x1f0/0x1f0 kernel_init+0x1f/0x1d0 ? rest_init+0x1f0/0x1f0 ret_from_fork+0x3d/0x50 ? rest_init+0x1f0/0x1f0 ret_from_fork_asm+0x11/0x20 </TASK> Modules linked in: CR2: 00000000000000f0 ---[ end trace 0000000000000000 ]--- RIP: 0010:__sev_snp_shutdown_locked+0x2e/0x150 Code: 00 55 48 89 e5 41 57 41 56 41 54 53 48 83 ec 10 41 89 f7 49 89 fe 65 48 8b 04 25 28 00 00 00 48 89 45 d8 4
e/0x150 Code: 00 55 48 89 e5 41 57 41 56 41 54 53 48 83 ec 10 41 89 f7 49 89 fe 65 48 8b 04 25 28 00 00 00 48 89 45 d8 48 8b 05 6a 5a 7f 06 <4c> 8b a0 f0 00 00 00 41 0f b6 9c 24 a2 00 00 00 48 83 fb 02 0f 83 RSP: 0018:ffffb2ea4014b7b8 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff9e4acd2e0a28 RCX: 0000000000000000 RDX: 0000000 ---truncated--- Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/bbf2c94503f6a421ed9b79e300d8085810da765d - https://git.kernel.org/stable/c/468e3295774d0edce15f4ae475913b5076dd4f40
CVE ID: CVE-2024-43875 State: PUBLISHED Published: 2024-08-21T00:06:27.204Z Last Updated: 2025-11-03T22:06:24.740Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: Clean up error handling in vpci_scan_bus() Smatch complains about inconsistent NULL checking in vpci_scan_bus(): drivers/pci/endpoint/functions/pci-epf-vntb.c:1024 vpci_scan_bus() error: we previously assumed 'vpci_bus' could be null (see line 1021) Instead of printing an error message and then crashing we should return an error code and clean up. Also the NULL check is reversed so it prints an error for success instead of failure. Additional Analyst Not
d clean up. Also the NULL check is reversed so it prints an error for success instead of failure. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/24414c842a24d0fd498f9db6d2a762a8dddf1832 - https://git.kernel.org/stable/c/7d368de78b60088ec9031c60c88976c0063ea4c0 - https://git.kernel.org/stable/c/0e27e2e8697b8ce96cdef43f135426525d9d1f8f - https://git.kernel.org/stable/c/b9e8695246bcfc028341470cbf92630cdc1ba36b - https://git.kernel.org/stable/c/8e0f5a96c534f781e8c57ca30459448b3bfe5429
CVE ID: CVE-2024-43876 State: PUBLISHED Published: 2024-08-21T00:06:28.260Z Last Updated: 2025-11-03T22:06:26.230Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: PCI: rcar: Demote WARN() to dev_warn_ratelimited() in rcar_pcie_wakeup() Avoid large backtrace, it is sufficient to warn the user that there has been a link problem. Either the link has failed and the system is in need of maintenance, or the link continues to work and user has been informed. The message from the warning can be looked up in the sources. This makes an actual link issue less verbose. First of all, this controller has a limitation in that the controller dr
. This makes an actual link issue less verbose. First of all, this controller has a limitation in that the controller driver has to assist the hardware with transition to L1 link state by writing L1IATN to PMCTRL register, the L1 and L0 link state switching is not fully automatic on this controller. In case of an ASMedia ASM1062 PCIe SATA controller which does not support ASPM, on entry to suspend or during platform pm_test, the SATA controller enters D3hot state and the link enters L1 state. If the SATA controller wakes up before rcar_pcie_wakeup() was called and returns to D0, the link returns to L0 before the controller driver even started its transition to L1 link state. At this point, t
o D0, the link returns to L0 before the controller driver even started its transition to L1 link state. At this point, the SATA controller did send an PM_ENTER_L1 DLLP to the PCIe controller and the PCIe controller received it, and the PCIe controller did set PMSR PMEL1RX bit. Once rcar_pcie_wakeup() is called, if the link is already back in L0 state and PMEL1RX bit is set, the controller driver has no way to determine if it should perform the link transition to L1 state, or treat the link as if it is in L0 state. Currently the driver attempts to perform the transition to L1 link state unconditionally, which in this specific case fails with a PMSR L1FAEG poll timeout, however the link still
1 link state unconditionally, which in this specific case fails with a PMSR L1FAEG poll timeout, however the link still works as it is already back in L0 state. Reduce this warning verbosity. In case the link is really broken, the rcar_pcie_config_access() would fail, otherwise it will succeed and any system with this controller and ASM1062 can suspend without generating a backtrace. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/59c78e8fddc1fe68f14011450a09b3418127d2ad - https://git.kernel.org/stable/c/2ae4769332dfdb97f4b6f5dc9ac8f46d02aaa3df - https://git.kernel.org/stable/c/526a877c6273d4cd0d0aede84c1d620479764b1c
e/c/2ae4769332dfdb97f4b6f5dc9ac8f46d02aaa3df - https://git.kernel.org/stable/c/526a877c6273d4cd0d0aede84c1d620479764b1c - https://git.kernel.org/stable/c/3ff3bdde950f1840df4030726cef156758a244d7 - https://git.kernel.org/stable/c/c93637e6a4c4e1d0e85ef7efac78d066bbb24d96
CVE ID: CVE-2024-43877 State: PUBLISHED Published: 2024-08-21T00:06:29.330Z Last Updated: 2025-11-03T22:06:27.712Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: pci: ivtv: Add check for DMA map result In case DMA fails, 'dma->SG_length' is 0. This value is later used to access 'dma->SGarray[dma->SG_length - 1]', which will cause out of bounds access. Add check to return early on invalid value. Adjust warnings accordingly. 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/38f72c7e7c6b5
yst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/38f72c7e7c6b55614f9407555fd5ce9d019b0fa4 - https://git.kernel.org/stable/c/81d0664bed91a858c7b50c263954b59d65f1b414 - https://git.kernel.org/stable/c/24062aa7407091dee3e45a8e8037df437e848718 - https://git.kernel.org/stable/c/3d8fd92939e21ff0d45100ab208f8124af79402a - https://git.kernel.org/stable/c/c766065e8272085ea9c436414b7ddf1f12e7787b - https://git.kernel.org/stable/c/629913d6d79508b166c66e07e4857e20233d85a9