Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
smc_pnet_netdev_event() is also calling smc_pnet_add_base_pnetid() when handling NETDEV_UP event. [1] extract of typical syzbot reports 2 locks held by syz-executor.3/12252: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.4/12253: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: s
++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.1/12257: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.2/12261: #0: ffffffff8f
+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.2/12261: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.0/12265: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffff
#1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.3/12268: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.4/12271: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 n
2 locks held by syz-executor.4/12271: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.1/12274: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0
netids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 2 locks held by syz-executor.2/12280: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4c7/0x7b0 net/core/net_namespace.c:491 #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline] #1: ffffffff8f375b88 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x10a/0x1e0 net/smc/smc_pnet.c:878 Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/bc4d1ebca11b4f194e262326bd45938e857c59d2 - https://git.kernel.org/
chment: References: - https://git.kernel.org/stable/c/bc4d1ebca11b4f194e262326bd45938e857c59d2 - https://git.kernel.org/stable/c/b9117dc783c0ab0a3866812f70e07bf2ea071ac4 - https://git.kernel.org/stable/c/d7ee3bf0caf599c14db0bf4af7aacd6206ef8a23 - https://git.kernel.org/stable/c/a2e6bffc0388526ed10406040279a693d62b36ec - https://git.kernel.org/stable/c/6e920422e7104928f760fc0e12b6d65ab097a2e7 - https://git.kernel.org/stable/c/00af2aa93b76b1bade471ad0d0525d4d29ca5cc0
CVE ID: CVE-2024-35935 State: PUBLISHED Published: 2024-05-19T10:10:42.319Z Last Updated: 2025-05-04T09:08:46.079Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: send: handle path ref underflow in header iterate_inode_ref() Change BUG_ON to proper error handling if building the path buffer fails. The pointers are not printed so we don't accidentally leak kernel addresses. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/be2b6bcc936ae17f42fff6494106a5660b35d8d3 - https://git.kernel.org/stable/c/024529c27c8b4b273325a169e078337c8279e229 - https://git.k
ae17f42fff6494106a5660b35d8d3 - https://git.kernel.org/stable/c/024529c27c8b4b273325a169e078337c8279e229 - https://git.kernel.org/stable/c/4720d590c4cb5d9ffa0060b89743651cc7e995f9 - https://git.kernel.org/stable/c/2f6174fd4ccf403b42b3d5f0d1b6b496a0e5330a - https://git.kernel.org/stable/c/9ae356c627b493323e1433dcb27a26917668c07c - https://git.kernel.org/stable/c/c1363ed8867b81ea169fba2ccc14af96a85ed183 - https://git.kernel.org/stable/c/03938619a1e718b6168ae4528e1b0f979293f1a5 - https://git.kernel.org/stable/c/3c6ee34c6f9cd12802326da26631232a61743501
CVE ID: CVE-2024-35936 State: PUBLISHED Published: 2024-05-19T10:10:42.967Z Last Updated: 2025-05-04T09:08:47.348Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() The unhandled case in btrfs_relocate_sys_chunks() loop is a corruption, as it could be caused only by two impossible conditions: - at first the search key is set up to look for a chunk tree item, with offset -1, this is an inexact search and the key->offset will contain the correct offset upon a successful search, a valid chunk tree item cannot have an offset -1 - after first successful search, the fo
ffset upon a successful search, a valid chunk tree item cannot have an offset -1 - after first successful search, the found_key corresponds to a chunk item, the offset is decremented by 1 before the next loop, it's impossible to find a chunk item there due to alignment and size constraints Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/bebd9e0ff90034875c5dfe4bd514fd7055fc7a89 - https://git.kernel.org/stable/c/576164bd01bd795f8b09fb194b493103506b33c9 - https://git.kernel.org/stable/c/87299cdaae757f3f41212146cfb5b3af416b8385 - https://git.kernel.org/stable/c/d1ffa4ae2d591fdd40471074e79954ec45f147f7 - https://git.kernel.
1212146cfb5b3af416b8385 - https://git.kernel.org/stable/c/d1ffa4ae2d591fdd40471074e79954ec45f147f7 - https://git.kernel.org/stable/c/36c2a2863bc3896243eb724dc3fd4cf9aea633f2 - https://git.kernel.org/stable/c/0d23b34c68c46cd225b55868bc8a269e3134816d - https://git.kernel.org/stable/c/1f9212cdbd005bc55f2b7422e7b560d9c02bd1da - https://git.kernel.org/stable/c/7411055db5ce64f836aaffd422396af0075fdc99
CVE ID: CVE-2024-35937 State: PUBLISHED Published: 2024-05-19T10:10:43.615Z Last Updated: 2025-11-03T21:55:02.670Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: check A-MSDU format more carefully If it looks like there's another subframe in the A-MSDU but the header isn't fully there, we can end up reading data out of bounds, only to discard later. Make this a bit more careful and check if the subframe header can even be present. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9eb3bc0973d084423a6df21cf2c74692ff05647e - https://git.kernel.
lnrichment: References: - https://git.kernel.org/stable/c/9eb3bc0973d084423a6df21cf2c74692ff05647e - https://git.kernel.org/stable/c/5d7a8585fbb31e88fb2a0f581b70667d3300d1e9 - https://git.kernel.org/stable/c/16da1e1dac23be45ef6e23c41b1508c400e6c544 - https://git.kernel.org/stable/c/9ad7974856926129f190ffbe3beea78460b3b7cc
CVE ID: CVE-2024-35938 State: PUBLISHED Published: 2024-05-19T10:10:44.279Z Last Updated: 2025-05-04T09:08:49.797Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: decrease MHI channel buffer length to 8KB Currently buf_len field of ath11k_mhi_config_qca6390 is assigned with 0, making MHI use a default size, 64KB, to allocate channel buffers. This is likely to fail in some scenarios where system memory is highly fragmented and memory compaction or reclaim is not allowed. There is a fail report which is caused by it: kworker/u32:45: page allocation failure: order:4, mode:0x40c00(GFP_NOIO|__GFP_COMP), nodemask=(null),
h is caused by it: kworker/u32:45: page allocation failure: order:4, mode:0x40c00(GFP_NOIO|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 CPU: 0 PID: 19318 Comm: kworker/u32:45 Not tainted 6.8.0-rc3-1.gae4495f-default #1 openSUSE Tumbleweed (unreleased) 493b6d5b382c603654d7a81fc3c144d59a1dfceb Workqueue: events_unbound async_run_entry_fn Call Trace: <TASK> dump_stack_lvl+0x47/0x60 warn_alloc+0x13a/0x1b0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __alloc_pages_direct_compact+0xab/0x210 __alloc_pages_slowpath.constprop.0+0xd3e/0xda0 __alloc_pages+0x32d/0x350 ? mhi_prepare_channel+0x127/0x2d0 [mhi 40df44e07c05479f7a6e7b90fba9f0e0031a7814] __kmalloc_large_node+0x72/0x110 __kmalloc+0x37c/0x480
channel+0x127/0x2d0 [mhi 40df44e07c05479f7a6e7b90fba9f0e0031a7814] __kmalloc_large_node+0x72/0x110 __kmalloc+0x37c/0x480 ? mhi_map_single_no_bb+0x77/0xf0 [mhi 40df44e07c05479f7a6e7b90fba9f0e0031a7814] ? mhi_prepare_channel+0x127/0x2d0 [mhi 40df44e07c05479f7a6e7b90fba9f0e0031a7814] mhi_prepare_channel+0x127/0x2d0 [mhi 40df44e07c05479f7a6e7b90fba9f0e0031a7814] __mhi_prepare_for_transfer+0x44/0x80 [mhi 40df44e07c05479f7a6e7b90fba9f0e0031a7814] ? __pfx_____mhi_prepare_for_transfer+0x10/0x10 [mhi 40df44e07c05479f7a6e7b90fba9f0e0031a7814] device_for_each_child+0x5c/0xa0 ? __pfx_pci_pm_resume+0x10/0x10 ath11k_core_resume+0x65/0x100 [ath11k a5094e22d7223135c40d93c8f5321cf09fd85e4e] ? srso_alias_retu
ci_pm_resume+0x10/0x10 ath11k_core_resume+0x65/0x100 [ath11k a5094e22d7223135c40d93c8f5321cf09fd85e4e] ? srso_alias_return_thunk+0x5/0xfbef5 ath11k_pci_pm_resume+0x32/0x60 [ath11k_pci 830b7bfc3ea80ebef32e563cafe2cb55e9cc73ec] ? srso_alias_return_thunk+0x5/0xfbef5 dpm_run_callback+0x8c/0x1e0 device_resume+0x104/0x340 ? __pfx_dpm_watchdog_handler+0x10/0x10 async_resume+0x1d/0x30 async_run_entry_fn+0x32/0x120 process_one_work+0x168/0x330 worker_thread+0x2f5/0x410 ? __pfx_worker_thread+0x10/0x10 kthread+0xe8/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> Actually those buffers are used only by QMI target -> host communication
d+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> Actually those buffers are used only by QMI target -> host communication. And for WCN6855 and QCA6390, the largest packet size for that is less than 6KB. So change buf_len field to 8KB, which results in order 1 allocation if page size is 4KB. In this way, we can at least save some memory, and as well as decrease the possibility of allocation failure in those scenarios. Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/805a1cdde82fec00c7471a393f4bb437b2741559 - https://git.kernel.org/sta
ner: References: - https://git.kernel.org/stable/c/805a1cdde82fec00c7471a393f4bb437b2741559 - https://git.kernel.org/stable/c/6597a6687af54e2cb58371cf8f6ee4dd85c537de - https://git.kernel.org/stable/c/138fdeac75fb7512a7f9f1c3b236cd2e754af793 - https://git.kernel.org/stable/c/ae5876b3b7b2243d874e2afa099e7926122087a1 - https://git.kernel.org/stable/c/1cca1bddf9ef080503c15378cecf4877f7510015
CVE ID: CVE-2024-35939 State: PUBLISHED Published: 2024-05-19T10:10:44.931Z Last Updated: 2025-05-04T09:08:51.275Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dma-direct: Leak pages on dma_set_decrypted() failure On TDX it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. DMA could free decrypted/shared pages if dma_set_decrypted() fails. This
h could lead to functional or security issues. DMA could free decrypted/shared pages if dma_set_decrypted() fails. This should be a rare case. Just leak the pages in this case instead of freeing them. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/4e0cfb25d49da2e6261ad582f58ffa5b5dd8c8e9 - https://git.kernel.org/stable/c/4031b72ca747a1e6e9ae4fa729e765b43363d66a - https://git.kernel.org/stable/c/b57326c96b7bc7638aa8c44e12afa2defe0c934c - https://git.kernel.org/stable/c/b9fa16949d18e06bdf728a560f5c8af56d2bdcaf
CVE ID: CVE-2024-35940 State: PUBLISHED Published: 2024-05-19T10:10:45.582Z Last Updated: 2025-05-04T09:08:52.423Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pstore/zone: Add a null pointer check to the psz_kmsg_read kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the pointer validity. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/98e2b97acb875d65bdfc75fc408e67975cef3041 - https://git.kernel.org/stable/c/0ff96ec22a84d80a18d7ae8ca7eb111c34ee33bb - https://g
acb875d65bdfc75fc408e67975cef3041 - https://git.kernel.org/stable/c/0ff96ec22a84d80a18d7ae8ca7eb111c34ee33bb - https://git.kernel.org/stable/c/635594cca59f9d7a8e96187600c34facb8bc0682 - https://git.kernel.org/stable/c/ec7256887d072f98c42cdbef4dcc80ddf84c7a70 - https://git.kernel.org/stable/c/6f9f2e498eae7897ba5d3e33908917f68ff4abcc - https://git.kernel.org/stable/c/98bc7e26e14fbb26a6abf97603d59532475e97f8
CVE ID: CVE-2024-35941 State: REJECTED Published: 2024-05-19T10:10:46.233Z Last Updated: 2024-06-04T12:55:24.200Z Description: No description available.
CVE ID: CVE-2024-35942 State: PUBLISHED Published: 2024-05-19T10:10:46.876Z Last Updated: 2025-05-04T09:08:54.018Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pmdomain: imx8mp-blk-ctrl: imx8mp_blk: Add fdcc clock to hdmimix domain According to i.MX8MP RM and HDMI ADD, the fdcc clock is part of hdmi rx verification IP that should not enable for HDMI TX. But actually if the clock is disabled before HDMI/LCDIF probe, LCDIF will not get pixel clock from HDMI PHY and print the error logs: [CRTC:39:crtc-2] vblank wait timed out WARNING: CPU: 2 PID: 9 at drivers/gpu/drm/drm_atomic_helper.c:1634 drm_atomic_helper_wait_for_vblanks.pa
wait timed out WARNING: CPU: 2 PID: 9 at drivers/gpu/drm/drm_atomic_helper.c:1634 drm_atomic_helper_wait_for_vblanks.part.0+0x23c/0x260 Add fdcc clock to LCDIF and HDMI TX power domains to fix the issue. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9d3f959b426635c4da50dfc7b1306afd84d23e7c - https://git.kernel.org/stable/c/b13c0d871cd878ff53d25507ca535f59ed1f6a2a - https://git.kernel.org/stable/c/697624ee8ad557ab5417f985d2c804241a7ad30d
CVE ID: CVE-2024-35943 State: PUBLISHED Published: 2024-05-19T10:10:47.529Z Last Updated: 2025-11-03T21:55:04.223Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pmdomain: ti: Add a null pointer check to the omap_prm_domain_init devm_kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the pointer validity. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e65f7eb117e1b44742212d65784236269085e736 - https://git.kernel.org/stable/c/984212fa6b4bc6d9ed58f5b0838e8d5af7679ce
ble/c/e65f7eb117e1b44742212d65784236269085e736 - https://git.kernel.org/stable/c/984212fa6b4bc6d9ed58f5b0838e8d5af7679ce5 - https://git.kernel.org/stable/c/bc08f5ab11b1881b85371f0bd9c9a3d27f65cca8 - https://git.kernel.org/stable/c/ce666cecc09c0f92d5f86d89d8068ecfcf723a7e - https://git.kernel.org/stable/c/04f23510daa40f9010fadf309507564a34ad956f - https://git.kernel.org/stable/c/5d7f58ee08434a33340f75ac7ac5071eea9673b3
CVE ID: CVE-2024-35944 State: PUBLISHED Published: 2024-05-19T10:10:48.183Z Last Updated: 2025-05-04T09:08:56.644Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() Syzkaller hit 'WARNING in dg_dispatch_as_host' bug. memcpy: detected field-spanning write (size 56) of single field "&dg_info->msg" at drivers/misc/vmw_vmci/vmci_datagram.c:237 (size 24) WARNING: CPU: 0 PID: 1555 at drivers/misc/vmw_vmci/vmci_datagram.c:237 dg_dispatch_as_host+0x88e/0xa60 drivers/misc/vmw_vmci/vmci_datagram.c:237 Some code commentry, based on my understanding: 544 #define VMCI_DG_SIZE(_dg) (V
ivers/misc/vmw_vmci/vmci_datagram.c:237 Some code commentry, based on my understanding: 544 #define VMCI_DG_SIZE(_dg) (VMCI_DG_HEADERSIZE + (size_t)(_dg)->payload_size) /// This is 24 + payload_size memcpy(&dg_info->msg, dg, dg_size); Destination = dg_info->msg ---> this is a 24 byte structure(struct vmci_datagram) Source = dg --> this is a 24 byte structure (struct vmci_datagram) Size = dg_size = 24 + payload_size {payload_size = 56-24 =32} -- Syzkaller managed to set payload_size to 32. 35 struct delayed_datagram_info { 36 struct datagram_entry *entry; 37 struct work_struct work; 38 bool in_dg_host_queue; 39 /* msg and msg_payload must be together. */ 40 struct vmci_datagram msg; 41 u8 msg
ct work; 38 bool in_dg_host_queue; 39 /* msg and msg_payload must be together. */ 40 struct vmci_datagram msg; 41 u8 msg_payload[]; 42 }; So those extra bytes of payload are copied into msg_payload[], a run time warning is seen while fuzzing with Syzkaller. One possible way to fix the warning is to split the memcpy() into two parts -- one -- direct assignment of msg and second taking care of payload. Gustavo quoted: "Under FORTIFY_SOURCE we should not copy data across multiple members in a structure." Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e87bb99d2df6512d8ee37a5d63d2ca9a39a8c051 - https://git.kernel.org/stabl
r: References: - https://git.kernel.org/stable/c/e87bb99d2df6512d8ee37a5d63d2ca9a39a8c051 - https://git.kernel.org/stable/c/f15eca95138b3d4ec17b63c3c1937b0aa0d3624b - https://git.kernel.org/stable/c/ad78c5047dc4076d0b3c4fad4f42ffe9c86e8100 - https://git.kernel.org/stable/c/130b0cd064874e0d0f58e18fb00e6f3993e90c74 - https://git.kernel.org/stable/c/feacd430b42bbfa9ab3ed9e4f38b86c43e348c75 - https://git.kernel.org/stable/c/dae70a57565686f16089737adb8ac64471570f73 - https://git.kernel.org/stable/c/491a1eb07c2bd8841d63cb5263455e185be5866f - https://git.kernel.org/stable/c/19b070fefd0d024af3daa7329cbc0d00de5302ec
CVE ID: CVE-2024-35945 State: PUBLISHED Published: 2024-05-19T10:10:48.839Z Last Updated: 2025-05-21T09:12:40.907Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: phy: phy_device: Prevent nullptr exceptions on ISR If phydev->irq is set unconditionally, check for valid interrupt handler or fall back to polling mode to prevent nullptr exceptions in interrupt service routine. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7a71f61ebf95cedd3f245db6da397822971d8db5 - https://git.kernel.org/stable/c/3419ee39e3d3162ab2ec9942bb537613ed5b6311 - https://git.ker
edd3f245db6da397822971d8db5 - https://git.kernel.org/stable/c/3419ee39e3d3162ab2ec9942bb537613ed5b6311 - https://git.kernel.org/stable/c/61c81872815f46006982bb80460c0c80a949b35b
CVE ID: CVE-2024-35946 State: PUBLISHED Published: 2024-05-19T10:10:49.493Z Last Updated: 2025-05-04T09:08:59.002Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix null pointer access when abort scan During cancel scan we might use vif that weren't scanning. Fix this by using the actual scanning vif. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/b34d64e9aa5505e3c84570aed5c757f1839573e8 - https://git.kernel.org/stable/c/4f11c741908dab7dd48fa5a986b210d4fc74ca8d - https://git.kernel.org/stable/c/7e11a2966f51695c0af0b1f976a32d64dee243b2
CVE ID: CVE-2024-35947 State: PUBLISHED Published: 2024-05-19T11:14:49.924Z Last Updated: 2025-05-04T09:09:00.219Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dyndbg: fix old BUG_ON in >control parser Fix a BUG_ON from 2009. Even if it looks "unreachable" (I didn't really look), lets make sure by removing it, doing pr_err and return -EINVAL instead. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3c718bddddca9cbef177ac475b94c5c91147fb38 - https://git.kernel.org/stable/c/343081c21e56bd6690d342e2f5ae8c00183bf081 - https://git.kernel.org/stable/c/41d8ac23
38 - https://git.kernel.org/stable/c/343081c21e56bd6690d342e2f5ae8c00183bf081 - https://git.kernel.org/stable/c/41d8ac238ab1cab01a8c71798d61903304f4e79b - https://git.kernel.org/stable/c/ba3c118cff7bcb0fe6aa84ae1f9080d50e31c561 - https://git.kernel.org/stable/c/a66c869b17c4c4dcf81d273b02cb0efe88e127ab - https://git.kernel.org/stable/c/a69e1bdd777ce51061111dc419801e8a2fd241cc - https://git.kernel.org/stable/c/529e1852785599160415e964ca322ee7add7aef0 - https://git.kernel.org/stable/c/00e7d3bea2ce7dac7bee1cf501fb071fd0ea8f6c
CVE ID: CVE-2024-35948 State: PUBLISHED Published: 2024-05-20T09:17:34.536Z Last Updated: 2025-05-04T09:09:01.327Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bcachefs: Check for journal entries overruning end of sb clean section Fix a missing bounds check in superblock validation. Note that we don't yet have repair code for this case - repair code for individual items is generally low priority, since the whole superblock is checksummed, validated prior to write, and we have backups. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/fcdbc1d7a4b638e5d5668
s: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/fcdbc1d7a4b638e5d5668de461f320386f3002aa