Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
k_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90 The root cause is: inode node and dnode node share the same nid, so during f2fs_evict_inode(), dnode node truncation will invalidate its NAT entry, so when truncating inode node, it fails due to invalid NAT entry, result in inode is still marked as dirty, fix this issue by clearing dirty for inode and setting SBI_NEED_FSCK flag in filesystem. output from dump.f2fs: [print_node_info: 354] Node ID
ing dirty for inode and setting SBI_NEED_FSCK flag in filesystem. output from dump.f2fs: [print_node_info: 354] Node ID [0xf:15] is inode i_nid[0] [0x f : 15] References: - https://git.kernel.org/stable/c/54c116615c99e22aa08aa950757ed726e2f60821 - https://git.kernel.org/stable/c/ccd58045beb997544b94558a9156be4742628491 - https://git.kernel.org/stable/c/c9196d21359be8c7ee231029d13682273925fd00 - https://git.kernel.org/stable/c/03c9373b15fa1c245ec99b2b5e7ba209eae4ef42 - https://git.kernel.org/stable/c/c469953917b319d415fd621b9e5d0ea5203565cd - https://git.kernel.org/stable/c/f2db71053dc0409fae785096ad19cce4c8a95af7
CVE ID: CVE-2022-49365 State: PUBLISHED Published: 2025-02-26T02:11:10.768Z Last Updated: 2025-10-01T19:46:53.842Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Off by one in dm_dmub_outbox1_low_irq() The > ARRAY_SIZE() should be >= ARRAY_SIZE() to prevent an out of bounds access. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/ec9ec3bc08b18c5b1b2feafd306ea7c348013898 - https://git.kernel.org/stable/c/b0808b7a04157b3f56e919f27023fec37a075fad - https://git.kernel.org/stable/c/607c5cd1a08e196d9f2bd3b25a8083ed27ad7ceb - https://git.kernel.org/stable/c/a35faec3db0e13aac8
://git.kernel.org/stable/c/607c5cd1a08e196d9f2bd3b25a8083ed27ad7ceb - https://git.kernel.org/stable/c/a35faec3db0e13aac8ea720bc1a3503081dd5a3d
CVE ID: CVE-2022-49366 State: PUBLISHED Published: 2025-02-26T02:11:11.250Z Last Updated: 2025-10-01T19:46:53.699Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix reference count leak in smb_check_perm_dacl() The issue happens in a specific path in smb_check_perm_dacl(). When "id" and "uid" have the same value, the function simply jumps out of the loop without decrementing the reference count of the object "posix_acls", which is increased by get_acl() earlier. This may result in memory leaks. Fix it by decreasing the reference count of "posix_acls" before jumping to label "check_access_bits". Additional Analyst Notes:
by decreasing the reference count of "posix_acls" before jumping to label "check_access_bits". Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/cf824b95c12a1abacadbc2d069931963221a3414 - https://git.kernel.org/stable/c/248d71b440aef829f5cc5f6545ca113ef5062900 - https://git.kernel.org/stable/c/9758a6653c27867d810de02b4e5697163dda9883 - https://git.kernel.org/stable/c/d21a580dafc69aa04f46e6099616146a536b0724
CVE ID: CVE-2022-49367 State: PUBLISHED Published: 2025-02-26T02:11:11.729Z Last Updated: 2025-10-01T19:46:53.552Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. mv88e6xxx_mdio_register() pass the device node to of_mdiobus_register(). We don't need the device node after it. Add missing of_node_put() to avoid refcount leak. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/dc1cf8c6f9793546696fded437a5
ional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/dc1cf8c6f9793546696fded437a5b4c84944c48b - https://git.kernel.org/stable/c/86c3c5f8e4bd1325e24f6fba9017cade29933377 - https://git.kernel.org/stable/c/a101793994c0a14c70bb4e44c7fda597eeebba0a - https://git.kernel.org/stable/c/42658e47f1abbbe592007d3ba303de466114d0bb - https://git.kernel.org/stable/c/c1df9cb756e5a9ba1841648c44ee5d92306b9c65 - https://git.kernel.org/stable/c/e0d763d0c7665c7897e4f5a0847ab0c82543345f - https://git.kernel.org/stable/c/8a1a1255152da4fb934290e7ababc66f24985520 - https://git.kernel.org/stable/c/02ded5a173619b11728b8bf75a3fd995a2c1ff28
CVE ID: CVE-2022-49368 State: PUBLISHED Published: 2025-02-26T02:11:12.193Z Last Updated: 2025-10-01T19:46:53.404Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_eth_soc: out of bounds read in mtk_hwlro_get_fdir_entry() The "fsp->location" variable comes from user via ethtool_get_rxnfc(). Check that it is valid to prevent an out of bounds read. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b4f0e57ea0d867aacffad7999527e48bd4ea9293 - https://git.kernel.org/stable/c/5ba81f82607ead85fe36f50869fc4f5661359ab8 - https://git.kernel.org/stable/c/657e7174603f0aab2cdedc
it.kernel.org/stable/c/5ba81f82607ead85fe36f50869fc4f5661359ab8 - https://git.kernel.org/stable/c/657e7174603f0aab2cdedc64ac81edffd2a87afe - https://git.kernel.org/stable/c/2bd1faedb74dc2a2be3972abcd4239b75a3e7b00 - https://git.kernel.org/stable/c/71ae30662ec610b92644d13f79c78f76f17873b3 - https://git.kernel.org/stable/c/b24ca1cf846273361d5bd73a35de95a486a54b6d - https://git.kernel.org/stable/c/4cde554c70d7397cfa2e4116bacb4accdfb6fd48 - https://git.kernel.org/stable/c/0b238f75b65ed4462ef4cdfa718cac0ac7fce3b8 - https://git.kernel.org/stable/c/e7e7104e2d5ddf3806a28695670f21bef471f1e1
CVE ID: CVE-2022-49369 State: PUBLISHED Published: 2025-02-26T02:11:12.706Z Last Updated: 2025-10-01T19:46:53.281Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: amt: fix possible memory leak in amt_rcv() If an amt receives packets and it finds socket. If it can't find a socket, it should free a received skb. But it doesn't. So, a memory leak would possibly occur. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/60d9c020c69977e138727b3577bc6a0458325e9c - https://git.kernel.org/stable/c/4b8032d39b276c52db57ff834c300405b9da2691 - https://git.kernel.org/stable/c/1a1a0e80e005cbdc2c250
git.kernel.org/stable/c/4b8032d39b276c52db57ff834c300405b9da2691 - https://git.kernel.org/stable/c/1a1a0e80e005cbdc2c250fc858e1d8570f4e4acb
CVE ID: CVE-2022-49370 State: PUBLISHED Published: 2025-02-26T02:11:13.176Z Last Updated: 2025-10-01T19:46:53.103Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add() If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Fix this issue by calling kobject_put(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a9bfb37d6ba7c376b0d53337a4c5f5ff324bd72
st Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a9bfb37d6ba7c376b0d53337a4c5f5ff324bd725 - https://git.kernel.org/stable/c/ed38d04342dfbe9e5aca745c8b5eb4188a74f0ef - https://git.kernel.org/stable/c/c66cc3c62870a27ea8f060a7e4c1ad8d26dd3f0d - https://git.kernel.org/stable/c/a724634b2a49f6ff0177a9e19a5a92fc1545e1b7 - https://git.kernel.org/stable/c/985706bd3bbeffc8737bc05965ca8d24837bc7db - https://git.kernel.org/stable/c/fdffa4ad8f6bf1ece877edfb807f2b2c729d8578 - https://git.kernel.org/stable/c/3ba359ebe914ac3f8c6c832b28007c14c39d3766 - https://git.kernel.org/stable/c/ec752973aa721ee281d5441e497364637c626c7b - https://git.kernel.org/stable/c/660ba678f9998aca6db
//git.kernel.org/stable/c/ec752973aa721ee281d5441e497364637c626c7b - https://git.kernel.org/stable/c/660ba678f9998aca6db74f2dd912fa5124f0fa31
CVE ID: CVE-2022-49371 State: PUBLISHED Published: 2025-02-26T02:11:13.652Z Last Updated: 2025-10-01T19:46:52.917Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: driver core: fix deadlock in __device_attach In __device_attach function, The lock holding logic is as follows: ... __device_attach device_lock(dev) // get lock dev async_schedule_dev(__device_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __device_attach_async_helper will get lock dev as well, which will lead to A-A de
work limit, sync to execute func, but __device_attach_async_helper will get lock dev as well, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As shown above, when it is allowed to do async probes, because of out of memory or work limit, async work is not allowed, to do sync execute instead. it will lead to A-A deadlock because of __device_attach_async_helper getting lock dev. To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concu
we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/593b595332bd2d65e1a5c1ae7897996c157f5468 - https://git.kernel.org/stable/c/36ee9ffca8ef56c302f2855c4a5fccf61c0c1ada - https://git.kernel.org/stable/c/df6de52b80aa3b46f5ac804412355ffe2e1df93e - https://git.kernel.org/stable/c/d53a227bfcd5160ce1b61d9954901968a20651e7 - https://git.kernel.org/stable/c/34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e - https://git.kernel.org/stable/c/b232b02bf3c205b1
ps://git.kernel.org/stable/c/34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e - https://git.kernel.org/stable/c/b232b02bf3c205b13a26dcec08e53baddd8e59ed
CVE ID: CVE-2022-49372 State: PUBLISHED Published: 2025-02-26T02:11:14.119Z Last Updated: 2025-05-04T08:36:17.133Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rtx_synack() can be called from process context Laurent reported the enclosed report [1] This bug triggers with following coditions: 0) Kernel built with CONFIG_DEBUG_PREEMPT=y 1) A new passive FastOpen TCP socket is created. This FO socket waits for an ACK coming from client to be a complete ESTABLISHED one. 2) A socket operation on this socket goes through lock_sock() release_sock() dance. 3) While the socket is owned by the user in step 2), a retransmit of
ket goes through lock_sock() release_sock() dance. 3) While the socket is owned by the user in step 2), a retransmit of the SYN is received and stored in socket backlog. 4) At release_sock() time, the socket backlog is processed while in process context. 5) A SYNACK packet is cooked in response of the SYN retransmit. 6) -> tcp_rtx_synack() is called in process context. Before blamed commit, tcp_rtx_synack() was always called from BH handler, from a timer handler. Fix this by using TCP_INC_STATS() & NET_INC_STATS() which do not assume caller is in non preemptible context. [1] BUG: using __this_cpu_add() in preemptible [00000000] code: epollpep/2180 caller is tcp_rtx_synack.part.0+0x36/0xc0 CP
] BUG: using __this_cpu_add() in preemptible [00000000] code: epollpep/2180 caller is tcp_rtx_synack.part.0+0x36/0xc0 CPU: 10 PID: 2180 Comm: epollpep Tainted: G OE 5.16.0-0.bpo.4-amd64 #1 Debian 5.16.12-1~bpo11+1 Hardware name: Supermicro SYS-5039MC-H8TRF/X11SCD-F, BIOS 1.7 11/23/2021 Call Trace: <TASK> dump_stack_lvl+0x48/0x5e check_preemption_disabled+0xde/0xe0 tcp_rtx_synack.part.0+0x36/0xc0 tcp_rtx_synack+0x8d/0xa0 ? kmem_cache_alloc+0x2e0/0x3e0 ? apparmor_file_alloc_security+0x3b/0x1f0 inet_rtx_syn_ack+0x16/0x30 tcp_check_req+0x367/0x610 tcp_rcv_state_process+0x91/0xf60 ? get_nohz_timer_target+0x18/0x1a0 ? lock_timer_base+0x61/0x80 ? preempt_count_add+0x68/0xa0 tcp_v4_do_rcv+0xbd/0x270
60 ? get_nohz_timer_target+0x18/0x1a0 ? lock_timer_base+0x61/0x80 ? preempt_count_add+0x68/0xa0 tcp_v4_do_rcv+0xbd/0x270 __release_sock+0x6d/0xb0 release_sock+0x2b/0x90 sock_setsockopt+0x138/0x1140 ? __sys_getsockname+0x7e/0xc0 ? aa_sk_perm+0x3e/0x1a0 __sys_setsockopt+0x198/0x1e0 __x64_sys_setsockopt+0x21/0x30 do_syscall_64+0x38/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae References: - https://git.kernel.org/stable/c/3db889f883e65bbd3b1401279bfc1e9ed255c481 - https://git.kernel.org/stable/c/c348b0f8d035fc4bdc040796889beec7218bd1b8 - https://git.kernel.org/stable/c/58bd38cbc961fd799842b7be8c5222310f04b908 - https://git.kernel.org/stable/c/d05c2fdf8e10528bb6751bd95243e862d5402a9b - https://g
bc961fd799842b7be8c5222310f04b908 - https://git.kernel.org/stable/c/d05c2fdf8e10528bb6751bd95243e862d5402a9b - https://git.kernel.org/stable/c/0a0f7f84148445c9f02f226928803a870139d820 - https://git.kernel.org/stable/c/88cd232146207ff1d41dededed5e77c0d4438113 - https://git.kernel.org/stable/c/bdc28a8fb43cc476e33b11519235adb816ce00e8 - https://git.kernel.org/stable/c/d8e1bc6029acac796293310aacef7b7336f35b6a - https://git.kernel.org/stable/c/0a375c822497ed6ad6b5da0792a12a6f1af10c0b
CVE ID: CVE-2022-49373 State: PUBLISHED Published: 2025-02-26T02:11:14.603Z Last Updated: 2025-10-01T19:46:52.749Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: watchdog: ts4800_wdt: Fix refcount leak in ts4800_wdt_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() in some error paths. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/5b110d940417942bc87d9e4bea6d4f24e05ed483 - https://git.kernel.org/stable/c/910b1cdf6c50ae8fb222e46657d04fb181577017 - https://git.kernel.org/stable/c/7a4af
ed483 - https://git.kernel.org/stable/c/910b1cdf6c50ae8fb222e46657d04fb181577017 - https://git.kernel.org/stable/c/7a4afd8a003d6abf1f5d159c2bb67e6b7cbde253 - https://git.kernel.org/stable/c/91fa5aa53f68b85e779164b3127c7e23cad5c457 - https://git.kernel.org/stable/c/f067b5286edfd83d2d3903e8578b561599d62539 - https://git.kernel.org/stable/c/5d24df3d690809952528e7a19a43d84bc5b99d44
CVE ID: CVE-2022-49374 State: PUBLISHED Published: 2025-02-26T02:11:15.127Z Last Updated: 2025-10-01T19:46:52.564Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tipc: check attribute length for bearer name syzbot reported uninit-value: ===================================================== BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:644 [inline] BUG: KMSAN: uninit-value in string+0x4f9/0x6f0 lib/vsprintf.c:725 string_nocheck lib/vsprintf.c:644 [inline] string+0x4f9/0x6f0 lib/vsprintf.c:725 vsnprintf+0x2222/0x3650 lib/vsprintf.c:2806 vprintk_store+0x537/0x2150 kernel/printk/printk.c:2158 vprintk_emit+0x28b/0xab0 ke
ntf+0x2222/0x3650 lib/vsprintf.c:2806 vprintk_store+0x537/0x2150 kernel/printk/printk.c:2158 vprintk_emit+0x28b/0xab0 kernel/printk/printk.c:2256 vprintk_default+0x86/0xa0 kernel/printk/printk.c:2283 vprintk+0x15f/0x180 kernel/printk/printk_safe.c:50 _printk+0x18d/0x1cf kernel/printk/printk.c:2293 tipc_enable_bearer net/tipc/bearer.c:371 [inline] __tipc_nl_bearer_enable+0x2022/0x22a0 net/tipc/bearer.c:1033 tipc_nl_bearer_enable+0x6c/0xb0 net/tipc/bearer.c:1042 genl_family_rcv_msg_doit net/netlink/genetlink.c:731 [inline] - Do sanity check the attribute length for TIPC_NLA_BEARER_NAME. - Do not use 'illegal name' in printing message. Additional Analyst Notes: - CISA ADP Vulnrichment: Referenc
EARER_NAME. - Do not use 'illegal name' in printing message. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/f07670871f4d19e613740eebe210e7e9ea535973 - https://git.kernel.org/stable/c/8b91d0dfc839e67708c905648cd0e7507a2263e5 - https://git.kernel.org/stable/c/b8fac8e321044a9ac50f7185b4e9d91a7745e4b0 - https://git.kernel.org/stable/c/92a930fcf4250fe961f6238b99af0bc405799f39 - https://git.kernel.org/stable/c/292be63c382ce20673ee61dff1ee9ed4a3dcaae7 - https://git.kernel.org/stable/c/3af15272cde28fe5c8489174b8624e232c1775ec - https://git.kernel.org/stable/c/7f36f798f89bf32c0164049cb0e3fd1af613d0bb
CVE ID: CVE-2022-49375 State: PUBLISHED Published: 2025-02-26T02:11:15.627Z Last Updated: 2025-10-01T19:46:52.396Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: rtc: mt6397: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/3867f0bbb94773d41e789257abec0d14f37da217 - https://git.kernel.org/stable/c/79fa3f5758d8712df0678df98161f948fc4370e5 - https://git.kernel.org/stable/c/6ecd4d5c28408df36a1a6f0b1973f633c949ac1f - https://git
8d8712df0678df98161f948fc4370e5 - https://git.kernel.org/stable/c/6ecd4d5c28408df36a1a6f0b1973f633c949ac1f - https://git.kernel.org/stable/c/d77f28c1bc9d3043a52069fe42e4a26fbf961ebd - https://git.kernel.org/stable/c/82bfea344e8f7e9a0e0b1bf9af27552baa756620 - https://git.kernel.org/stable/c/865051de2d9eaa50630e055b73921ceaf3c4a7fc - https://git.kernel.org/stable/c/58a729c55ce3a432eb827fdaa24c7909cd3b0a6b - https://git.kernel.org/stable/c/da38e86d6cf6dd3bc65c602d998f357145aa1a0b - https://git.kernel.org/stable/c/d3b43eb505bffb8e4cdf6800c15660c001553fe6
CVE ID: CVE-2022-49376 State: PUBLISHED Published: 2025-02-26T02:11:16.118Z Last Updated: 2025-10-01T19:46:52.245Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: sd: Fix potential NULL pointer dereference If sd_probe() sees an early error before sdkp->device is initialized, sd_zbc_release_disk() is called. This causes a NULL pointer dereference when sd_is_zoned() is called inside that function. Avoid this by removing the call to sd_zbc_release_disk() in sd_probe() error path. This change is safe and does not result in zone information memory leakage because the zone information for a zoned disk is allocated only when sd_r
not result in zone information memory leakage because the zone information for a zoned disk is allocated only when sd_revalidate_disk() is called, at which point sdkp->disk_dev is fully set, resulting in sd_disk_release() being called when needed to cleanup a disk zone information using sd_zbc_release_disk(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c1f0187025905e9981000d44a92e159468b561a8 - https://git.kernel.org/stable/c/0fcb0b131cc90c8f523a293d84c58d0c7273c96f - https://git.kernel.org/stable/c/78f8e96df06e2d04d82d4071c299b59d28744f47 - https://git.kernel.org/stable/c/3733439593ad12f7b54ae35c273ea6f15d692de3 - https://git.kernel.org/
071c299b59d28744f47 - https://git.kernel.org/stable/c/3733439593ad12f7b54ae35c273ea6f15d692de3 - https://git.kernel.org/stable/c/05fbde3a77a4f1d62e4c4428f384288c1f1a0be5
CVE ID: CVE-2022-49377 State: PUBLISHED Published: 2025-02-26T02:11:16.607Z Last Updated: 2025-05-04T08:36:23.254Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: blk-mq: don't touch ->tagset in blk_mq_get_sq_hctx blk_mq_run_hw_queues() could be run when there isn't queued request and after queue is cleaned up, at that time tagset is freed, because tagset lifetime is covered by driver, and often freed after blk_cleanup_queue() returns. So don't touch ->tagset for figuring out current default hctx by the mapping built in request queue, so use-after-free on tagset can be avoided. Meantime this way should be fast than retrieving ma
built in request queue, so use-after-free on tagset can be avoided. Meantime this way should be fast than retrieving mapping from tagset. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/460aa288c5cd0544dcf933a2f0ad0e8c6d2d35ff - https://git.kernel.org/stable/c/b140bac470b4f707cda59c7266214246238661df - https://git.kernel.org/stable/c/70fdd922c7bf8949f8df109cf2635dff64c90392 - https://git.kernel.org/stable/c/5d05426e2d5fd7df8afc866b78c36b37b00188b7
CVE ID: CVE-2022-49378 State: PUBLISHED Published: 2025-02-26T02:11:17.084Z Last Updated: 2025-05-04T08:36:24.847Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: sfc: fix considering that all channels have TX queues Normally, all channels have RX and TX queues, but this is not true if modparam efx_separate_tx_channels=1 is used. In that cases, some channels only have RX queues and others only TX queues (or more preciselly, they have them allocated, but not initialized). Fix efx_channel_has_tx_queues to return the correct value for this case too. Messages shown at probe time before the fix: sfc 0000:03:00.0 ens6f0np0: MC command
the correct value for this case too. Messages shown at probe time before the fix: sfc 0000:03:00.0 ens6f0np0: MC command 0x82 inlen 544 failed rc=-22 (raw=0) arg=0 ------------[ cut here ]------------ netdevice: ens6f0np0: failed to initialise TXQ -1 WARNING: CPU: 1 PID: 626 at drivers/net/ethernet/sfc/ef10.c:2393 efx_ef10_tx_init+0x201/0x300 [sfc] [...] stripped RIP: 0010:efx_ef10_tx_init+0x201/0x300 [sfc] [...] stripped Call Trace: efx_init_tx_queue+0xaa/0xf0 [sfc] efx_start_channels+0x49/0x120 [sfc] efx_start_all+0x1f8/0x430 [sfc] efx_net_open+0x5a/0xe0 [sfc] __dev_open+0xd0/0x190 __dev_change_flags+0x1b3/0x220 dev_change_flags+0x21/0x60 [...] stripped Messages shown at remove time before
0xd0/0x190 __dev_change_flags+0x1b3/0x220 dev_change_flags+0x21/0x60 [...] stripped Messages shown at remove time before the fix: sfc 0000:03:00.0 ens6f0np0: failed to flush 10 queues sfc 0000:03:00.0 ens6f0np0: failed to flush queues References: - https://git.kernel.org/stable/c/8f81a4113e1e574d2cbde4f2cd599380a9189c0f - https://git.kernel.org/stable/c/5567d69b95b9c07e1c56f15cf0301251d12e5f97 - https://git.kernel.org/stable/c/e7e8d5e25dc762b70f9c88ec6b7d451d0816eead - https://git.kernel.org/stable/c/913d45f02d346ce41c4aad057eaf53a8ed449dc3 - https://git.kernel.org/stable/c/2e102b53f8a778f872dc137f4c7ac548705817aa
CVE ID: CVE-2022-49379 State: PUBLISHED Published: 2025-02-26T02:11:17.795Z Last Updated: 2025-05-04T08:36:25.934Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction Mounting NFS rootfs was timing out when deferred_probe_timeout was non-zero [1]. This was because ip_auto_config() initcall times out waiting for the network interfaces to show up when deferred_probe_timeout was non-zero. While ip_auto_config() calls wait_for_device_probe() to make sure any currently running deferred probe work or asynchronous probe finishes, that wasn't sufficient to account