Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
ter()). To fix this, we try to register each such matching VF( if it is visible as a netdevice) at the end of netvsc_probe. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/bcb7164258d0a9a8aa2e73ddccc2d78f67d2519d - https://git.kernel.org/stable/c/c7441c77c91e47f653104be8353b44a3366a5366 - https://git.kernel.org/stable/c/5b10a88f64c0315cfdef45de0aaaa4eef57de0b7 - https://git.kernel.org/stable/c/b6d46f306b3964d05055ddaa96b58cd8bd3a472c - https://git.kernel.org/stable/c/309ef7de5d840e17607e7d65cbf297c0564433ef - https://git.kernel.org/stable/c/a71302c8638939c45e4ba5a99ea438185fd3f418 - https://git.kernel.org/stable/c/4d29
4433ef - https://git.kernel.org/stable/c/a71302c8638939c45e4ba5a99ea438185fd3f418 - https://git.kernel.org/stable/c/4d29a58d96a78728cb01ee29ed70dc4bd642f135 - https://git.kernel.org/stable/c/9cae43da9867412f8bd09aee5c8a8dc5e8dc3dc2
CVE ID: CVE-2024-26821 State: REJECTED Published: 2024-04-17T09:43:48.600Z Last Updated: 2024-05-16T12:22:39.501Z Description: No description available.
CVE ID: CVE-2024-26822 State: PUBLISHED Published: 2024-04-17T09:43:49.221Z Last Updated: 2025-05-04T12:54:51.429Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: smb: client: set correct id, uid and cruid for multiuser automounts When uid, gid and cruid are not specified, we need to dynamically set them into the filesystem context used for automounting otherwise they'll end up reusing the values from the parent mount. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c2aa2718cda2d56b4a551cb40043e9abc9684626 - https://git.kernel.org/stable/c/7590ba9057c6d74c
ps://git.kernel.org/stable/c/c2aa2718cda2d56b4a551cb40043e9abc9684626 - https://git.kernel.org/stable/c/7590ba9057c6d74c66f3b909a383ec47cd2f27fb - https://git.kernel.org/stable/c/4508ec17357094e2075f334948393ddedbb75157
CVE ID: CVE-2024-26823 State: PUBLISHED Published: 2024-04-17T09:43:49.850Z Last Updated: 2025-05-04T08:57:20.077Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Restore quirk probing for ACPI-based systems While refactoring the way the ITSs are probed, the handling of quirks applicable to ACPI-based platforms was lost. As a result, systems such as HIP07 lose their GICv4 functionnality, and some other may even fail to boot, unless they are configured to boot with DT. Move the enabling of quirks into its_probe_one(), making it common to all firmware implementations. Additional Analyst Notes: - CVE Program Con
irks into its_probe_one(), making it common to all firmware implementations. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/91a80fff3eeed928b6fba21271f6a9719b22a5d8 - https://git.kernel.org/stable/c/4c60c611441f1f1e5de8e00e98ee5a4970778a00 - https://git.kernel.org/stable/c/8b02da04ad978827e5ccd675acf170198f747a7a
CVE ID: CVE-2024-26824 State: PUBLISHED Published: 2024-04-17T09:43:50.485Z Last Updated: 2025-05-04T08:57:21.556Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: algif_hash - Remove bogus SGL free on zero-length error path When a zero-length message is hashed by algif_hash, and an error is triggered, it tries to free an SG list that was never allocated in the first place. Fix this by not freeing the SG list on the zero-length error path. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9c82920359b7c1eddaf72069bcfe0ffddf088cd0 - https://git.kernel.o
nrichment: References: - https://git.kernel.org/stable/c/9c82920359b7c1eddaf72069bcfe0ffddf088cd0 - https://git.kernel.org/stable/c/775f3c1882a493168e08fdb8cde0865c8f3a8a29 - https://git.kernel.org/stable/c/24c890dd712f6345e382256cae8c97abb0406b70
CVE ID: CVE-2024-26825 State: PUBLISHED Published: 2024-04-17T09:43:51.114Z Last Updated: 2025-05-04T08:57:22.904Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nfc: nci: free rx_data_reassembly skb on NCI device cleanup rx_data_reassembly skb is stored during NCI data exchange for processing fragmented packets. It is dropped only when the last fragment is processed or when an NTF packet with NCI_OP_RF_DEACTIVATE_NTF opcode is received. However, the NCI device may be deallocated before that which leads to skb leak. As by design the rx_data_reassembly skb is bound to the NCI device and nothing prevents the device to be freed be
leak. As by design the rx_data_reassembly skb is bound to the NCI device and nothing prevents the device to be freed before the skb is processed in some way and cleaned, free it on the NCI device cleanup. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7e9a8498658b398bf11b8e388005fa54e40aed81 - https://git.kernel.org/stable/c/71349abe3aba7fedcab5b3fcd7aa82371fb5ccbf - https://git.kernel.org/stable/c/2f6d16f0520d6505241629ee2f5c131b547d5f9d - https://git.kernel.org/stable/c/471c9ede8061357b43a116fa692e70d91941ac23 - https://git.kernel.org/stable/c/5c
547d5f9d - https://git.kernel.org/stable/c/471c9ede8061357b43a116fa692e70d91941ac23 - https://git.kernel.org/stable/c/5c0c5ffaed73cbae6c317374dc32ba6cacc60895 - https://git.kernel.org/stable/c/16d3f507b0fa70453dc54550df093d6e9ac630c1 - https://git.kernel.org/stable/c/a3d90fb5c23f29ba59c04005ae76c5228cef2be9 - https://git.kernel.org/stable/c/bfb007aebe6bff451f7f3a4be19f4f286d0d5d9c
CVE ID: CVE-2024-26826 State: PUBLISHED Published: 2024-04-17T09:43:51.741Z Last Updated: 2025-05-04T08:57:24.333Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mptcp: fix data re-injection from stale subflow When the MPTCP PM detects that a subflow is stale, all the packet scheduler must re-inject all the mptcp-level unacked data. To avoid acquiring unneeded locks, it first try to check if any unacked data is present at all in the RTX queue, but such check is currently broken, as it uses TCP-specific helper on an MPTCP socket. Funnily enough fuzzers and static checkers are happy, as the accessed memory still belongs to the mp
on an MPTCP socket. Funnily enough fuzzers and static checkers are happy, as the accessed memory still belongs to the mptcp_sock struct, and even from a functional perspective the recovery completed successfully, as the short-cut test always failed. A recent unrelated TCP change - commit d5fed5addb2b ("tcp: reorganize tcp_sock fast path variables") - exposed the issue, as the tcp field reorganization makes the mptcp code always skip the re-inection. Fix the issue dropping the bogus call: we are on a slow path, the early optimization proved once again to be evil. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6f95120f8
Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6f95120f898b40d13fd441225ef511307853c9c2 - https://git.kernel.org/stable/c/6673d9f1c2cd984390550dbdf7d5ae07b20abbf8 - https://git.kernel.org/stable/c/b609c783c535493aa3fca22c7e40a120370b1ca5 - https://git.kernel.org/stable/c/624902eab7abcb8731b333ec73f206d38d839cd8 - https://git.kernel.org/stable/c/b6c620dc43ccb4e802894e54b651cf81495e9598
CVE ID: CVE-2024-26827 State: REJECTED Published: 2024-04-17T09:43:52.377Z Last Updated: 2024-04-18T14:51:25.379Z Description: No description available.
CVE ID: CVE-2024-26828 State: PUBLISHED Published: 2024-04-17T09:43:52.995Z Last Updated: 2025-05-04T08:57:25.809Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cifs: fix underflow in parse_server_interfaces() In this loop, we step through the buffer and after each item we check if the size_left is greater than the minimum size we need. However, the problem is that "bytes_left" is type ssize_t while sizeof() is type size_t. That means that because of type promotion, the comparison is done as an unsigned and if we have negative bytes left the loop continues instead of ending. Additional Analyst Notes: - CISA ADP Vulnrichment: -
f we have negative bytes left the loop continues instead of ending. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7190353835b4a219abb70f90b06cdcae97f11512 - https://git.kernel.org/stable/c/f7ff1c89fb6e9610d2b01c1821727729e6609308 - https://git.kernel.org/stable/c/df2af9fdbc4ddde18a3371c4ca1a86596e8be301 - https://git.kernel.org/stable/c/cffe487026be13eaf37ea28b783d9638ab147204
CVE ID: CVE-2024-26829 State: PUBLISHED Published: 2024-04-17T10:03:13.088Z Last Updated: 2025-06-19T12:39:16.644Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: ir_toy: fix a memleak in irtoy_tx When irtoy_command fails, buf should be freed since it is allocated by irtoy_tx, or there is a memleak. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/207557e393a135c1b6fe1df7cc0741d2c1789fff - https://git.kernel.org/stable/c/be76ad74a43f90f340f9f479e6b04f02125f6aef - https://git.kernel.org/stable/c/7219a692ffc00089015ada33b85b334d1a4b6e8e - https://git.k
f90f340f9f479e6b04f02125f6aef - https://git.kernel.org/stable/c/7219a692ffc00089015ada33b85b334d1a4b6e8e - https://git.kernel.org/stable/c/b37259448bbc70af1d0e52a9dd5559a9c29c9621 - https://git.kernel.org/stable/c/dc9ceb90c4b42c6e5c6757df1d6257110433788e
CVE ID: CVE-2024-26830 State: PUBLISHED Published: 2024-04-17T09:43:53.643Z Last Updated: 2025-05-04T08:57:28.813Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: i40e: Do not allow untrusted VF to remove administratively set MAC Currently when PF administratively sets VF's MAC address and the VF is put down (VF tries to delete all MACs) then the MAC is removed from MAC filters and primary VF MAC is zeroed. Do not allow untrusted VF to remove primary MAC when it was set administratively by PF. Reproducer: 1) Create VF 2) Set VF interface up 3) Administratively set the VF's MAC 4) Put VF interface down [root@host ~]# echo 1 > /sy
eate VF 2) Set VF interface up 3) Administratively set the VF's MAC 4) Put VF interface down [root@host ~]# echo 1 > /sys/class/net/enp2s0f0/device/sriov_numvfs [root@host ~]# ip link set enp2s0f0v0 up [root@host ~]# ip link set enp2s0f0 vf 0 mac fe:6c:b5:da:c7:7d [root@host ~]# ip link show enp2s0f0 23: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 3c:ec:ef:b7:dd:04 brd ff:ff:ff:ff:ff:ff vf 0 link/ether fe:6c:b5:da:c7:7d brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off [root@host ~]# ip link set enp2s0f0v0 down [root@host ~]# ip link show enp2s0f0 23: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
]# ip link set enp2s0f0v0 down [root@host ~]# ip link show enp2s0f0 23: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 3c:ec:ef:b7:dd:04 brd ff:ff:ff:ff:ff:ff vf 0 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/1c981792e4ccbc134b468797acdd7781959e6893 - https://git.kernel.org/stable/c/be147926140ac48022c9605d7ab0a67387e4b404 - https://git.kernel.org/stable/c/d250a81ba813a93563be68072c563aa1e346346d - https://git.kernel.org/stable/c/73d9629e1c8c1982f13
//git.kernel.org/stable/c/d250a81ba813a93563be68072c563aa1e346346d - https://git.kernel.org/stable/c/73d9629e1c8c1982f13688c4d1019c3994647ccc
CVE ID: CVE-2024-26831 State: PUBLISHED Published: 2024-04-17T09:43:54.270Z Last Updated: 2025-05-04T12:54:52.504Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/handshake: Fix handshake_req_destroy_test1 Recently, handshake_req_destroy_test1 started failing: Expected handshake_req_destroy_test == req, but handshake_req_destroy_test == 0000000000000000 req == 0000000060f99b40 not ok 11 req_destroy works This is because "sock_release(sock)" was replaced with "fput(filp)" to address a memory leak. Note that sock_release() is synchronous but fput() usually delays the final close and clean-up. The delay is not consequential in
sock_release() is synchronous but fput() usually delays the final close and clean-up. The delay is not consequential in the other cases that were changed but handshake_req_destroy_test1 is testing that handshake_req_cancel() followed by closing the file actually does call the ->hp_destroy method. Thus the PTR_EQ test at the end has to be sure that the final close is complete before it checks the pointer. We cannot use a completion here because if ->hp_destroy is never called (ie, there is an API bug) then the test will hang. Reported by: Guenter Roeck <linux@roeck-us.net> Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c
dditional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/d74226e03df1bf19848f18344401f254345af912 - https://git.kernel.org/stable/c/7f97805b8df6e33850e225e6bd3ebd9e246920af - https://git.kernel.org/stable/c/4e1d71cabb19ec2586827adfc60d68689c68c194
CVE ID: CVE-2024-26832 State: PUBLISHED Published: 2024-04-17T10:10:01.016Z Last Updated: 2025-05-04T12:54:53.558Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mm: zswap: fix missing folio cleanup in writeback race path In zswap_writeback_entry(), after we get a folio from __read_swap_cache_async(), we grab the tree lock again to check that the swap entry was not invalidated and recycled. If it was, we delete the folio we just added to the swap cache and exit. However, __read_swap_cache_async() returns the folio locked when it is newly allocated, which is always true for this path, and the folio is ref'd. Make sure to unlock
olio locked when it is newly allocated, which is always true for this path, and the folio is ref'd. Make sure to unlock and put the folio before returning. This was discovered by code inspection, probably because this path handles a race condition that should not happen often, and the bug would not crash the system, it will only strand the folio indefinitely. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/14f1992430ef9e647b02aa8ca12c5bcb9a1dffea - https://git.kernel.org/stable/c/6156277d1b26cb3fdb6fcbf0686ab78268571644 - https://git.kernel.org/stable/c/e2891c763aa2cff74dd6b5e978411ccf0cf94abe - https://git.kernel.org/
bf0686ab78268571644 - https://git.kernel.org/stable/c/e2891c763aa2cff74dd6b5e978411ccf0cf94abe - https://git.kernel.org/stable/c/e3b63e966cac0bf78aaa1efede1827a252815a1d
CVE ID: CVE-2024-26833 State: PUBLISHED Published: 2024-04-17T10:10:01.654Z Last Updated: 2025-05-04T08:57:33.191Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak in dm_sw_fini() After destroying dmub_srv, the memory associated with it is not freed, causing a memory leak: unreferenced object 0xffff896302b45800 (size 1024): comm "(udev-worker)", pid 222, jiffies 4294894636 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 6265fd77): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x34
0 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 6265fd77): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x340 [<ffffffffc0ea4a94>] dm_dmub_sw_init+0xb4/0x450 [amdgpu] [<ffffffffc0ea4e55>] dm_sw_init+0x15/0x2b0 [amdgpu] [<ffffffffc0ba8557>] amdgpu_device_init+0x1417/0x24e0 [amdgpu] [<ffffffffc0bab285>] amdgpu_driver_load_kms+0x15/0x190 [amdgpu] [<ffffffffc0ba09c7>] amdgpu_pci_probe+0x187/0x4e0 [amdgpu] [<ffffffff9968fd1e>] local_pci_probe+0x3e/0x90 [<ffffffff996918a3>] pci_device_probe+0xc3/0x230 [<ffffffff99805872>] really_probe+0xe2/0x480 [<ffffffff99805c98>] __driver_probe_device+0x78/0x160 [<ffffffff99805daf>] driver_probe_device+0x1f/0x90 [<ffffffff9980601e>] __driver_attach+
_driver_probe_device+0x78/0x160 [<ffffffff99805daf>] driver_probe_device+0x1f/0x90 [<ffffffff9980601e>] __driver_attach+0xce/0x1c0 [<ffffffff99803170>] bus_for_each_dev+0x70/0xc0 [<ffffffff99804822>] bus_add_driver+0x112/0x210 [<ffffffff99807245>] driver_register+0x55/0x100 [<ffffffff990012d1>] do_one_initcall+0x41/0x300 Fix this by freeing dmub_srv after destroying it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/b49b022f7dfce85eb77d0d987008fde5c01d7857 - https://git.kernel.org/stable/c/33f649f1b1cea39ed360e6c12bba4fac83118e6e - https://git.kernel.org/stable/c/58168005337eabef345a872be3f87d0215ff3b30 - https://git.
cea39ed360e6c12bba4fac83118e6e - https://git.kernel.org/stable/c/58168005337eabef345a872be3f87d0215ff3b30 - https://git.kernel.org/stable/c/10c6b90e975358c17856a578419dc449887899c2 - https://git.kernel.org/stable/c/541e79265ea7e339a7c4a462feafe9f8f996e04b - https://git.kernel.org/stable/c/bae67893578d608e35691dcdfa90c4957debf1d3
CVE ID: CVE-2024-26834 State: PUBLISHED Published: 2024-04-17T10:10:02.282Z Last Updated: 2025-05-04T08:57:34.639Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_flow_offload: release dst in case direct xmit path is used Direct xmit does not use it since it calls dev_queue_xmit() to send packets, hence it calls dst_release(). kmemleak reports: unreferenced object 0xffff88814f440900 (size 184): comm "softirq", pid 0, jiffies 4294951896 hex dump (first 32 bytes): 00 60 5b 04 81 88 ff ff 00 e6 e8 82 ff ff ff ff .`[............. 21 0b 50 82 ff ff ff ff 00 00 00 00 00 00 00 00 !.P............. backtrace (crc cb2bf5d6)
2 ff ff ff ff .`[............. 21 0b 50 82 ff ff ff ff 00 00 00 00 00 00 00 00 !.P............. backtrace (crc cb2bf5d6): [<000000003ee17107>] kmem_cache_alloc+0x286/0x340 [<0000000021a5de2c>] dst_alloc+0x43/0xb0 [<00000000f0671159>] rt_dst_alloc+0x2e/0x190 [<00000000fe5092c9>] __mkroute_output+0x244/0x980 [<000000005fb96fb0>] ip_route_output_flow+0xc0/0x160 [<0000000045367433>] nf_ip_route+0xf/0x30 [<0000000085da1d8e>] nf_route+0x2d/0x60 [<00000000d1ecd1cb>] nft_flow_route+0x171/0x6a0 [nft_flow_offload] [<00000000d9b2fb60>] nft_flow_offload_eval+0x4e8/0x700 [nft_flow_offload] [<000000009f447dbb>] expr_call_ops_eval+0x53/0x330 [nf_tables] [<00000000072e1be6>] nft_do_chain+0x17c/0x840 [nf_tab
ad] [<000000009f447dbb>] expr_call_ops_eval+0x53/0x330 [nf_tables] [<00000000072e1be6>] nft_do_chain+0x17c/0x840 [nf_tables] [<00000000d0551029>] nft_do_chain_inet+0xa1/0x210 [nf_tables] [<0000000097c9d5c6>] nf_hook_slow+0x5b/0x160 [<0000000005eccab1>] ip_forward+0x8b6/0x9b0 [<00000000553a269b>] ip_rcv+0x221/0x230 [<00000000412872e5>] __netif_receive_skb_one_core+0xfe/0x110 Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/13b57b5cd591d5b22f9bbf047b2922967de411f3 - https://git.kernel.org/stable/c/a6cafdb49a7bbf4a88367db209703eee6941e023 - https://git.kernel.org/stable/c/9256ab9232e35a16af9c30fa4e522e6d1bd3605a - https://
b49a7bbf4a88367db209703eee6941e023 - https://git.kernel.org/stable/c/9256ab9232e35a16af9c30fa4e522e6d1bd3605a - https://git.kernel.org/stable/c/2d17cf10179a7de6d8f0128168b84ad0b4a1863f - https://git.kernel.org/stable/c/8762785f459be1cfe6fcf7285c123aad6a3703f0
CVE ID: CVE-2024-26835 State: PUBLISHED Published: 2024-04-17T10:10:02.907Z Last Updated: 2025-05-04T08:57:35.908Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: set dormant flag on hook register failure We need to set the dormant flag again if we fail to register the hooks. During memory pressure hook registration can fail and we end up with a table marked as active but no registered hooks. On table/base chain deletion, nf_tables will attempt to unregister the hook again which yields a warn splat from the nftables core. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References
arn splat from the nftables core. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a6411f3c48f991c19aaf9a24fce36865fbba28d7 - https://git.kernel.org/stable/c/ae4360cbd385f0d7a8a86d5723e50448cc6318f3 - https://git.kernel.org/stable/c/31ea574aeca1aa488e18716459bde057217637af - https://git.kernel.org/stable/c/664264a5c55bf97a9c571c557d477b75416199be - https://git.kernel.org/stable/c/0c9302a6da262e6ab6a6c1d30f04a6130ed97376 - https://git.kernel.org/stable/c/f2135bbf14949687e96cabb13d8a91ae3deb9069 - https://git.kernel.org/stable/c/6f2496366426cec18ba53f1c7f6c3ac307ca6a95 - https://git.kernel.org/stable/c/bccebf64701735533c8
//git.kernel.org/stable/c/6f2496366426cec18ba53f1c7f6c3ac307ca6a95 - https://git.kernel.org/stable/c/bccebf64701735533c8db37773eeacc6566cc8ec
CVE ID: CVE-2024-26836 State: PUBLISHED Published: 2024-04-17T10:10:03.539Z Last Updated: 2025-05-04T08:57:37.100Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: platform/x86: think-lmi: Fix password opcode ordering for workstations The Lenovo workstations require the password opcode to be run before the attribute value is changed (if Admin password is enabled). Tested on some Thinkpads to confirm they are OK with this order too. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/2deb10a99671afda30f834e95e5b992a805bba6a - https://git.kernel.org/stable/c/2bfb
ences: - https://git.kernel.org/stable/c/2deb10a99671afda30f834e95e5b992a805bba6a - https://git.kernel.org/stable/c/2bfbe1e0aed00ba51d58573c79452fada3f62ed4 - https://git.kernel.org/stable/c/6f7d0f5fd8e440c3446560100ac4ff9a55eec340
CVE ID: CVE-2024-26837 State: PUBLISHED Published: 2024-04-17T10:10:04.164Z Last Updated: 2025-05-04T08:57:38.464Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: bridge: switchdev: Skip MDB replays of deferred events on offload Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration. While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was gen
n of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event. The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed. This is only an issue when replaying additions. While deletion events may still be pendin