Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
370 [ 286.493579][ C0] ip_local_deliver_finish+0x297/0x420 [ 286.494268][ C0] ip_local_deliver+0x168/0x430 [ 286.494867][ C0] ? __pfx_ip_local_deliver+0x10/0x10 [ 286.495498][ C0] ? __pfx_ip_local_deliver_finish+0x10/0x10 [ 286.496204][ C0] ? ip_rcv_finish_core+0x19a/0x1f20 [ 286.496806][ C0] ? lock_release+0x217/0x2c0 [ 286.497414][ C0] ip_rcv+0x455/0x6e0 [ 286.497945][ C0] ? __pfx_ip_rcv+0x10/0x10 [ ---truncated--- Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/6265538446e2426f4bf3b57e91d7680b2047ddd9 - https://git.kernel.org/stable/c/17e58be5b49f58bf17799a504f55c2d05ab2ecdc - https://git.kernel.org/stable/c/fc01b547c3f8bfa6e1d23cd5a2c63c73
org/stable/c/17e58be5b49f58bf17799a504f55c2d05ab2ecdc - https://git.kernel.org/stable/c/fc01b547c3f8bfa6e1d23cd5a2c63c736e8c3e4e - https://git.kernel.org/stable/c/c240375587ddcc80e1022f52ee32b946bbc3a639 - https://git.kernel.org/stable/c/3a982ada411b8c52695f1784c3f4784771f30209 - https://git.kernel.org/stable/c/ec462449f4cf616b0aa2ed119f5f44b5fdfcefab - https://git.kernel.org/stable/c/a21cb31642ffc84ca4ce55028212a96f72f54d30 - https://git.kernel.org/stable/c/46d22b47df2741996af277a2838b95f130436c13
CVE ID: CVE-2025-38036 State: PUBLISHED Published: 2025-06-18T09:33:22.928Z Last Updated: 2025-06-19T13:10:58.362Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Perform early GT MMIO initialization to read GMDID VFs need to communicate with the GuC to obtain the GMDID value and existing GuC functions used for that assume that the GT has it's MMIO members already setup. However, due to recent refactoring the gt->mmio is initialized later, and any attempt by the VF to use xe_mmio_read|write() from GuC functions will lead to NPD crash due to unset MMIO register address: [] xe 0000:00:02.1: [drm] Running in SR-IOV VF mo
C functions will lead to NPD crash due to unset MMIO register address: [] xe 0000:00:02.1: [drm] Running in SR-IOV VF mode [] xe 0000:00:02.1: [drm] GT0: sending H2G MMIO 0x5507 [] BUG: unable to handle page fault for address: 0000000000190240 Since we are already tweaking the id and type of the primary GT to mimic it's a Media GT before initializing the GuC communication, we can also call xe_gt_mmio_init() to perform early setup of the gt->mmio which will make those GuC functions work again. References: - https://git.kernel.org/stable/c/ef6e950aea76a5009ccc79ebfa955ecc66cd85a2 - https://git.kernel.org/stable/c/13265fe7426ec9ba5aa86baab913417ca361e8a4
CVE ID: CVE-2025-38037 State: PUBLISHED Published: 2025-06-18T09:33:23.551Z Last Updated: 2025-11-03T17:33:16.449Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: vxlan: Annotate FDB data races The 'used' and 'updated' fields in the FDB entry structure can be accessed concurrently by multiple threads, leading to reports such as [1]. Can be reproduced using [2]. Suppress these reports by annotating these accesses using READ_ONCE() / WRITE_ONCE(). [1] BUG: KCSAN: data-race in vxlan_xmit / vxlan_xmit write to 0xffff942604d263a8 of 8 bytes by task 286 on cpu 0: vxlan_xmit+0xb29/0x2380 dev_hard_start_xmit+0x84/0x2f0 __dev_queue_xmit+
ff942604d263a8 of 8 bytes by task 286 on cpu 0: vxlan_xmit+0xb29/0x2380 dev_hard_start_xmit+0x84/0x2f0 __dev_queue_xmit+0x45a/0x1650 packet_xmit+0x100/0x150 packet_sendmsg+0x2114/0x2ac0 __sys_sendto+0x318/0x330 __x64_sys_sendto+0x76/0x90 x64_sys_call+0x14e8/0x1c00 do_syscall_64+0x9e/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f read to 0xffff942604d263a8 of 8 bytes by task 287 on cpu 2: vxlan_xmit+0xadf/0x2380 dev_hard_start_xmit+0x84/0x2f0 __dev_queue_xmit+0x45a/0x1650 packet_xmit+0x100/0x150 packet_sendmsg+0x2114/0x2ac0 __sys_sendto+0x318/0x330 __x64_sys_sendto+0x76/0x90 x64_sys_call+0x14e8/0x1c00 do_syscall_64+0x9e/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f value changed: 0x00000000f
x64_sys_call+0x14e8/0x1c00 do_syscall_64+0x9e/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f value changed: 0x00000000fffbac6e -> 0x00000000fffbac6f Reported by Kernel Concurrency Sanitizer on: CPU: 2 UID: 0 PID: 287 Comm: mausezahn Not tainted 6.13.0-rc7-01544-gb4b270f11a02 #5 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 [2] #!/bin/bash set +H echo whitelist > /sys/kernel/debug/kcsan echo !vxlan_xmit > /sys/kernel/debug/kcsan ip link add name vx0 up type vxlan id 10010 dstport 4789 local 192.0.2.1 bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 198.51.100.1 taskset -c 0 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q & taskset -c 2 mauseza
v vx0 self static dst 198.51.100.1 taskset -c 0 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q & taskset -c 2 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q & Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/02a33b1035a307453a1da6ce0a1bf3676be287d7 - https://git.kernel.org/stable/c/87d076987a9ba106c83412fcd113656f71af05a1 - https://git.kernel.org/stable/c/e033da39fc6abbddab6c29624acef80757f273fa - https://git.kernel.org/stable/c/784b78295a3a58bf052339dd669e6e03710220d3 - https://git.kernel.org/stable/c/13cba3f837903f7184d6e9b6137d5165ffe82a8f - https://git.kernel.org/stable/c/a6644aeb8ddf196dec5f8e782293c36f065df4d7 - https://git.kernel.o
d6e9b6137d5165ffe82a8f - https://git.kernel.org/stable/c/a6644aeb8ddf196dec5f8e782293c36f065df4d7 - https://git.kernel.org/stable/c/4eceb7eae6ea7c950384c34e6dbbe872c981935f - https://git.kernel.org/stable/c/f6205f8215f12a96518ac9469ff76294ae7bd612
CVE ID: CVE-2025-38038 State: PUBLISHED Published: 2025-06-18T09:33:24.178Z Last Updated: 2025-06-19T13:10:59.768Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost set_boost is a per-policy function call, hence a driver wide lock is unnecessary. Also this mutex_acquire can collide with the mutex_acquire from the mode-switch path in status_store(), which can lead to a deadlock. So, remove it. References: - https://git.kernel.org/stable/c/61e931ee145eeab8196e585ff4334870b130b744 - https://git.kernel.org/stable/c/cd347d071713234586762d79c5a691785e9be418 - https://git.k
eeab8196e585ff4334870b130b744 - https://git.kernel.org/stable/c/cd347d071713234586762d79c5a691785e9be418 - https://git.kernel.org/stable/c/db1cafc77aaaf871509da06f4a864e9af6d6791f
CVE ID: CVE-2025-38039 State: PUBLISHED Published: 2025-06-18T09:33:25.111Z Last Updated: 2025-06-18T09:33:25.111Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid WARN_ON when configuring MQPRIO with HTB offload enabled When attempting to enable MQPRIO while HTB offload is already configured, the driver currently returns `-EINVAL` and triggers a `WARN_ON`, leading to an unnecessary call trace. Update the code to handle this case more gracefully by returning `-EOPNOTSUPP` instead, while also providing a helpful user message. References: - https://git.kernel.org/stable/c/090c0ba179eaf7b670e720aa054533756a43d565 -
viding a helpful user message. References: - https://git.kernel.org/stable/c/090c0ba179eaf7b670e720aa054533756a43d565 - https://git.kernel.org/stable/c/b82e496531c571caf8a2ef247f51c160bab2162e - https://git.kernel.org/stable/c/9e2bac6835f73895598df5a3a125a19497fad46b - https://git.kernel.org/stable/c/689805dcc474c2accb5cffbbcea1c06ee4a54570
CVE ID: CVE-2025-38040 State: PUBLISHED Published: 2025-06-18T09:33:25.720Z Last Updated: 2025-11-03T17:33:17.475Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: serial: mctrl_gpio: split disable_ms into sync and no_sync APIs The following splat has been observed on a SAMA5D27 platform using atmel_serial: BUG: sleeping function called from invalid context at kernel/irq/manage.c:738 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 27, name: kworker/u5:0 preempt_count: 1, expected: 0 INFO: lockdep is turned off. irq event stamp: 0 hardirqs last enabled at (0): [<00000000>] 0x0 hardirqs last disabled at (0): [<c01588f0>] c
ned off. irq event stamp: 0 hardirqs last enabled at (0): [<00000000>] 0x0 hardirqs last disabled at (0): [<c01588f0>] copy_process+0x1c4c/0x7bec softirqs last enabled at (0): [<c0158944>] copy_process+0x1ca0/0x7bec softirqs last disabled at (0): [<00000000>] 0x0 CPU: 0 UID: 0 PID: 27 Comm: kworker/u5:0 Not tainted 6.13.0-rc7+ #74 Hardware name: Atmel SAMA5 Workqueue: hci0 hci_power_on [bluetooth] Call trace: unwind_backtrace from show_stack+0x18/0x1c show_stack from dump_stack_lvl+0x44/0x70 dump_stack_lvl from __might_resched+0x38c/0x598 __might_resched from disable_irq+0x1c/0x48 disable_irq from mctrl_gpio_disable_ms+0x74/0xc0 mctrl_gpio_disable_ms from atmel_disable_ms.part.0+0x80/0x1f4 a
1c/0x48 disable_irq from mctrl_gpio_disable_ms+0x74/0xc0 mctrl_gpio_disable_ms from atmel_disable_ms.part.0+0x80/0x1f4 atmel_disable_ms.part.0 from atmel_set_termios+0x764/0x11e8 atmel_set_termios from uart_change_line_settings+0x15c/0x994 uart_change_line_settings from uart_set_termios+0x2b0/0x668 uart_set_termios from tty_set_termios+0x600/0x8ec tty_set_termios from ttyport_set_flow_control+0x188/0x1e0 ttyport_set_flow_control from wilc_setup+0xd0/0x524 [hci_wilc] wilc_setup [hci_wilc] from hci_dev_open_sync+0x330/0x203c [bluetooth] hci_dev_open_sync [bluetooth] from hci_dev_do_open+0x40/0xb0 [bluetooth] hci_dev_do_open [bluetooth] from hci_power_on+0x12c/0x664 [bluetooth] hci_power_on [bl
dev_do_open+0x40/0xb0 [bluetooth] hci_dev_do_open [bluetooth] from hci_power_on+0x12c/0x664 [bluetooth] hci_power_on [bluetooth] from process_one_work+0x998/0x1a38 process_one_work from worker_thread+0x6e0/0xfb4 worker_thread from kthread+0x3d4/0x484 kthread from ret_from_fork+0x14/0x28 This warning is emitted when trying to toggle, at the highest level, some flow control (with serdev_device_set_flow_control) in a device driver. At the lowest level, the atmel_serial driver is using serial_mctrl_gpio lib to enable/disable the corresponding IRQs accordingly. The warning emitted by CONFIG_DEBUG_ATOMIC_SLEEP is due to disable_irq (called in mctrl_gpio_disable_ms) being possibly called in some at
ed by CONFIG_DEBUG_ATOMIC_SLEEP is due to disable_irq (called in mctrl_gpio_disable_ms) being possibly called in some atomic context (some tty drivers perform modem lines configuration in regions protected by port lock). Split mctrl_gpio_disable_ms into two differents APIs, a non-blocking one and a blocking one. Replace mctrl_gpio_disable_ms calls with the relevant version depending on whether the call is protected by some port lock. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/68435c1fa3db696db4f480385db9e50e26691d0d - https://git.kernel.org/stable/c/c504c11b94d6e4ad818ca5578dffa8ff29ad0f20 - https://git.kernel.org/stable/c/e6a46719a2369eb
tps://git.kernel.org/stable/c/c504c11b94d6e4ad818ca5578dffa8ff29ad0f20 - https://git.kernel.org/stable/c/e6a46719a2369eb5186d4f7e6c0478720ca1ec3d - https://git.kernel.org/stable/c/7187ec6b0b9ff22ebac2c3bb4178b7dbbdc0a55a - https://git.kernel.org/stable/c/1bd2aad57da95f7f2d2bb52f7ad15c0f4993a685
CVE ID: CVE-2025-38041 State: PUBLISHED Published: 2025-06-18T09:33:26.543Z Last Updated: 2025-06-18T09:33:26.543Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h616: Reparent GPU clock during frequency changes The H616 manual does not state that the GPU PLL supports dynamic frequency configuration, so we must take extra care when changing the frequency. Currently any attempt to do device DVFS on the GPU lead to panfrost various ooops, and GPU hangs. The manual describes the algorithm for changing the PLL frequency, which the CPU PLL notifier code already support, so we reuse that to reparent the GPU clock to GP
ing the PLL frequency, which the CPU PLL notifier code already support, so we reuse that to reparent the GPU clock to GPU1 clock during frequency changes. References: - https://git.kernel.org/stable/c/1439673b78185eaaa5fae444b3a9d58c434ee78e - https://git.kernel.org/stable/c/eb963d7948ce6571939c6875424b557b25f16610
CVE ID: CVE-2025-38042 State: PUBLISHED Published: 2025-06-18T09:33:27.214Z Last Updated: 2025-06-19T13:11:01.212Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: k3-udma-glue: Drop skip_fdq argument from k3_udma_glue_reset_rx_chn The user of k3_udma_glue_reset_rx_chn() e.g. ti_am65_cpsw_nuss can run on multiple platforms having different DMA architectures. On some platforms there can be one FDQ for all flows in the RX channel while for others there is a separate FDQ for each flow in the RX channel. So far we have been relying on the skip_fdq argument of k3_udma_glue_reset_rx_chn(). Instead of relying on the user
el. So far we have been relying on the skip_fdq argument of k3_udma_glue_reset_rx_chn(). Instead of relying on the user to provide this information, infer it based on DMA architecture during k3_udma_glue_request_rx_chn() and save it in an internal flag 'single_fdq'. Use that flag at k3_udma_glue_reset_rx_chn() to deicide if the FDQ needs to be cleared for every flow or just for flow 0. Fixes the below issue on ti_am65_cpsw_nuss driver on AM62-SK. > ip link set eth1 down > ip link set eth0 down > ethtool -L eth0 rx 8 > ip link set eth0 up > modprobe -r ti_am65_cpsw_nuss [ 103.045726] ------------[ cut here ]------------ [ 103.050505] k3_knav_desc_pool size 512000 != avail 64000 [ 103.050703]
3.045726] ------------[ cut here ]------------ [ 103.050505] k3_knav_desc_pool size 512000 != avail 64000 [ 103.050703] WARNING: CPU: 1 PID: 450 at drivers/net/ethernet/ti/k3-cppi-desc-pool.c:33 k3_cppi_desc_pool_destroy+0xa0/0xa8 [k3_cppi_desc_pool] [ 103.068810] Modules linked in: ti_am65_cpsw_nuss(-) k3_cppi_desc_pool snd_soc_hdmi_codec crct10dif_ce snd_soc_simple_card snd_soc_simple_card_utils display_connector rtc_ti_k3 k3_j72xx_bandgap tidss drm_client_lib snd_soc_davinci_mcas p drm_dma_helper tps6598x phylink snd_soc_ti_udma rti_wdt drm_display_helper snd_soc_tlv320aic3x_i2c typec at24 phy_gmii_sel snd_soc_ti_edma snd_soc_tlv320aic3x sii902x snd_soc_ti_sdma sa2ul omap_mailbox drm_kms_
ic3x_i2c typec at24 phy_gmii_sel snd_soc_ti_edma snd_soc_tlv320aic3x sii902x snd_soc_ti_sdma sa2ul omap_mailbox drm_kms_helper authenc cfg80211 r fkill fuse drm drm_panel_orientation_quirks backlight ip_tables x_tables ipv6 [last unloaded: k3_cppi_desc_pool] [ 103.119950] CPU: 1 UID: 0 PID: 450 Comm: modprobe Not tainted 6.13.0-rc7-00001-g9c5e3435fa66 #1011 [ 103.119968] Hardware name: Texas Instruments AM625 SK (DT) [ 103.119974] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 103.119983] pc : k3_cppi_desc_pool_destroy+0xa0/0xa8 [k3_cppi_desc_pool] [ 103.148007] lr : k3_cppi_desc_pool_destroy+0xa0/0xa8 [k3_cppi_desc_pool] [ 103.154709] sp : ffff8000826ebbc0 [ 103.158015] x
148007] lr : k3_cppi_desc_pool_destroy+0xa0/0xa8 [k3_cppi_desc_pool] [ 103.154709] sp : ffff8000826ebbc0 [ 103.158015] x29: ffff8000826ebbc0 x28: ffff0000090b6300 x27: 0000000000000000 [ 103.165145] x26: 0000000000000000 x25: 0000000000000000 x24: ffff0000019df6b0 [ 103.172271] x23: ffff0000019df6b8 x22: ffff0000019df410 x21: ffff8000826ebc88 [ 103.179397] x20: 000000000007d000 x19: ffff00000a3b3000 x18: 0000000000000000 [ 103.186522] x17: 0000000000000000 x16: 0000000000000000 x15: 000001e8c35e1cde [ 103.193647] x14: 0000000000000396 x13: 000000000000035c x12: 0000000000000000 [ 103.200772] x11: 000000000000003a x10: 00000000000009c0 x9 : ffff8000826eba20 [ 103.207897] x8 : ffff0000090b6d20
0000 [ 103.200772] x11: 000000000000003a x10: 00000000000009c0 x9 : ffff8000826eba20 [ 103.207897] x8 : ffff0000090b6d20 x7 : ffff00007728c180 x6 : ffff00007728c100 [ 103.215022] x5 : 0000000000000001 x4 : ffff000000508a50 x3 : ffff7ffff6146000 [ 103.222147] x2 : 0000000000000000 x1 : e300b4173ee6b200 x0 : 0000000000000000 [ 103.229274] Call trace: [ 103.231714] k3_cppi_desc_pool_destroy+0xa0/0xa8 [k3_cppi_desc_pool] (P) [ 103.238408] am65_cpsw_nuss_free_rx_chns+0x28/0x4c [ti_am65_cpsw_nuss] [ 103.244942] devm_action_release+0x14/0x20 [ 103.249040] release_nodes+0x3c/0x68 [ 103.252610] devres_release_all+0x8c/0xdc [ 103.256614] device_unbind_cleanup+0x18/0x60 [ 103.260876] device_release_dri
103.252610] devres_release_all+0x8c/0xdc [ 103.256614] device_unbind_cleanup+0x18/0x60 [ 103.260876] device_release_driver_internal+0xf8/0x178 [ 103.266004] driver_detach+0x50/0x9c [ 103.269571] bus_remove_driver+0x6c/0xbc [ 103.273485] driver_unregister+0x30/0x60 [ 103.277401] platform_driver_unregister+0x14/0x20 [ 103.282096] am65_cpsw_nuss_driver_exit+0x18/0xff4 [ti_am65_cpsw_nuss] [ 103.288620] __arm64_sys_delete_module+0x17c/0x25c [ 103.293404] invoke_syscall+0x44/0x100 [ 103.297149] el0_svc_common.constprop.0+0xc0/0xe0 [ 103.301845] do_el0_svc+0x1c/0x28 [ 103.305155] el0_svc+0x28/0x98 ---truncated--- References: - https://git.kernel.org/stable/c/d0dd9d133ef8fdc894e0be9aa27dc49ef5f813c
el0_svc+0x28/0x98 ---truncated--- References: - https://git.kernel.org/stable/c/d0dd9d133ef8fdc894e0be9aa27dc49ef5f813cb - https://git.kernel.org/stable/c/0da30874729baeb01889b0eca16cfda122687503
CVE ID: CVE-2025-38043 State: PUBLISHED Published: 2025-06-18T09:33:27.994Z Last Updated: 2025-11-03T17:33:18.425Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Set dma_mask for ffa devices Set dma_mask for FFA devices, otherwise DMA allocation using the device pointer lead to following warning: WARNING: CPU: 1 PID: 1 at kernel/dma/mapping.c:597 dma_alloc_attrs+0xe0/0x124 Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/97bab02f0b64ba6bcdf6a8fae561db07f509aee9 - https://git.kernel.org/stable/c/c6aa1d6bd6ccff4ecdf064d288817657ec8532f0 - https://git.kernel.org/st
ae561db07f509aee9 - https://git.kernel.org/stable/c/c6aa1d6bd6ccff4ecdf064d288817657ec8532f0 - https://git.kernel.org/stable/c/e2de76c34a8a925efe80fccae4810427bc144ed0 - https://git.kernel.org/stable/c/3a3efeef64364c2a028cf0d03d68c831813a97fd - https://git.kernel.org/stable/c/2e62c803feec1ef5847d8fa47dd0de039abfa378 - https://git.kernel.org/stable/c/cc0aac7ca17e0ea3ca84b552fc79f3e86fd07f53
CVE ID: CVE-2025-38044 State: PUBLISHED Published: 2025-06-18T09:33:28.669Z Last Updated: 2025-11-03T17:33:20.343Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: cx231xx: set device_caps for 417 The video_device for the MPEG encoder did not set device_caps. Add this, otherwise the video device can't be registered (you get a WARN_ON instead). Not seen before since currently 417 support is disabled, but I found this while experimenting with it. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/2ad41beb7df3bd63b209842d16765ec59dafe6e4 - https://git.kernel.org/stable/c/0884dd3ab
: - https://git.kernel.org/stable/c/2ad41beb7df3bd63b209842d16765ec59dafe6e4 - https://git.kernel.org/stable/c/0884dd3abbe80307a2d4cbdbe5e312be164f8adb - https://git.kernel.org/stable/c/c91447e35b9bea60bda4408c48e7891d14351021 - https://git.kernel.org/stable/c/9d1a5be86dbe074bd8dd6bdd63a99d6bb66d5930 - https://git.kernel.org/stable/c/5c9eca180a4235abd56cc7f7308ca72128d93dce - https://git.kernel.org/stable/c/4731d5328f507ae8fd8a57abbca9119ec7a8d665 - https://git.kernel.org/stable/c/e43fd82bb2110bf9d13d800cdc49cceddfd0ede5 - https://git.kernel.org/stable/c/a79efc44b51432490538a55b9753a721f7d3ea42
CVE ID: CVE-2025-38045 State: PUBLISHED Published: 2025-06-18T09:33:29.289Z Last Updated: 2025-06-18T09:33:29.289Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: fix debug actions order The order of actions taken for debug was implemented incorrectly. Now we implemented the dump split and do the FW reset only in the middle of the dump (rather than the FW killing itself on error.) As a result, some of the actions taken when applying the config will now crash the device, so we need to fix the order. References: - https://git.kernel.org/stable/c/2b790fe67ed483d86c1aeb8be6735bf792caa7e5 - https://git.kernel.org/stabl
r. References: - https://git.kernel.org/stable/c/2b790fe67ed483d86c1aeb8be6735bf792caa7e5 - https://git.kernel.org/stable/c/181e8b56b74ad3920456dcdc8a361520d9007956 - https://git.kernel.org/stable/c/328fbc96ecbee16c5fcbfcb3ac57b476f94da2f0 - https://git.kernel.org/stable/c/eb29b4ffafb20281624dcd2cbb768d6f30edf600
CVE ID: CVE-2025-38046 State: REJECTED Published: 2025-06-18T09:33:29.932Z Last Updated: 2025-06-18T11:20:31.938Z Description: No description available.
CVE ID: CVE-2025-38047 State: PUBLISHED Published: 2025-06-18T09:33:30.742Z Last Updated: 2025-07-15T15:43:55.220Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: x86/fred: Fix system hang during S4 resume with FRED enabled Upon a wakeup from S4, the restore kernel starts and initializes the FRED MSRs as needed from its perspective. It then loads a hibernation image, including the image kernel, and attempts to load image pages directly into their original page frames used before hibernation unless those frames are currently in use. Once all pages are moved to their original locations, it jumps to a "trampoline" page in the image
are currently in use. Once all pages are moved to their original locations, it jumps to a "trampoline" page in the image kernel. At this point, the image kernel takes control, but the FRED MSRs still contain values set by the restore kernel, which may differ from those set by the image kernel before hibernation. Therefore, the image kernel must ensure the FRED MSRs have the same values as before hibernation. Since these values depend only on the location of the kernel text and data, they can be recomputed from scratch. References: - https://git.kernel.org/stable/c/c42f740a07eea4807e98d2d8febc549c957a7b49 - https://git.kernel.org/stable/c/e7090fe75a2826363c71ad1fb4e95e58141478df - https://git
7eea4807e98d2d8febc549c957a7b49 - https://git.kernel.org/stable/c/e7090fe75a2826363c71ad1fb4e95e58141478df - https://git.kernel.org/stable/c/e5f1e8af9c9e151ecd665f6d2e36fb25fec3b110
CVE ID: CVE-2025-38048 State: PUBLISHED Published: 2025-06-18T09:33:31.413Z Last Updated: 2025-11-03T17:33:21.278Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN syzbot reports a data-race when accessing the event_triggered, here is the simplified stack when the issue occurred: ================================================================== BUG: KCSAN: data-race in virtqueue_disable_cb / virtqueue_enable_cb_delayed write to 0xffff8881025bc452 of 1 bytes by task 3288 on cpu 0: virtqueue_enable_cb_delayed+0x42/0x3c0 drivers/virtio/virtio_ring.c:2653 start_
5bc452 of 1 bytes by task 3288 on cpu 0: virtqueue_enable_cb_delayed+0x42/0x3c0 drivers/virtio/virtio_ring.c:2653 start_xmit+0x230/0x1310 drivers/net/virtio_net.c:3264 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3800 [inline] read to 0xffff8881025bc452 of 1 bytes by interrupt on cpu 1: virtqueue_disable_cb_split drivers/virtio/virtio_ring.c:880 [inline] virtqueue_disable_cb+0x92/0x180 drivers/virtio/virtio_ring.c:2566 skb_xmit_done+0x5f/0x140 drivers/net/virtio_net.c:777 vring_interrupt+0x161/0x190 drivers/virtio/virtio_ring.c:2715 __handle_irq_event_percpu+0x95/0x490 kernel/irq/handle.c:158 han