CVE-2025-21801

In the Linux kernel, the following vulnerability has been resolved: net: ravb: Fix missing rtnl lock in suspend/resume path Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations. Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

net: dsa: Avoid cross-chip syncing of VLAN filtering

Changes to VLAN filtering are not applicable to cross-chip notifications.

On a system like this:

.-----. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-' '-1-2-' '-1-2-'

Before this change, upon sw1p1 leaving a bridge, a call to dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.

In this scenario:

.---------. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-3-4-' '-1-2-' '-1-2-'

When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be called for sw2 and sw3 with a non-existing port - leading to array out-of-bounds accesses and crashes on mv88e6xxx.(CVE-2022-49234)

In the Linux kernel, the following vulnerability has been resolved:

scsi: target: iscsi: Fix a race condition between login_work and the login thread

In case a malicious initiator sends some random data immediately after a login PDU; the iscsi_target_sk_data_ready() callback will schedule the login_work and, at the same time, the negotiation may end without clearing the LOGIN_FLAGS_INITIAL_PDU flag (because no additional PDU exchanges are required to complete the login).

The login has been completed but the login_work function will find the LOGIN_FLAGS_INITIAL_PDU flag set and will never stop from rescheduling itself; at this point, if the initiator drops the connection, the iscsit_conn structure will be freed, login_work will dereference a released socket structure and the kernel crashes.

BUG: kernel NULL pointer dereference, address: 0000000000000230 PF: supervisor write access in kernel mode PF: error_code(0x0002) - not-present page Workqueue: events iscsi_target_do_login_rx [iscsi_target_mod] RIP: 0010:_raw_read_lock_bh+0x15/0x30 Call trace: iscsi_target_do_login_rx+0x75/0x3f0 [iscsi_target_mod] process_one_work+0x1e8/0x3c0

Fix this bug by forcing login_work to stop after the login has been completed and the socket callbacks have been restored.

Add a comment to clearify the return values of iscsi_target_do_login()(CVE-2022-50350)

In the Linux kernel, the following vulnerability has been resolved:

fbdev: fbcon: release buffer when fbcon_do_set_font() failed

syzbot is reporting memory leak at fbcon_do_set_font() [1], for commit a5a923038d70 ("fbdev: fbcon: Properly revert changes when vc_resize() failed") missed that the buffer might be newly allocated by fbcon_set_font().(CVE-2022-50404)

In the Linux kernel, the following vulnerability has been resolved:

udf: Fix uninitialized array access for some pathnames

For filenames that begin with . and are between 2 and 5 characters long, UDF charset conversion code would read uninitialized memory in the output buffer. The only practical impact is that the name may be prepended a "unification hash" when it is not actually needed but still it is good to fix this.(CVE-2023-53165)

In the Linux kernel, the following vulnerability has been resolved:

nfsd: call op_release, even when op_func returns an error

For ops with "trivial" replies, nfsd4_encode_operation will shortcut most of the encoding work and skip to just marshalling up the status. One of the things it skips is calling op_release. This could cause a memory leak in the layoutget codepath if there is an error at an inopportune time.

Have the compound processing engine always call op_release, even when op_func sets an error in op->status. With this change, we also need nfsd4_block_get_device_info_scsi to set the gd_device pointer to NULL on error to avoid a double free.(CVE-2023-53241)

In the Linux kernel, the following vulnerability has been resolved:

VMCI: check context->notify_page after call to get_user_pages_fast() to avoid GPF

The call to get_user_pages_fast() in vmci_host_setup_notify() can return NULL…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

net: dsa: Avoid cross-chip syncing of VLAN filtering

Changes to VLAN filtering are not applicable to cross-chip notifications.

On a system like this:

.-----. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-' '-1-2-' '-1-2-'

Before this change, upon sw1p1 leaving a bridge, a call to dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.

In this scenario:

.---------. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-3-4-' '-1-2-' '-1-2-'

When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be called for sw2 and sw3 with a non-existing port - leading to array out-of-bounds accesses and crashes on mv88e6xxx.(CVE-2022-49234)

In the Linux kernel, the following vulnerability has been resolved:

scsi: target: iscsi: Fix a race condition between login_work and the login thread

In case a malicious initiator sends some random data immediately after a login PDU; the iscsi_target_sk_data_ready() callback will schedule the login_work and, at the same time, the negotiation may end without clearing the LOGIN_FLAGS_INITIAL_PDU flag (because no additional PDU exchanges are required to complete the login).

The login has been completed but the login_work function will find the LOGIN_FLAGS_INITIAL_PDU flag set and will never stop from rescheduling itself; at this point, if the initiator drops the connection, the iscsit_conn structure will be freed, login_work will dereference a released socket structure and the kernel crashes.

BUG: kernel NULL pointer dereference, address: 0000000000000230 PF: supervisor write access in kernel mode PF: error_code(0x0002) - not-present page Workqueue: events iscsi_target_do_login_rx [iscsi_target_mod] RIP: 0010:_raw_read_lock_bh+0x15/0x30 Call trace: iscsi_target_do_login_rx+0x75/0x3f0 [iscsi_target_mod] process_one_work+0x1e8/0x3c0

Fix this bug by forcing login_work to stop after the login has been completed and the socket callbacks have been restored.

Add a comment to clearify the return values of iscsi_target_do_login()(CVE-2022-50350)

In the Linux kernel, the following vulnerability has been resolved:

fbdev: fbcon: release buffer when fbcon_do_set_font() failed

syzbot is reporting memory leak at fbcon_do_set_font() [1], for commit a5a923038d70 ("fbdev: fbcon: Properly revert changes when vc_resize() failed") missed that the buffer might be newly allocated by fbcon_set_font().(CVE-2022-50404)

In the Linux kernel, the following vulnerability has been resolved:

nfsd: call op_release, even when op_func returns an error

For ops with "trivial" replies, nfsd4_encode_operation will shortcut most of the encoding work and skip to just marshalling up the status. One of the things it skips is calling op_release. This could cause a memory leak in the layoutget codepath if there is an error at an inopportune time.

Have the compound processing engine always call op_release, even when op_func sets an error in op->status. With this change, we also need nfsd4_block_get_device_info_scsi to set the gd_device pointer to NULL on error to avoid a double free.(CVE-2023-53241)

In the Linux kernel, the following vulnerability has been resolved:

VMCI: check context->notify_page after call to get_user_pages_fast() to avoid GPF

The call to get_user_pages_fast() in vmci_host_setup_notify() can return NULL context->notify_page causing a GPF. To avoid GPF check if context->notify_page == NULL and return error if so.

general protection fault, probably for non-canonical address 0xe0009d1000000060: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0x0005088000000300- 0x0005088000000307] CPU: 2 PID: 26180 Comm: repro_34802241 Not tainted 6.1.0-rc4 #1 Hardware name: Red Hat KVM, BIOS 1.15.0-2.module+el8.6.0 04/01/2014…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

net: ravb: Fix missing rtnl lock in suspend/resume path

Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations.

Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down(CVE-2025-21801)

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: btrtl: Prevent potential NULL dereference

The btrtl_initialize() function checks that rtl_load_file() either had an error or it loaded a zero length file. However, if it loaded a zero length file then the error code is not set correctly. It results in an error pointer vs NULL bug, followed by a NULL pointer dereference. This was detected by Smatch:

drivers/bluetooth/btrtl.c:592 btrtl_initialize() warn: passing zero to 'ERR_PTR'(CVE-2025-37792)

In the Linux kernel, the following vulnerability has been resolved:

net_sched: ets: Fix double list add in class with netem as child qdisc

As described in Gerrard's report [1], there are use cases where a netem child qdisc will make the parent qdisc's enqueue callback reentrant. In the case of ets, there won't be a UAF, but the code will add the same classifier to the list twice, which will cause memory corruption.

In addition to checking for qlen being zero, this patch checks whether the class was already added to the active_list (cl_is_active) before doing the addition to cater for the reentrant case.

[1] https://lore.kernel.org/netdev/CAHcdcOm+03OD2j6R0=YHKqmy=VgJ8xEOKuP6c7mSgnp-TEJJbw@mail.gmail.com/(CVE-2025-37914)

In the Linux kernel, the following vulnerability has been resolved:

btrfs: adjust subpage bit start based on sectorsize

When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes.

When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do

bit_start++;

to move onto the next bit. The…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

net: ravb: Fix missing rtnl lock in suspend/resume path

Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations.

Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down(CVE-2025-21801)

In the Linux kernel, the following vulnerability has been resolved:

usb: renesas_usbhs: Flush the notify_hotplug_work

When performing continuous unbind/bind operations on the USB drivers available on the Renesas RZ/G2L SoC, a kernel crash with the message "Unable to handle kernel NULL pointer dereference at virtual address" may occur. This issue points to the usbhsc_notify_hotplug() function.

Flush the delayed work to avoid its execution when driver resources are unavailable.(CVE-2025-21917)

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: btrtl: Prevent potential NULL dereference

The btrtl_initialize() function checks that rtl_load_file() either had an error or it loaded a zero length file. However, if it loaded a zero length file then the error code is not set correctly. It results in an error pointer vs NULL bug, followed by a NULL pointer dereference. This was detected by Smatch:

drivers/bluetooth/btrtl.c:592 btrtl_initialize() warn: passing zero to 'ERR_PTR'(CVE-2025-37792)

In the Linux kernel, the following vulnerability has been resolved:

net_sched: ets: Fix double list add in class with netem as child qdisc

As described in Gerrard's report [1], there are use cases where a netem child qdisc will make the parent qdisc's enqueue callback reentrant. In the case of ets, there won't be a UAF, but the code will add the same classifier to the list twice, which will cause memory corruption.

In addition to checking for qlen being zero, this patch checks whether the class was already added to the active_list (cl_is_active) before doing the addition to cater for the reentrant case.

[1] https://lore.kernel.org/netdev/CAHcdcOm+03OD2j6R0=YHKqmy=VgJ8xEOKuP6c7mSgnp-TEJJbw@mail.gmail.com/(CVE-2025-37914)

In the…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

net: ravb: Fix missing rtnl lock in suspend/resume path

Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations.

Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down(CVE-2025-21801)

In the Linux kernel, the following vulnerability has been resolved:

usb: renesas_usbhs: Flush the notify_hotplug_work

When performing continuous unbind/bind operations on the USB drivers available on the Renesas RZ/G2L SoC, a kernel crash with the message "Unable to handle kernel NULL pointer dereference at virtual address" may occur. This issue points to the usbhsc_notify_hotplug() function.

Flush the delayed work to avoid its execution when driver resources are unavailable.(CVE-2025-21917)

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: btrtl: Prevent potential NULL dereference

The btrtl_initialize() function checks that rtl_load_file() either had an error or it loaded a zero length file. However, if it loaded a zero length file then the error code is not set correctly. It results in an error pointer vs NULL bug, followed by a NULL pointer dereference. This was detected by Smatch:

drivers/bluetooth/btrtl.c:592 btrtl_initialize() warn: passing zero to 'ERR_PTR'(CVE-2025-37792)

In the Linux kernel, the following vulnerability has been resolved:

net_sched: ets: Fix double list add in class with netem as child qdisc

As described in Gerrard's report [1], there are use cases where a netem child qdisc will make the parent qdisc's enqueue callback reentrant. In the case of ets, there won't be a UAF, but the code will add the same classifier to the list twice, which will cause memory corruption.

In addition to checking for qlen being zero, this patch checks whether the class was already added to the active_list (cl_is_active) before doing the addition to cater for the reentrant case.

[1] https://lore.kernel.org/netdev/CAHcdcOm+03OD2j6R0=YHKqmy=VgJ8xEOKuP6c7mSgnp-TEJJbw@mail.gmail.com/(CVE-2025-37914)

In the…

Root has patched CVE-2025-21801 in the linux package for Root:Debian:11. Multiple fixed versions available.

Root has patched CVE-2025-21801 in the linux package for Root:Debian:12. Multiple fixed versions available.

Root has patched CVE-2025-21801 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.

Root has patched CVE-2025-21801 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.

In the Linux kernel, the following vulnerability has been resolved: net: ravb: Fix missing rtnl lock in suspend/resume path Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations. Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down

In the Linux kernel, the following vulnerability has been resolved:

net: ravb: Fix missing rtnl lock in suspend/resume path

Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations.

Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down

In the Linux kernel, the following vulnerability has been resolved:

net: ravb: Fix missing rtnl lock in suspend/resume path

Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations.

Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• PowerPC architecture;
• x86 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Bluetooth drivers;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• FireWire subsystem;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device (Mouse) drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• SPI subsystem;
• Media staging drivers;
• Trusted Execution Environment drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB core drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• Framebuffer layer;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• UBI file system;
• BPF subsystem;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• L3 Master device support module;
• TCP network protocol;
• XFRM subsystem;
• Tracing infrastructure;
• io_uring subsystem;
• Process Accounting mechanism;
• Perf events;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Scheduler infrastructure;
• Workqueue subsystem;
• Memory management;
• B.A.T.M.A.N. meshing protocol;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Wireless networking;
• Key management;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers;
• SOF drivers; (CVE-2025-21737, CVE-2025-21711, CVE-2025-21987, CVE-2025-21848, CVE-2024-49570, CVE-2025-21762, CVE-2025-21738, CVE-2025-21712, CVE-2025-21719, CVE-2025-21870, CVE-2024-57984, CVE-2025-21815, CVE-2025-21744, CVE-2024-58058, CVE-2024-58078, CVE-2024-57990, CVE-2024-54458, CVE-2025-21899, CVE-2025-21814, CVE-2025-21746, CVE-2024-54456, CVE-2025-21739, CVE-2024-58057, CVE-2025-21855, CVE-2025-21758, CVE-2024-58006, CVE-2024-58007, CVE-2025-21720, CVE-2024-58090, CVE-2025-21852, CVE-2024-57982, CVE-2024-58013, CVE-2024-58082, CVE-2025-21825, CVE-2024-58072, CVE-2024-57996, CVE-2025-21787, CVE-2025-21742, CVE-2025-21705, CVE-2025-21829, CVE-2024-58060, CVE-2025-21811, CVE-2025-21900, CVE-2025-21853, CVE-2025-21809, CVE-2025-21938, CVE-2025-21728, CVE-2025-21785, CVE-2025-21732, CVE-2025-21888, CVE-2025-21768, CVE-2025-21875, CVE-2025-21721, CVE-2025-21766, CVE-2025-21892, CVE-2024-57953, CVE-2025-21772, CVE-2025-21735, CVE-2024-58017, CVE-2024-58086, CVE-2024-58084, CVE-2025-21761, CVE-2024-58008, CVE-2024-57988, CVE-2025-21874, CVE-2024-58011, CVE-2025-21706, CVE-2024-57999, CVE-2025-21858, CVE-2024-58061, CVE-2025-21727, CVE-2025-21780, CVE-2024-58051, CVE-2025-21791, CVE-2025-21788, CVE-2025-21786, CVE-2024-58012, CVE-2024-58010, CVE-2024-58001, CVE-2025-21844, CVE-2025-21708, CVE-2024-57834, CVE-2025-21873,…

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• PowerPC architecture;
• x86 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Bluetooth drivers;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Hardware crypto device drivers;
• FireWire subsystem;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device (Mouse) drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• SPI subsystem;
• Media staging drivers;
• Trusted Execution Environment drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB core drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• Framebuffer layer;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• UBI file system;
• BPF subsystem;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• L3 Master device support module;
• TCP network protocol;
• XFRM subsystem;
• Tracing infrastructure;
• io_uring subsystem;
• Process Accounting mechanism;
• Perf events;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Scheduler infrastructure;
• Workqueue subsystem;
• Memory management;
• B.A.T.M.A.N. meshing protocol;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Wireless networking;
• Key management;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers;
• SOF drivers; (CVE-2025-21799, CVE-2025-21765, CVE-2024-57834, CVE-2025-21971, CVE-2025-21855, CVE-2024-58019, CVE-2025-21987, CVE-2025-21754, CVE-2025-21779, CVE-2024-57986, CVE-2025-21809, CVE-2025-21887, CVE-2025-21744, CVE-2024-58014, CVE-2025-21892, CVE-2025-21848, CVE-2024-58051, CVE-2024-58085, CVE-2025-21862, CVE-2024-57981, CVE-2024-57987, CVE-2024-58053, CVE-2024-58063, CVE-2024-58079, CVE-2025-21875, CVE-2025-21715, CVE-2024-58004, CVE-2025-21857, CVE-2025-21856, CVE-2025-21938, CVE-2024-58082, CVE-2025-21815, CVE-2025-21864, CVE-2024-52559, CVE-2024-58078, CVE-2024-57989, CVE-2024-58001, CVE-2025-21889, CVE-2025-21739, CVE-2024-58005, CVE-2025-21829, CVE-2024-58069, CVE-2025-21712, CVE-2025-21846, CVE-2025-21883, CVE-2025-21852, CVE-2025-21808, CVE-2025-21900, CVE-2025-21888, CVE-2025-21784, CVE-2025-21838, CVE-2024-58054, CVE-2025-21781, CVE-2025-21737, CVE-2024-58013, CVE-2025-21885, CVE-2025-21877, CVE-2024-58010, CVE-2025-21844, CVE-2024-58012, CVE-2024-58083, CVE-2025-21783, CVE-2025-21798, CVE-2024-57973, CVE-2024-57982, CVE-2025-21708, CVE-2024-58003, CVE-2025-21786, CVE-2025-21750, CVE-2025-21870, CVE-2025-21745, CVE-2024-58081, CVE-2024-57979, CVE-2025-21718, CVE-2025-21816, CVE-2025-21868, CVE-2025-21731, CVE-2025-21814, CVE-2025-21826, CVE-2024-58006, CVE-2025-21821, CVE-2024-57852, CVE-2025-21746,…

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2024-57980, CVE-2024-58061, CVE-2025-21742, CVE-2025-21820, CVE-2024-57993, CVE-2024-58071, CVE-2024-58017, CVE-2024-58019, CVE-2025-21745, CVE-2024-58016, CVE-2024-58011, CVE-2024-58054, CVE-2025-21731, CVE-2024-58058, CVE-2024-58082, CVE-2025-21722, CVE-2024-58063, CVE-2024-58014, CVE-2025-21735, CVE-2025-21828, CVE-2025-21804, CVE-2024-58018, CVE-2025-21814, CVE-2024-58005, CVE-2024-58078, CVE-2025-21832, CVE-2025-21725, CVE-2025-21732, CVE-2025-21718, CVE-2024-58069, CVE-2024-58052, CVE-2024-57973, CVE-2025-21825, CVE-2024-58056, CVE-2024-58080, CVE-2025-21810, CVE-2024-57953, CVE-2025-37974, CVE-2024-57979, CVE-2025-21708, CVE-2024-57974, CVE-2025-21753, CVE-2025-21736, CVE-2025-21728, CVE-2025-21743, CVE-2025-21815, CVE-2025-21802, CVE-2025-21739, CVE-2024-57986, CVE-2024-57982, CVE-2025-21749, CVE-2025-21806, CVE-2025-21754, CVE-2025-21738, CVE-2025-21716, CVE-2025-21705, CVE-2024-57998, CVE-2024-58006, CVE-2024-58068, CVE-2025-21748, CVE-2024-58077, CVE-2025-21723, CVE-2024-58013, CVE-2025-21719, CVE-2024-58002, CVE-2025-21750, CVE-2024-58053, CVE-2024-58070, CVE-2025-21809, CVE-2024-57975, CVE-2025-21816, CVE-2025-21798, CVE-2024-58051, CVE-2024-58083, CVE-2025-21808, CVE-2025-21799, CVE-2024-57996, CVE-2024-58085, CVE-2025-21744, CVE-2024-57994, CVE-2024-58055, CVE-2024-58076, CVE-2025-21710, CVE-2025-21707, CVE-2024-58072, CVE-2025-21726, CVE-2025-21811, CVE-2025-37750, CVE-2024-58001, CVE-2025-21714, CVE-2025-21711, CVE-2025-21830, CVE-2024-58007, CVE-2025-21812, CVE-2025-21734, CVE-2024-58034, CVE-2024-58081, CVE-2024-58079, CVE-2024-58003, CVE-2025-21721, CVE-2024-49887, CVE-2024-57984, CVE-2025-21715, CVE-2025-21801, CVE-2024-57997, CVE-2025-21741, CVE-2025-21727, CVE-2024-58057, CVE-2025-21724, CVE-2024-57990, CVE-2024-57981, CVE-2024-57999, CVE-2025-21733, CVE-2025-21829, CVE-2024-58010, CVE-2025-21720, CVE-2025-21826)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2024-57980, CVE-2024-57999, CVE-2025-21727, CVE-2024-58058, CVE-2024-58052, CVE-2025-21739, CVE-2025-21722, CVE-2024-58072, CVE-2025-21748, CVE-2024-57993, CVE-2024-58003, CVE-2024-58077, CVE-2025-21734, CVE-2024-58070, CVE-2025-21719, CVE-2024-58006, CVE-2025-21826, CVE-2024-58061, CVE-2025-21745, CVE-2025-21715, CVE-2024-58078, CVE-2025-21829, CVE-2024-49887, CVE-2025-21742, CVE-2025-21721, CVE-2025-21724, CVE-2025-21828, CVE-2025-21814, CVE-2025-21801, CVE-2024-57953, CVE-2024-58081, CVE-2024-58080, CVE-2025-21753, CVE-2025-21732, CVE-2025-21811, CVE-2025-37974, CVE-2024-58068, CVE-2024-58010, CVE-2024-58011, CVE-2024-58085, CVE-2025-21714, CVE-2025-21705, CVE-2025-21735, CVE-2024-58001, CVE-2024-58082, CVE-2024-58055, CVE-2025-21743, CVE-2025-21716, CVE-2024-57998, CVE-2025-21731, CVE-2024-58017, CVE-2024-58053, CVE-2025-21808, CVE-2024-57997, CVE-2024-58016, CVE-2024-58076, CVE-2025-21710, CVE-2025-21738, CVE-2025-21809, CVE-2025-21733, CVE-2025-21810, CVE-2024-57996, CVE-2024-58005, CVE-2025-21720, CVE-2025-21728, CVE-2024-58054, CVE-2024-58057, CVE-2025-21725, CVE-2025-21812, CVE-2025-21830, CVE-2024-58014, CVE-2025-21832, CVE-2024-58002, CVE-2025-21802, CVE-2024-57986, CVE-2025-21749, CVE-2024-58018, CVE-2024-57984, CVE-2025-21736, CVE-2024-58079, CVE-2024-58034, CVE-2024-57973, CVE-2024-57974, CVE-2025-21718, CVE-2025-21723, CVE-2024-58019, CVE-2025-21820, CVE-2024-58013, CVE-2025-21707, CVE-2024-58071, CVE-2025-21711, CVE-2024-58056, CVE-2024-58007, CVE-2024-58051, CVE-2025-21815, CVE-2024-57982, CVE-2025-21799, CVE-2025-21754, CVE-2025-21708, CVE-2025-21798, CVE-2024-57979, CVE-2024-57981, CVE-2024-58069, CVE-2025-21744, CVE-2025-21741, CVE-2024-58063, CVE-2024-58083, CVE-2024-57994, CVE-2025-21804, CVE-2025-21825, CVE-2024-57990, CVE-2025-21726, CVE-2025-21806, CVE-2024-57975, CVE-2025-21750, CVE-2025-21816, CVE-2025-37750)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2024-58058, CVE-2024-57984, CVE-2025-21727, CVE-2025-21812, CVE-2024-58070, CVE-2024-57974, CVE-2025-21810, CVE-2025-21816, CVE-2024-58085, CVE-2025-21738, CVE-2024-58057, CVE-2025-21733, CVE-2024-58054, CVE-2024-57994, CVE-2025-21721, CVE-2024-57979, CVE-2025-21825, CVE-2025-37750, CVE-2025-21750, CVE-2025-21798, CVE-2024-58080, CVE-2024-58034, CVE-2025-21724, CVE-2025-21714, CVE-2025-21742, CVE-2025-21720, CVE-2024-58077, CVE-2025-21710, CVE-2024-58014, CVE-2024-58052, CVE-2024-57986, CVE-2024-58007, CVE-2024-58017, CVE-2025-21731, CVE-2024-58056, CVE-2025-21722, CVE-2025-21826, CVE-2024-58079, CVE-2024-58005, CVE-2025-21732, CVE-2025-21749, CVE-2024-57998, CVE-2024-58055, CVE-2025-21809, CVE-2025-21806, CVE-2025-21820, CVE-2024-58010, CVE-2025-21829, CVE-2025-21705, CVE-2024-58082, CVE-2024-58051, CVE-2024-57982, CVE-2025-21723, CVE-2024-58053, CVE-2024-57973, CVE-2024-58006, CVE-2025-21707, CVE-2024-58061, CVE-2025-21735, CVE-2025-21804, CVE-2024-58068, CVE-2024-57996, CVE-2025-21748, CVE-2024-57999, CVE-2024-58069, CVE-2024-57953, CVE-2025-21718, CVE-2024-49887, CVE-2025-21708, CVE-2024-58063, CVE-2024-58001, CVE-2025-21811, CVE-2025-21744, CVE-2025-21754, CVE-2025-21734, CVE-2025-21715, CVE-2024-57981, CVE-2025-21743, CVE-2024-57990, CVE-2024-58011, CVE-2025-21745, CVE-2024-58076, CVE-2024-58002, CVE-2024-57997, CVE-2025-21728, CVE-2025-21802, CVE-2025-21830, CVE-2025-21719, CVE-2025-21711, CVE-2024-57975, CVE-2025-37974, CVE-2025-21716, CVE-2024-58071, CVE-2024-58019, CVE-2025-21828, CVE-2025-21832, CVE-2025-21799, CVE-2025-21739, CVE-2024-58083, CVE-2025-21725, CVE-2024-58013, CVE-2025-21801, CVE-2025-21808, CVE-2024-58003, CVE-2025-21814, CVE-2024-58016, CVE-2024-58072, CVE-2024-57993, CVE-2024-58018, CVE-2025-21726, CVE-2024-57980, CVE-2024-58081, CVE-2024-58078, CVE-2025-21736, CVE-2025-21753, CVE-2025-21741, CVE-2025-21815)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2024-58052, CVE-2025-21826, CVE-2025-21736, CVE-2025-21809, CVE-2025-21723, CVE-2024-57994, CVE-2025-21802, CVE-2024-58003, CVE-2024-58078, CVE-2025-21742, CVE-2025-21721, CVE-2024-57973, CVE-2025-21830, CVE-2025-21733, CVE-2025-21714, CVE-2024-58002, CVE-2025-21804, CVE-2025-21825, CVE-2024-58014, CVE-2024-58055, CVE-2025-21808, CVE-2024-57986, CVE-2024-57997, CVE-2024-57981, CVE-2025-21753, CVE-2025-21743, CVE-2025-37750, CVE-2024-57975, CVE-2025-21741, CVE-2025-21715, CVE-2025-21744, CVE-2025-21829, CVE-2025-21801, CVE-2025-21815, CVE-2024-58051, CVE-2024-58082, CVE-2024-58058, CVE-2024-58079, CVE-2024-58006, CVE-2024-58011, CVE-2025-21750, CVE-2024-57996, CVE-2025-21705, CVE-2024-58056, CVE-2024-58072, CVE-2025-21806, CVE-2024-57999, CVE-2025-21814, CVE-2024-58080, CVE-2024-57953, CVE-2025-37974, CVE-2025-21732, CVE-2024-58069, CVE-2024-58053, CVE-2024-58054, CVE-2025-21725, CVE-2025-21708, CVE-2025-21799, CVE-2024-57998, CVE-2024-57984, CVE-2025-21719, CVE-2024-58057, CVE-2024-57990, CVE-2024-57979, CVE-2025-21722, CVE-2025-21812, CVE-2024-58071, CVE-2024-57974, CVE-2024-58076, CVE-2024-57980, CVE-2024-58005, CVE-2024-58007, CVE-2024-58083, CVE-2025-21716, CVE-2025-21710, CVE-2025-21745, CVE-2024-58063, CVE-2024-58018, CVE-2024-57993, CVE-2024-49887, CVE-2025-21798, CVE-2024-58081, CVE-2025-21810, CVE-2024-58068, CVE-2024-58013, CVE-2025-21731, CVE-2024-57982, CVE-2025-21727, CVE-2025-21738, CVE-2025-21811, CVE-2024-58085, CVE-2025-21735, CVE-2025-21720, CVE-2025-21748, CVE-2025-21749, CVE-2024-58077, CVE-2025-21711, CVE-2025-21726, CVE-2025-21754, CVE-2024-58019, CVE-2025-21739, CVE-2024-58010, CVE-2024-58070, CVE-2025-21724, CVE-2024-58061, CVE-2025-21820, CVE-2025-21816, CVE-2025-21718, CVE-2024-58017, CVE-2025-21734, CVE-2025-21728, CVE-2024-58034, CVE-2024-58016, CVE-2024-58001, CVE-2025-21832, CVE-2025-21707, CVE-2025-21828)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2024-57973, CVE-2024-58076, CVE-2025-21733, CVE-2024-58016, CVE-2024-58013, CVE-2025-21731, CVE-2024-58017, CVE-2024-58079, CVE-2025-21815, CVE-2025-21812, CVE-2025-21705, CVE-2025-21804, CVE-2025-21718, CVE-2025-21802, CVE-2025-21708, CVE-2024-58011, CVE-2025-21734, CVE-2025-21716, CVE-2024-57998, CVE-2025-21715, CVE-2024-57975, CVE-2024-57981, CVE-2025-21738, CVE-2025-21820, CVE-2025-21721, CVE-2024-58069, CVE-2025-21732, CVE-2025-21742, CVE-2025-21754, CVE-2025-21745, CVE-2024-57974, CVE-2025-21826, CVE-2025-37974, CVE-2025-21801, CVE-2024-58054, CVE-2024-58071, CVE-2025-21799, CVE-2024-58034, CVE-2024-58070, CVE-2025-21739, CVE-2024-58061, CVE-2024-57980, CVE-2025-21741, CVE-2024-57990, CVE-2025-21816, CVE-2025-21719, CVE-2024-57999, CVE-2025-37750, CVE-2024-49887, CVE-2025-21808, CVE-2024-58081, CVE-2025-21710, CVE-2025-21728, CVE-2024-58018, CVE-2025-21825, CVE-2024-57986, CVE-2025-21727, CVE-2024-57984, CVE-2025-21725, CVE-2024-57979, CVE-2024-58056, CVE-2025-21707, CVE-2025-21811, CVE-2024-58003, CVE-2024-58057, CVE-2024-58063, CVE-2024-58005, CVE-2025-21748, CVE-2024-57993, CVE-2024-58006, CVE-2025-21832, CVE-2024-58072, CVE-2025-21736, CVE-2025-21798, CVE-2025-21711, CVE-2024-58002, CVE-2024-58080, CVE-2025-21720, CVE-2024-58010, CVE-2025-21809, CVE-2025-21829, CVE-2024-58019, CVE-2025-21724, CVE-2024-58058, CVE-2025-21735, CVE-2024-57994, CVE-2024-58078, CVE-2024-57997, CVE-2025-21806, CVE-2024-58077, CVE-2024-58051, CVE-2024-58083, CVE-2024-58055, CVE-2025-21750, CVE-2024-58082, CVE-2024-58001, CVE-2025-21810, CVE-2025-21744, CVE-2024-57953, CVE-2024-58007, CVE-2025-21722, CVE-2025-21828, CVE-2025-21714, CVE-2024-58053, CVE-2025-21726, CVE-2024-58085, CVE-2024-58014, CVE-2024-58052, CVE-2025-21749, CVE-2025-21814, CVE-2025-21743, CVE-2024-57996, CVE-2025-21830, CVE-2025-21723, CVE-2024-58068, CVE-2025-21753, CVE-2024-57982)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2025-21829, CVE-2025-21753, CVE-2024-58051, CVE-2025-21738, CVE-2025-21727, CVE-2025-21719, CVE-2024-57982, CVE-2025-21745, CVE-2024-58003, CVE-2025-21716, CVE-2025-21728, CVE-2024-58001, CVE-2024-58069, CVE-2025-21754, CVE-2025-21812, CVE-2025-21816, CVE-2024-58071, CVE-2024-58018, CVE-2025-21708, CVE-2024-58078, CVE-2025-21707, CVE-2025-21741, CVE-2024-57996, CVE-2024-58019, CVE-2024-58014, CVE-2024-58058, CVE-2024-57953, CVE-2025-21710, CVE-2024-58061, CVE-2025-21808, CVE-2025-21826, CVE-2025-21725, CVE-2025-21722, CVE-2025-21733, CVE-2024-58034, CVE-2025-21718, CVE-2025-21714, CVE-2025-21723, CVE-2025-21743, CVE-2025-21736, CVE-2024-58056, CVE-2025-21810, CVE-2024-58077, CVE-2024-58002, CVE-2024-49887, CVE-2025-21739, CVE-2024-57980, CVE-2025-21721, CVE-2025-21815, CVE-2025-21811, CVE-2024-57974, CVE-2024-58005, CVE-2025-21814, CVE-2024-58055, CVE-2025-21744, CVE-2025-21798, CVE-2024-58082, CVE-2024-58081, CVE-2025-21832, CVE-2024-58053, CVE-2025-21828, CVE-2024-58076, CVE-2025-21820, CVE-2024-58083, CVE-2024-58054, CVE-2024-57984, CVE-2025-21742, CVE-2024-58013, CVE-2025-21799, CVE-2025-21715, CVE-2025-21750, CVE-2025-21804, CVE-2024-57994, CVE-2024-58010, CVE-2024-58007, CVE-2024-58011, CVE-2024-57975, CVE-2025-37750, CVE-2025-21731, CVE-2025-21726, CVE-2024-58052, CVE-2024-57979, CVE-2025-21720, CVE-2025-21724, CVE-2024-57986, CVE-2024-58057, CVE-2024-58080, CVE-2024-58079, CVE-2024-57990, CVE-2025-21748, CVE-2025-21806, CVE-2025-21825, CVE-2024-58016, CVE-2025-21711, CVE-2024-58072, CVE-2025-21732, CVE-2024-57999, CVE-2024-57981, CVE-2024-58068, CVE-2025-21734, CVE-2024-58017, CVE-2024-57997, CVE-2025-21749, CVE-2025-37974, CVE-2025-21802, CVE-2024-58070, CVE-2025-21809, CVE-2024-58063, CVE-2024-58085, CVE-2025-21735, CVE-2024-57973, CVE-2024-58006, CVE-2024-57993, CVE-2025-21705, CVE-2024-57998, CVE-2025-21830, CVE-2025-21801)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2024-58055, CVE-2024-58077, CVE-2024-58080, CVE-2024-58082, CVE-2025-21743, CVE-2024-57953, CVE-2024-57994, CVE-2025-21806, CVE-2024-58007, CVE-2024-58002, CVE-2024-57974, CVE-2024-57980, CVE-2025-21720, CVE-2024-57990, CVE-2025-21725, CVE-2024-58057, CVE-2024-58018, CVE-2024-58011, CVE-2025-21814, CVE-2025-21799, CVE-2024-58017, CVE-2024-58014, CVE-2025-21731, CVE-2024-58072, CVE-2024-58069, CVE-2024-58006, CVE-2024-57984, CVE-2025-21710, CVE-2024-58061, CVE-2024-57997, CVE-2024-57975, CVE-2025-21724, CVE-2025-37974, CVE-2025-21808, CVE-2024-58056, CVE-2025-21753, CVE-2024-58068, CVE-2025-21728, CVE-2025-21714, CVE-2024-58054, CVE-2025-21741, CVE-2025-21736, CVE-2025-21715, CVE-2025-21802, CVE-2025-21739, CVE-2025-21727, CVE-2025-21749, CVE-2024-58053, CVE-2024-58081, CVE-2025-21828, CVE-2025-21705, CVE-2024-58051, CVE-2024-57979, CVE-2025-21754, CVE-2025-21734, CVE-2025-21829, CVE-2025-21735, CVE-2025-21826, CVE-2025-21738, CVE-2024-58079, CVE-2025-21815, CVE-2025-21708, CVE-2024-57986, CVE-2024-58085, CVE-2025-21801, CVE-2024-58071, CVE-2025-21810, CVE-2025-21726, CVE-2025-21744, CVE-2025-21830, CVE-2025-21748, CVE-2024-58001, CVE-2024-58063, CVE-2024-57996, CVE-2025-21716, CVE-2024-58013, CVE-2024-58019, CVE-2025-21811, CVE-2025-21711, CVE-2024-58076, CVE-2024-58070, CVE-2024-57982, CVE-2024-57998, CVE-2025-21745, CVE-2025-21804, CVE-2024-57973, CVE-2024-58083, CVE-2025-21742, CVE-2025-37750, CVE-2025-21733, CVE-2025-21750, CVE-2024-57981, CVE-2025-21718, CVE-2024-58058, CVE-2024-49887, CVE-2024-58003, CVE-2024-57993, CVE-2024-57999, CVE-2024-58010, CVE-2025-21825, CVE-2025-21732, CVE-2025-21719, CVE-2025-21721, CVE-2024-58034, CVE-2024-58005, CVE-2025-21707, CVE-2025-21809, CVE-2024-58078, CVE-2025-21812, CVE-2024-58016, CVE-2025-21816, CVE-2024-58052, CVE-2025-21722, CVE-2025-21832, CVE-2025-21723, CVE-2025-21820, CVE-2025-21798)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Mellanox network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• i.MX PM domains;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Serial drivers;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• GFS2 file system;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Kernel CPU control infrastructure;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• DCCP (Datagram Congestion Control Protocol);
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• VMware vSockets driver;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2025-21830, CVE-2025-21678, CVE-2025-21815, CVE-2024-57974, CVE-2025-21725, CVE-2025-21718, CVE-2025-21748, CVE-2025-21732, CVE-2024-57953, CVE-2025-21727, CVE-2025-21816, CVE-2025-21719, CVE-2024-53124, CVE-2024-58019, CVE-2025-38001, CVE-2025-21720, CVE-2025-21734, CVE-2025-21672, CVE-2025-21692, CVE-2024-58076, CVE-2025-21694, CVE-2024-58061, CVE-2025-21714, CVE-2025-21689, CVE-2024-49887, CVE-2024-57949, CVE-2025-38177, CVE-2025-21683, CVE-2025-21669, CVE-2025-21722, CVE-2024-57980, CVE-2025-38000, CVE-2025-37932, CVE-2024-58034, CVE-2024-58081, CVE-2025-21733, CVE-2025-21682, CVE-2024-57924, CVE-2025-21743, CVE-2024-57975, CVE-2025-37798, CVE-2024-58058, CVE-2025-21809, CVE-2025-21676, CVE-2024-57993, CVE-2025-21699, CVE-2024-58016, CVE-2025-21832, CVE-2025-21804, CVE-2024-58011, CVE-2024-58007, CVE-2025-21826, CVE-2024-58055, CVE-2025-21668, CVE-2025-21715, CVE-2024-58078, CVE-2025-21829, CVE-2025-21811, CVE-2025-21814, CVE-2024-58053, CVE-2025-21726, CVE-2025-21943, CVE-2025-37750, CVE-2025-21673, CVE-2024-57984, CVE-2025-37997, CVE-2025-21684, CVE-2025-21750, CVE-2024-58013, CVE-2025-21799, CVE-2024-58083, CVE-2025-21798, CVE-2025-21731, CVE-2025-21708, CVE-2024-57986, CVE-2025-21744, CVE-2024-58014, CVE-2025-21721, CVE-2024-58063, CVE-2024-57979, CVE-2024-58005, CVE-2025-21728, CVE-2025-21681, CVE-2025-21806, CVE-2024-57982, CVE-2024-58002, CVE-2024-58082, CVE-2025-21812, CVE-2025-21745, CVE-2024-58017, CVE-2025-21665, CVE-2025-21828, CVE-2025-37890,…

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM64 architecture;
• PowerPC architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device (Mouse) drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• SPI subsystem;
• Media staging drivers;
• Trusted Execution Environment drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB core drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• Framebuffer layer;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• L3 Master device support module;
• TCP network protocol;
• XFRM subsystem;
• Tracing infrastructure;
• io_uring subsystem;
• Process Accounting mechanism;
• BPF subsystem;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Workqueue subsystem;
• Memory management;
• B.A.T.M.A.N. meshing protocol;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers;
• SOF drivers; (CVE-2025-37750, CVE-2025-21707, CVE-2025-21814, CVE-2025-21863, CVE-2025-21775, CVE-2024-57997, CVE-2025-21749, CVE-2025-21739, CVE-2025-21829, CVE-2025-21731, CVE-2025-21704, CVE-2024-57979, CVE-2025-21864, CVE-2024-57953, CVE-2025-21796, CVE-2025-21826, CVE-2024-57998, CVE-2025-21784, CVE-2024-58072, CVE-2025-21859, CVE-2025-21790, CVE-2025-21762, CVE-2025-37797, CVE-2024-57981, CVE-2024-58068, CVE-2025-21810, CVE-2024-58070, CVE-2025-21738, CVE-2024-58081, CVE-2024-58010, CVE-2025-21832, CVE-2025-21839, CVE-2024-58061, CVE-2024-58069, CVE-2024-58055, CVE-2024-57834, CVE-2025-21804, CVE-2025-21783, CVE-2025-21772, CVE-2024-57975, CVE-2024-57980, CVE-2024-58082, CVE-2025-21741, CVE-2025-21733, CVE-2025-21750, CVE-2025-21728, CVE-2025-21716, CVE-2025-21753, CVE-2025-21802, CVE-2024-57993, CVE-2025-21785, CVE-2024-57994, CVE-2025-21868, CVE-2025-21812, CVE-2025-21760, CVE-2025-21782, CVE-2025-21763, CVE-2024-57999, CVE-2025-21823, CVE-2024-57986, CVE-2024-58080, CVE-2025-21766, CVE-2025-21743, CVE-2025-21838, CVE-2025-21706, CVE-2025-21820, CVE-2024-58003, CVE-2025-21809, CVE-2025-21867, CVE-2024-57982, CVE-2025-21759, CVE-2024-57984, CVE-2025-21736, CVE-2024-58058, CVE-2025-21754, CVE-2024-49887, CVE-2025-21781, CVE-2025-21795, CVE-2025-21746, CVE-2024-58019, CVE-2025-21780, CVE-2024-58083, CVE-2025-21734, CVE-2025-21764, CVE-2025-21825, CVE-2024-54456, CVE-2024-58056, CVE-2025-21861, CVE-2024-57973, CVE-2025-21735, CVE-2025-21705, CVE-2024-57990, CVE-2025-21836, CVE-2025-21816, CVE-2024-58088, CVE-2024-58005, CVE-2025-21761,…

Duoming Zhou discovered race conditions in the AX.25 amateur radio protocol implementation in the Linux kernel, leading to use-after-free vulnerabilities. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2022-1205)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• USB Gadget drivers;
• Networking core;
• ARM32 architecture;
• ARM64 architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Speakup Console Speech Driver;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• Auxiliary display drivers;
• Drivers core;
• Bluetooth drivers;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Clocksource drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• Google firmware drivers;
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• HSI subsystem;
• Hardware monitoring drivers;
• CoreSight HW tracing drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• Input Device (Mouse) drivers;
• On-Chip Interconnect management framework;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Media drivers;
• Analog Devices digital potentiometer driver;
• Broadcom VK accelerator driver;
• Fastrpc Driver;
• MMC subsystem;
• MTD block device drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• STMicroelectronics network drivers;
• Texas Instruments network drivers;
• MediaTek network drivers;
• Near Field Communication (NFC) drivers;
• NTB driver;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• PA-RISC drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• Chrome hardware platform drivers;
• Mellanox platform drivers;
• Microsoft Surface platform drivers;
• x86 platform drivers;
• Power supply drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• RPMSG subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• SPI subsystem;
• small TFT LCD display modules;
• Greybus lights staging drivers;
• Media staging drivers;
• Realtek RTL8723BS SDIO drivers;
• TCM subsystem;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• Userspace I/O drivers;
• USB DSL drivers;
• Cypress C67X00 USB driver;
• USB core drivers;
• USB Host Controller drivers;
• Mustek MDC800 USB digital camera driver;
• USB Serial drivers;
• USB Mass Storage drivers;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• W1 Dallas's 1-wire bus driver;
• Watchdog drivers;
• Xen hypervisor drivers;
• 9P distributed file system;
• File systems infrastructure;
• BFS file system;
• BTRFS file system;
• Ceph distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• FAT file system;
• FUSE (File system in Userspace);
• HFS+ file system;
• HugeTLB file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• NTFS3 file system;
• OCFS2 file system; …

Duoming Zhou discovered race conditions in the AX.25 amateur radio protocol implementation in the Linux kernel, leading to use-after-free vulnerabilities. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2022-1205)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• USB Gadget drivers;
• ARM32 architecture;
• ARM64 architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Speakup Console Speech Driver;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• Auxiliary display drivers;
• Drivers core;
• Bluetooth drivers;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Clocksource drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Google firmware drivers;
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• HSI subsystem;
• Hardware monitoring drivers;
• CoreSight HW tracing drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• On-Chip Interconnect management framework;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Media drivers;
• Analog Devices digital potentiometer driver;
• Broadcom VK accelerator driver;
• Fastrpc Driver;
• MMC subsystem;
• MTD block device drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• MediaTek network drivers;
• Near Field Communication (NFC) drivers;
• NTB driver;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• PA-RISC drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• Chrome hardware platform drivers;
• Mellanox platform drivers;
• Microsoft Surface platform drivers;
• x86 platform drivers;
• Power supply drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• RPMSG subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• SPI subsystem;
• small TFT LCD display modules;
• Greybus lights staging drivers;
• Media staging drivers;
• Realtek RTL8723BS SDIO drivers;
• TCM subsystem;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• Userspace I/O drivers;
• USB DSL drivers;
• Cypress C67X00 USB driver;
• USB core drivers;
• USB Host Controller drivers;
• Mustek MDC800 USB digital camera driver;
• USB Serial drivers;
• USB Mass Storage drivers;
• USB Type-C Connector System Software Interface driver;
• USB over IP driver;
• vDPA drivers;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• W1 Dallas's 1-wire bus driver;
• Watchdog drivers;
• File systems infrastructure;
• BFS file system;
• BTRFS file system;
• Ceph distributed file system;
• eCrypt file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• FAT file system;
• FUSE (File system in Userspace);
• HFS+ file system;
• HugeTLB file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• NTFS3 file system;
• OCFS2 file system;
• OrangeFS file system;
• SMB network file system;
• SquashFS file system;
• UBI file system;
• UDF file system;
• XFS file system;
• BPF subsystem;
• IPv4 networking;
• Internal shared memory driver;
• Networking core;
• Scheduler infrastructure;
• Sun RPC protocol;
• Virtio network driver;
• Amateur Radio drivers;
• IP tunnels definitions;
• Network…

Duoming Zhou discovered race conditions in the AX.25 amateur radio protocol implementation in the Linux kernel, leading to use-after-free vulnerabilities. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2022-1205)

It was discovered that the i.MX clock driver in the Linux kernel did not properly handle certain memory allocation failure conditions, leading to a null pointer dereference vulnerability. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2022-3114)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• USB Gadget drivers;
• Networking core;
• User-space API (UAPI);
• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• OpenRISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Speakup Console Speech Driver;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Auxiliary display drivers;
• Drivers core;
• DRBD Distributed Replicated Block Device drivers;
• Rados block device (RBD) driver;
• Bluetooth drivers;
• Cdrom driver;
• Character device driver;
• Hardware random number generator core;
• TPM device driver;
• Clock framework and drivers;
• Clocksource drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• FireWire subsystem;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• Google firmware drivers;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• HSI subsystem;
• Hardware monitoring drivers;
• CoreSight HW tracing drivers;
• Intel Trace Hub HW tracing drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• IIO ADC drivers;
• IIO Magnetometer sensors drivers;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• Input Device (Mouse) drivers;
• On-Chip Interconnect management framework;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• MemoryStick subsystem;
• Multifunction device drivers;
• Analog Devices digital potentiometer driver;
• Broadcom VK accelerator driver;
• Fastrpc Driver;
• MMC subsystem;
• MTD block device drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• STMicroelectronics network drivers;
• Texas Instruments network drivers;
• MediaTek network drivers;
• Near Field Communication (NFC) drivers;
• NTB driver;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• PA-RISC drivers;
• Parport drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• Chrome hardware platform drivers;
• Mellanox platform drivers;
• Microsoft Surface platform drivers;
• x86 platform drivers;
• Generic PM domains;
• System reset/shutdown drivers;
• Power supply drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• Reset controller framework;
• RPMSG subsystem;
• Real Time Clock drivers;
• S/390 drivers;
• SCSI subsystem;
• SLIMbus drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Greybus lights staging drivers;
• Media staging drivers;
• Media Oriented Systems Transport (MOST) driver;
• NVIDIA Tegra embedded controller (NVEC)…