Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
1c0 - https://git.kernel.org/stable/c/a8799662fed1f8747edae87a1937549288baca6a - https://git.kernel.org/stable/c/6e5c8e8e024e147b834f56f2115aad241433679b - https://git.kernel.org/stable/c/c516db6ab9eabbedbc430b4f93b0d8728e9b427f - https://git.kernel.org/stable/c/eb85dace897c5986bc2f36b3c783c6abb8a4292e
CVE ID: CVE-2024-38583 State: PUBLISHED Published: 2024-06-19T13:37:39.858Z Last Updated: 2025-11-04T17:21:36.675Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of timer for log writer thread Patch series "nilfs2: fix log writer related issues". This bug fix series covers three nilfs2 log writer-related issues, including a timer use-after-free issue and potential deadlock issue on unmount, and a potential freeze issue in event synchronization found during their analysis. Details are described in each commit log. This patch (of 3): A use-after-free issue has been reported regarding the timer sc_timer
described in each commit log. This patch (of 3): A use-after-free issue has been reported regarding the timer sc_timer on the nilfs_sc_info structure. The problem is that even though it is used to wake up a sleeping log writer thread, sc_timer is not shut down until the nilfs_sc_info structure is about to be freed, and is used regardless of the thread's lifetime. Fix this issue by limiting the use of sc_timer only while the log writer thread is alive. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/822ae5a8eac30478578a75f7e064f0584931bf2d - https://git.kernel.org/stable/c/82933c84f188dcfe89eb26b0b48ab5d1ca99d164 - htt
22ae5a8eac30478578a75f7e064f0584931bf2d - https://git.kernel.org/stable/c/82933c84f188dcfe89eb26b0b48ab5d1ca99d164 - https://git.kernel.org/stable/c/67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148 - https://git.kernel.org/stable/c/e65ccf3a4de4f0c763d94789615b83e11f204438 - https://git.kernel.org/stable/c/86a30d6302deddb9fb97ba6fc4b04d0e870b582a - https://git.kernel.org/stable/c/f9186bba4ea282b07293c1c892441df3a5441cb0 - https://git.kernel.org/stable/c/2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6 - https://git.kernel.org/stable/c/68e738be5c518fc3c4e9146b66f67c8fee0135fb - https://git.kernel.org/stable/c/f5d4e04634c9cf68bdf23de08ada0bb92e8befe7
CVE ID: CVE-2024-38584 State: PUBLISHED Published: 2024-06-19T13:37:40.515Z Last Updated: 2025-05-04T09:14:39.303Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe() In the prueth_probe() function, if one of the calls to emac_phy_connect() fails due to of_phy_connect() returning NULL, then the subsequent call to phy_attached_info() will dereference a NULL pointer. Check the return code of emac_phy_connect and fail cleanly if there is an error. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c
dditional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/5cd17f0e74cb99d209945b9f1f06d411aa667eb1 - https://git.kernel.org/stable/c/b0a82ebabbdc4c307f781bb0e5cd617949a3900d - https://git.kernel.org/stable/c/1e1d5bd7f4682e6925dd960aba2a1aa1d93da53a - https://git.kernel.org/stable/c/b31c7e78086127a7fcaa761e8d336ee855a920c6
CVE ID: CVE-2024-38585 State: PUBLISHED Published: 2024-06-19T13:37:41.170Z Last Updated: 2025-05-04T09:14:40.760Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tools/nolibc/stdlib: fix memory error in realloc() Pass user_p_len to memcpy() instead of heap->len to prevent realloc() from copying an extra sizeof(heap) bytes from beyond the allocated region. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/5996b2b2dac739f2a27da13de8eee5b85b2550b3 - https://git.kernel.org/stable/c/f678c3c336559cf3255a32153e9a17c1be4e7c15 - https://git.kernel.org/stable/c/8019d
550b3 - https://git.kernel.org/stable/c/f678c3c336559cf3255a32153e9a17c1be4e7c15 - https://git.kernel.org/stable/c/8019d3dd921f39a237a9fab6d2ce716bfac0f983 - https://git.kernel.org/stable/c/4e6f225aefeb712cdb870176b6621f02cf235b8c - https://git.kernel.org/stable/c/791f4641142e2aced85de082e5783b4fb0b977c2
CVE ID: CVE-2024-38586 State: PUBLISHED Published: 2024-06-19T13:37:41.879Z Last Updated: 2025-05-04T09:14:41.890Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: r8169: Fix possible ring buffer corruption on fragmented Tx packets. An issue was found on the RTL8125b when transmitting small fragmented packets, whereby invalid entries were inserted into the transmit ring buffer, subsequently leading to calls to dma_unmap_single() with a null address. This was caused by rtl8169_start_xmit() not noticing changes to nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2(). To fi
nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2(). To fix this, postpone inspecting nr_frags until after any padding has been applied. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/61c1c98e2607120ce9c3fa1bf75e6da909712b27 - https://git.kernel.org/stable/c/b6d21cf40de103d63ae78551098a7c06af8c98dd - https://git.kernel.org/stable/c/0c48185a95309556725f818b82120bb74e9c627d - https://git.kernel.org/stable/c/68222d7b4b72aa321135cd453dac37f00ec41fd1 - https://git.kernel.org/stable/c/078d5b7500d70af2de6b38e226b03f0b932026a6 - https://git.kernel.org/stable/c/54e7
c41fd1 - https://git.kernel.org/stable/c/078d5b7500d70af2de6b38e226b03f0b932026a6 - https://git.kernel.org/stable/c/54e7a0d111240c92c0f02ceba6eb8f26bf6d6479 - https://git.kernel.org/stable/c/c71e3a5cffd5309d7f84444df03d5b72600cc417
CVE ID: CVE-2024-38587 State: PUBLISHED Published: 2024-06-19T13:37:42.537Z Last Updated: 2025-11-04T17:21:38.044Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: speakup: Fix sizeof() vs ARRAY_SIZE() bug The "buf" pointer is an array of u16 values. This code should be using ARRAY_SIZE() (which is 256) instead of sizeof() (which is 512), otherwise it can the still got out of bounds. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/42f0a3f67158ed6b2908d2b9ffbf7e96d23fd358 - https://git.kernel.org/stable/c/cd7f3978c2ec741aedd1d860b2adb227314cf996 - https://gi
7158ed6b2908d2b9ffbf7e96d23fd358 - https://git.kernel.org/stable/c/cd7f3978c2ec741aedd1d860b2adb227314cf996 - https://git.kernel.org/stable/c/07ef95cc7a579731198c93beed281e3a79a0e586 - https://git.kernel.org/stable/c/504178fb7d9f6cdb0496d5491efb05f45597e535 - https://git.kernel.org/stable/c/3726f75a1ccc16cd335c0ccfad1d92ee08ecba5e - https://git.kernel.org/stable/c/c6e1650cf5df1bd6638eeee231a683ef30c7d4eb - https://git.kernel.org/stable/c/eb1ea64328d4cc7d7a912c563f8523d5259716ef - https://git.kernel.org/stable/c/d52c04474feac8e305814a5228e622afe481b2ef - https://git.kernel.org/stable/c/008ab3c53bc4f0b2f20013c8f6c204a3203d0b8b
CVE ID: CVE-2024-38588 State: PUBLISHED Published: 2024-06-19T13:37:43.262Z Last Updated: 2025-11-03T20:38:10.030Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix possible use-after-free issue in ftrace_location() KASAN reports a bug: BUG: KASAN: use-after-free in ftrace_location+0x90/0x120 Read of size 8 at addr ffff888141d40010 by task insmod/424 CPU: 8 PID: 424 Comm: insmod Tainted: G W 6.9.0-rc2+ [...] Call Trace: <TASK> dump_stack_lvl+0x68/0xa0 print_report+0xcf/0x610 kasan_report+0xb5/0xe0 ftrace_location+0x90/0x120 register_kprobe+0x14b/0xa40 kprobe_init+0x2d/0xff0 [kprobe_example] do_one_initcall+0x8f/0x2d0 d
ace_location+0x90/0x120 register_kprobe+0x14b/0xa40 kprobe_init+0x2d/0xff0 [kprobe_example] do_one_initcall+0x8f/0x2d0 do_init_module+0x13a/0x3c0 load_module+0x3082/0x33d0 init_module_from_file+0xd2/0x130 __x64_sys_finit_module+0x306/0x440 do_syscall_64+0x68/0x140 entry_SYSCALL_64_after_hwframe+0x71/0x79 The root cause is that, in lookup_rec(), ftrace record of some address is being searched in ftrace pages of some module, but those ftrace pages at the same time is being freed in ftrace_release_mod() as the corresponding module is being deleted: CPU1 | CPU2 register_kprobes() { | delete_module() { check_kprobe_address_safe() { | arch_check_ftrace_location() { | ftrace_location() { | lookup_r
() { | delete_module() { check_kprobe_address_safe() { | arch_check_ftrace_location() { | ftrace_location() { | lookup_rec() // USE! | ftrace_release_mod() // Free! To fix this issue: 1. Hold rcu lock as accessing ftrace pages in ftrace_location_range(); 2. Use ftrace_location_range() instead of lookup_rec() in ftrace_location(); 3. Call synchronize_rcu() before freeing any ftrace pages both in ftrace_process_locs()/ftrace_release_mod()/ftrace_free_mem(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/eea46baf145150910ba134f75a67106ba2222c1b - https://git.kernel.org/stable/c/1880a324af1c95940a7c954b6b937e86844a33bd -
c/eea46baf145150910ba134f75a67106ba2222c1b - https://git.kernel.org/stable/c/1880a324af1c95940a7c954b6b937e86844a33bd - https://git.kernel.org/stable/c/8ea8ef5e42173560ac510e92a1cc797ffeea8831 - https://git.kernel.org/stable/c/dbff5f0bfb2416b8b55c105ddbcd4f885e98fada - https://git.kernel.org/stable/c/7b4881da5b19f65709f5c18c1a4d8caa2e496461 - https://git.kernel.org/stable/c/66df065b3106964e667b37bf8f7e55ec69d0c1f6 - https://git.kernel.org/stable/c/31310e373f4c8c74e029d4326b283e757edabc0b - https://git.kernel.org/stable/c/e60b613df8b6253def41215402f72986fee3fc8d
CVE ID: CVE-2024-38589 State: PUBLISHED Published: 2024-06-19T13:45:41.258Z Last Updated: 2025-11-04T17:21:39.426Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: netrom: fix possible dead-lock in nr_rt_ioctl() syzbot loves netrom, and found a possible deadlock in nr_rt_ioctl [1] Make sure we always acquire nr_node_list_lock before nr_node_lock(nr_node) [1] WARNING: possible circular locking dependency detected 6.9.0-rc7-syzkaller-02147-g654de42f3fc6 #0 Not tainted ------------------------------------------------------ syz-executor350/5129 is trying to acquire lock: ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: spin_lo
-------- syz-executor350/5129 is trying to acquire lock: ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: nr_node_lock include/net/netrom.h:152 [inline] ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:464 [inline] ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: nr_rt_ioctl+0x1bb/0x1090 net/netrom/nr_route.c:697 but task is already holding lock: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.
lude/linux/spinlock.h:356 [inline] ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:462 [inline] ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: nr_rt_ioctl+0x10a/0x1090 net/netrom/nr_route.c:697 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (nr_node_list_lock){+...}-{2:2}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline] _raw_spin_lock_bh+0x35/0x50 kernel/locking/spinlock.c:178 spin_lock_bh include/linux/spinlock.h:356 [inline] nr_remove_node net/netrom/nr_route.c:299 [inline] nr_del_node+0x4b4/0x820 net/netrom/nr_route.c
/spinlock.h:356 [inline] nr_remove_node net/netrom/nr_route.c:299 [inline] nr_del_node+0x4b4/0x820 net/netrom/nr_route.c:355 nr_rt_ioctl+0xa95/0x1090 net/netrom/nr_route.c:683 sock_do_ioctl+0x158/0x460 net/socket.c:1222 sock_ioctl+0x629/0x8e0 net/socket.c:1341 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&nr_node->node_lock){+...}-{2:2}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain+0x18cb/0x58e0 ker
/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline] _raw_spin_lock_bh+0x35/0x50 kernel/locking/spinlock.c:178 spin_lock_bh include/linux/spinlock.h:356 [inline] nr_node_lock include/net/netrom.h:152 [inline] nr_dec_obs net/netrom/nr_route.c:464 [inline] nr_rt_ioctl+0x1bb/0x1090 net/netrom/nr_route.c:697 sock_do_ioctl+0x158/0x460 net/socket.c:1222 sock_ioctl+0x629/0x8e0 net/socket.c:1341 vfs_ioctl fs/ioctl.c:51 [inline] __d
ock_do_ioctl+0x158/0x460 net/socket.c:1222 sock_ioctl+0x629/0x8e0 net/socket.c:1341 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(nr_node_list_lock); lock(&nr_node->node_lock); lock(nr_node_list_lock); lock(&nr_node->node_lock); *** DEADLOCK *** 1 lock held by syz-executor350/5129: #0: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inli
cutor350/5129: #0: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] #0: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:462 [inline] #0: ffffffff8f70 ---truncated--- Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b9d663fbf74290cb68fbc66ae4367bd56837ad1d - https://git.kernel.org/stable/c/1fbfb483c1a290dce3f41f52d45cc46dd88b7691 - https://git.kernel.org/stable/c/b117e5b4f27c2c9076561b6be450a9619f0b79de - https://git.kernel.org/stable/c/421c50fa81836775bf0fd6ce0e57a6eb27af24d5 - https://git.kernel.org/stable/c/3db2fc45d1d2a6457
s://git.kernel.org/stable/c/421c50fa81836775bf0fd6ce0e57a6eb27af24d5 - https://git.kernel.org/stable/c/3db2fc45d1d2a6457f06ebdfd45b9820e5b5c2b7 - https://git.kernel.org/stable/c/f28bdc2ee5d9300cc77bd3d97b5b3cdd14960fd8 - https://git.kernel.org/stable/c/5fb7e2a4335fc67d6952ad2a6613c46e0b05f7c5 - https://git.kernel.org/stable/c/5bc50a705cfac8f64ce51c95611c3dd0554ef9c3 - https://git.kernel.org/stable/c/e03e7f20ebf7e1611d40d1fdc1bde900fd3335f6
CVE ID: CVE-2024-38590 State: PUBLISHED Published: 2024-06-19T13:45:41.928Z Last Updated: 2025-05-04T09:14:47.116Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Modify the print level of CQE error Too much print may lead to a panic in kernel. Change ibdev_err() to ibdev_err_ratelimited(), and change the printing level of cqe dump to debug level. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/45b31be4dd22827903df15c548b97b416790139b - https://git.kernel.org/stable/c/cc699b7eb2bc963c12ffcd37f80f45330d2924bd - https://git.kernel.org/stable/c/17f3
90139b - https://git.kernel.org/stable/c/cc699b7eb2bc963c12ffcd37f80f45330d2924bd - https://git.kernel.org/stable/c/17f3741c65c4a042ae8ba094068b07a4b77e213c - https://git.kernel.org/stable/c/6f541a89ced8305da459e3ab0006e7528cf7da7b - https://git.kernel.org/stable/c/817a10a6df9354e67561922d2b7fce48dfbebc55 - https://git.kernel.org/stable/c/06cf121346bbd3d83a5eea05bb87666c6b279990 - https://git.kernel.org/stable/c/349e859952285ab9689779fb46de163f13f18f43
CVE ID: CVE-2024-38591 State: PUBLISHED Published: 2024-06-19T13:45:42.701Z Last Updated: 2025-11-03T20:38:11.422Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix deadlock on SRQ async events. xa_lock for SRQ table may be required in AEQ. Use xa_store_irq()/ xa_erase_irq() to avoid deadlock. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/605889754ee68aacf7c381938fcd5eb654e71822 - https://git.kernel.org/stable/c/4a3be1a0ffe04c085dd7f79be97c91b0c786df3d - https://git.kernel.org/stable/c/756ddbe665ea7f9416951bd76731b174d136eea0 - https://git.ke
4c085dd7f79be97c91b0c786df3d - https://git.kernel.org/stable/c/756ddbe665ea7f9416951bd76731b174d136eea0 - https://git.kernel.org/stable/c/22c915af31bd84ffaa46145e317f53333f94a868 - https://git.kernel.org/stable/c/72dc542f0d8977e7d41d610db6bb65c47cad43e9 - https://git.kernel.org/stable/c/d271e66abac5c7eb8de345b9b44d89f777437a4c - https://git.kernel.org/stable/c/b46494b6f9c19f141114a57729e198698f40af37
CVE ID: CVE-2024-38592 State: PUBLISHED Published: 2024-06-19T13:45:43.367Z Last Updated: 2025-05-04T09:14:49.921Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Init `ddp_comp` with devm_kcalloc() In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn't reproduce, presumably becaus
with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn't reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0. It really doesn't hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it's suggested to only use the non-initting alloc functions if you really need to. Let's switch the function to use an allocation function that zeros the memory. For me, this avoids the crash. Additional Analy
switch the function to use an allocation function that zeros the memory. For me, this avoids the crash. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/cf69d0af7db917b82aceaa44b7b1b9376609da22 - https://git.kernel.org/stable/c/9fe2cc3fa44f7ad7ba5f29c1a68b2b924c17b9b1 - https://git.kernel.org/stable/c/01a2c5123e27b3c4685bf2fc4c2e879f6e0c7b33
CVE ID: CVE-2024-38593 State: PUBLISHED Published: 2024-06-19T13:45:44.031Z Last Updated: 2025-05-04T09:14:51.176Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: micrel: Fix receiving the timestamp in the frame for lan8841 The blamed commit started to use the ptp workqueue to get the second part of the timestamp. And when the port was set down, then this workqueue is stopped. But if the config option NETWORK_PHY_TIMESTAMPING is not enabled, then the ptp_clock is not initialized so then it would crash when it would try to access the delayed work. So then basically by setting up and then down the port, it would crash. The fi
it would try to access the delayed work. So then basically by setting up and then down the port, it would crash. The fix consists in checking if the ptp_clock is initialized and only then cancel the delayed work. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3ddf170e4a604f5d4d9459a36993f5e92b53e8b0 - https://git.kernel.org/stable/c/3fd4282d5f25c3c97fef3ef0b89b82ef4e2bc975 - https://git.kernel.org/stable/c/64a47cf634ae44e92be24ebc982410841093bd7b - https://git.kernel.org/stable/c/aea27a92a41dae14843f92c79e9e42d8f570105c
CVE ID: CVE-2024-38594 State: PUBLISHED Published: 2024-06-19T13:45:44.671Z Last Updated: 2025-05-04T12:56:48.423Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: stmmac: move the EST lock to struct stmmac_priv Reinitialize the whole EST structure would also reset the mutex lock which is embedded in the EST structure, and then trigger the following warning. To address this, move the lock to struct stmmac_priv. We also need to reacquire the mutex lock when doing this initialization. DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 3 PID: 505 at kernel/locking/mutex.c:587 __mutex_lock+0xd84/0x1068 Modules linked in: CPU
->magic != lock) WARNING: CPU: 3 PID: 505 at kernel/locking/mutex.c:587 __mutex_lock+0xd84/0x1068 Modules linked in: CPU: 3 PID: 505 Comm: tc Not tainted 6.9.0-rc6-00053-g0106679839f7-dirty #29 Hardware name: NXP i.MX8MPlus EVK board (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mutex_lock+0xd84/0x1068 lr : __mutex_lock+0xd84/0x1068 sp : ffffffc0864e3570 x29: ffffffc0864e3570 x28: ffffffc0817bdc78 x27: 0000000000000003 x26: ffffff80c54f1808 x25: ffffff80c9164080 x24: ffffffc080d723ac x23: 0000000000000000 x22: 0000000000000002 x21: 0000000000000000 x20: 0000000000000000 x19: ffffffc083bc3000 x18: ffffffffffffffff x17: ffffffc08117b080 x16: 0000000000000002 x15:
0000 x20: 0000000000000000 x19: ffffffc083bc3000 x18: ffffffffffffffff x17: ffffffc08117b080 x16: 0000000000000002 x15: ffffff80d2d40000 x14: 00000000000002da x13: ffffff80d2d404b8 x12: ffffffc082b5a5c8 x11: ffffffc082bca680 x10: ffffffc082bb2640 x9 : ffffffc082bb2698 x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001 x5 : ffffff8178fe0d48 x4 : 0000000000000000 x3 : 0000000000000027 x2 : ffffff8178fe0d50 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: __mutex_lock+0xd84/0x1068 mutex_lock_nested+0x28/0x34 tc_setup_taprio+0x118/0x68c stmmac_setup_tc+0x50/0xf0 taprio_change+0x868/0xc9c Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References:
0/0xf0 taprio_change+0x868/0xc9c Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b538fefeb1026aad9dcdcbb410c42b56dff8aae9 - https://git.kernel.org/stable/c/487f9030b1ef34bab123f2df2a4ccbe01ba84416 - https://git.kernel.org/stable/c/6f476aff2d8da1a189621c4c16a76a6c534e4312 - https://git.kernel.org/stable/c/36ac9e7f2e5786bd37c5cd91132e1f39c29b8197
CVE ID: CVE-2024-38595 State: PUBLISHED Published: 2024-06-19T13:45:45.336Z Last Updated: 2025-05-04T12:56:49.631Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix peer devlink set for SF representor devlink port The cited patch change register devlink flow, and neglect to reflect the changes for peer devlink set logic. Peer devlink set is triggering a call trace if done after devl_register.[1] Hence, align peer devlink set logic with register devlink flow. [1] WARNING: CPU: 4 PID: 3394 at net/devlink/core.c:155 devlink_rel_nested_in_add+0x177/0x180 CPU: 4 PID: 3394 Comm: kworker/u40:1 Not tainted 6.9.0-rc4_for_linu