CVE-2025-38086

The Linux Kernel, the operating system core itself.

Security Fix(es):

A vulnerability was found in Linux Kernel up to 6.15.3 (Operating System). It has been rated as problematic.Using CWE to declare the problem leads to CWE-252. The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.Impacted is confidentiality, integrity, and availability.Upgrading to version 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4 or 6.16-rc1 eliminates this vulnerability. Applying the patch 119766de4930ff40db9f36b960cb53b0c400e81b/33163c68d2e3061fa3935b5f0a1867958b1cdbd2/9da3e442714f7f4393ff01c265c4959c03e88c2f/9a350f30d65197354706b7759b5c89d6c267b1a9/6bd2569d0b2f918e9581f744df0263caf73ee76c/4da7fcc098218ff92b2e83a43f545c02f714cedd/cdaa6d1cb2ff1219c6c822b27655dd170ffb0f72/9ad0452c0277b816a435433cca601304cfac7c21 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-19447).(CVE-2025-38086)

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

sch_hfsc: make hfsc_qlen_notify() idempotent

hfsc_qlen_notify() is not idempotent either and not friendly to its callers, like fq_codel_dequeue(). Let's make it idempotent to ease qdisc_tree_reduce_backlog() callers' life:

1. update_vf() decreases cl->cl_nactive, so we can check whether it is non-zero before calling it.

2. eltree_remove() always removes RB node cl->el_node, but we can use RB_EMPTY_NODE() + RB_CLEAR_NODE() to make it safe.(CVE-2025-38177)

A vulnerability was found in Linux Kernel up to 6.16-rc2 (Operating System) and classified as critical.Using CWE to declare the problem leads to CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.Impacted is availability.Upgrading to version 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4 or 6.16-rc3 eliminates this vulnerability. Applying the patch 956f1499412ed0953f6a116df7fdb855e9f1fc66/f4ae0f61dd9a63329ecb49b1e6356139d43240b8/dc724bd34d56f5589f7587a091a8cda2386826c4/058dd4a370f23a5553a9449f2db53d5bfa88d45e/bde8833eb075ba8e8674de88e32de6b669966451/988edde4d52d5c02ea4dd95d7619372a5e2fb7b7/d092c7fd8e220b23d6c47e03d7d0cc79e731f379/10876da918fa1aec0227fb4c67647513447f53a9 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.(CVE-2025-38181)

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.15.3 (Operating System).The manipulation of the argument ext4_prepare_inline_data with an unknown input leads to a unknown weakness.This is going to have an impact on confidentiality, integrity, and availability.Upgrading to version 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4 or 6.16-rc1 eliminates this vulnerability. Applying the patch d3dfc60efd145df5324b99a244b0b05505cde29b/717414a8c083c376d4a8940a1230fe0c6ed4ee00/9d1d1c5bf4fc1af76be154d3afb2acdbd89ec7d8/cf5f319a2d8ab8238f8cf3a19463b9bff6420934/26e09d18599da0adc543eabd300080daaeda6869/5766da2237e539f259aa0e5f3639ae37b44ca458/e80ee0263d88d77f2fd1927f915003a7066cbb50/227cb4ca5a6502164f850d22aec3104d7888b270 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-20034).(CVE-2025-38222)

A vulnerability was found in Linux Kernel up to 6.16-rc4 (Operating System). It has been classified as critical.CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or…

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:

Bluetooth: hci_conn: Use disable_delayed_work_sync

This makes use of disable_delayed_work_sync instead cancel_delayed_work_sync as it not only cancel the ongoing work but also disables new submit which is disarable since the object holding the work is about to be freed.(CVE-2024-56591)

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

ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().

fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything when it fails.

Commit 7dd73168e273 ("ipv6: Always allocate pcpu memory in a fib6_nh") moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init() but forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in case it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.

Let's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the error path.

Note that we can remove the fib6_nh_release() call in nh_create_ipv6() later in net-next.git.(CVE-2025-22005)

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

fs/ntfs3: Fix a couple integer overflows on 32bit systems

On 32bit systems the "off + sizeof(struct NTFS_DE)" addition can have an integer wrapping issue. Fix it by using size_add().(CVE-2025-22081)

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

jfs: Prevent copying of nlink with value 0 from disk inode

syzbot report a deadlock in diFree. [1]

When calling "ioctl$LOOP_SET_STATUS64", the offset value passed in is 4, which does not match the mounted loop device, causing the mapping of the mounted loop device to be invalidated.

When creating the directory and creating the inode of iag in diReadSpecial(), read the page of fixed disk inode (AIT) in raw mode in read_metapage(), the metapage data it returns is corrupted, which causes the nlink value of 0 to be assigned to the iag inode when executing copy_from_dinode(), which ultimately causes a deadlock when entering diFree().

To avoid this, first check the nlink value of dinode before setting iag inode.

[1] WARNING: possible recursive locking detected 6.12.0-rc7-syzkaller-00212-g4a5df3796467 #0 Not tainted

syz-executor301/5309 is trying to acquire lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x37c/0x2fb0 fs/jfs/jfs_imap.c:889

but task is already holding lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630

other info that might help us debug this: Possible unsafe locking scenario:

   CPU0
   ----

lock(&(imap->im_aglock[index])); lock(&(imap->im_aglock[index]));

*** DEADLOCK ***

May be due to missing lock nesting notation

5 locks held by syz-executor301/5309: #0: ffff8880422a4420 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:515 #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:850 [inline] #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x260/0x540 fs/namei.c:4026 #2: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630 #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2460 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocAG+0x4b7/0x1e50 fs/jfs/jfs_imap.c:1669 #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2477 [inline] #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #4: ffff88804755a618…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

Bluetooth: hci_conn: Use disable_delayed_work_sync

This makes use of disable_delayed_work_sync instead cancel_delayed_work_sync as it not only cancel the ongoing work but also disables new submit which is disarable since the object holding the work is about to be freed.(CVE-2024-56591)

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

ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().

fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything when it fails.

Commit 7dd73168e273 ("ipv6: Always allocate pcpu memory in a fib6_nh") moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init() but forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in case it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.

Let's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the error path.

Note that we can remove the fib6_nh_release() call in nh_create_ipv6() later in net-next.git.(CVE-2025-22005)

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

fs/ntfs3: Fix a couple integer overflows on 32bit systems

On 32bit systems the "off + sizeof(struct NTFS_DE)" addition can have an integer wrapping issue. Fix it by using size_add().(CVE-2025-22081)

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

jfs: Prevent copying of nlink with value 0 from disk inode

syzbot report a deadlock in diFree. [1]

When calling "ioctl$LOOP_SET_STATUS64", the offset value passed in is 4, which does not match the mounted loop device, causing the mapping of the mounted loop device to be invalidated.

When creating the directory and creating the inode of iag in diReadSpecial(), read the page of fixed disk inode (AIT) in raw mode in read_metapage(), the metapage data it returns is corrupted, which causes the nlink value of 0 to be assigned to the iag inode when executing copy_from_dinode(), which ultimately causes a deadlock when entering diFree().

To avoid this, first check the nlink value of dinode before setting iag inode.

[1] WARNING: possible recursive locking detected 6.12.0-rc7-syzkaller-00212-g4a5df3796467 #0 Not tainted

syz-executor301/5309 is trying to acquire lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x37c/0x2fb0 fs/jfs/jfs_imap.c:889

but task is already holding lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630

other info that might help us debug this: Possible unsafe locking scenario:

   CPU0
   ----

lock(&(imap->im_aglock[index])); lock(&(imap->im_aglock[index]));

*** DEADLOCK ***

May be due to missing lock nesting notation

5 locks held by syz-executor301/5309: #0: ffff8880422a4420 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:515 #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:850 [inline] #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x260/0x540 fs/namei.c:4026 #2: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630 #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2460 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocAG+0x4b7/0x1e50 fs/jfs/jfs_imap.c:1669 #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2477 [inline] #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #4: ffff88804755a618…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

Bluetooth: hci_conn: Use disable_delayed_work_sync

This makes use of disable_delayed_work_sync instead cancel_delayed_work_sync as it not only cancel the ongoing work but also disables new submit which is disarable since the object holding the work is about to be freed.(CVE-2024-56591)

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

ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().

fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything when it fails.

Commit 7dd73168e273 ("ipv6: Always allocate pcpu memory in a fib6_nh") moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init() but forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in case it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.

Let's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the error path.

Note that we can remove the fib6_nh_release() call in nh_create_ipv6() later in net-next.git.(CVE-2025-22005)

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

fs/ntfs3: Fix a couple integer overflows on 32bit systems

On 32bit systems the "off + sizeof(struct NTFS_DE)" addition can have an integer wrapping issue. Fix it by using size_add().(CVE-2025-22081)

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

jfs: Prevent copying of nlink with value 0 from disk inode

syzbot report a deadlock in diFree. [1]

When calling "ioctl$LOOP_SET_STATUS64", the offset value passed in is 4, which does not match the mounted loop device, causing the mapping of the mounted loop device to be invalidated.

When creating the directory and creating the inode of iag in diReadSpecial(), read the page of fixed disk inode (AIT) in raw mode in read_metapage(), the metapage data it returns is corrupted, which causes the nlink value of 0 to be assigned to the iag inode when executing copy_from_dinode(), which ultimately causes a deadlock when entering diFree().

To avoid this, first check the nlink value of dinode before setting iag inode.

[1] WARNING: possible recursive locking detected 6.12.0-rc7-syzkaller-00212-g4a5df3796467 #0 Not tainted

syz-executor301/5309 is trying to acquire lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x37c/0x2fb0 fs/jfs/jfs_imap.c:889

but task is already holding lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630

other info that might help us debug this: Possible unsafe locking scenario:

   CPU0
   ----

lock(&(imap->im_aglock[index])); lock(&(imap->im_aglock[index]));

*** DEADLOCK ***

May be due to missing lock nesting notation

5 locks held by syz-executor301/5309: #0: ffff8880422a4420 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:515 #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:850 [inline] #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x260/0x540 fs/namei.c:4026 #2: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630 #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2460 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocAG+0x4b7/0x1e50 fs/jfs/jfs_imap.c:1669 #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2477 [inline] #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #4: ffff88804755a618…

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). (CVE-2024-50154)

• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). (CVE-2024-50154)

• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)

• kernel: wifi: iwlwifi: limit printed string from FW file (CVE-2025-21905)

• kernel: RDMA/mlx5: Fix page_size variable overflow (CVE-2025-22091)

• kernel: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() (CVE-2025-22121)

• kernel: ext4: avoid journaling sb update on error if journal is destroying (CVE-2025-22113)

• kernel: RDMA/core: Fix use-after-free when rename device name (CVE-2025-22085)

• kernel: net_sched: hfsc: Fix a UAF vulnerability in class handling (CVE-2025-37797)

• kernel: mm/huge_memory: fix dereferencing invalid pmd migration entry (CVE-2025-37958)

• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

• kernel: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (CVE-2025-38110)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: padata: fix UAF in padata_reorder (CVE-2025-21727)

• kernel: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() (CVE-2025-21928)

• kernel: HID: intel-ish-hid: Fix use-after-free issue in hid_ishtp_cl_remove() (CVE-2025-21929)

• kernel: memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove (CVE-2025-22020)

• kernel: ext4: avoid journaling sb update on error if journal is destroying (CVE-2025-22113)

• kernel: RDMA/core: Fix use-after-free when rename device name (CVE-2025-22085)

• kernel: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (CVE-2025-37890)

• kernel: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done (CVE-2025-38052)

• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

• kernel: net/sched: fix use-after-free in taprio_dev_notifier (CVE-2025-38087)

• kernel: nvme-tcp: sanitize request list handling (CVE-2025-38264)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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

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

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

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

In the Linux kernel, the following vulnerability has been resolved: net: ch9200: fix uninitialised access during mii_nway_restart In mii_nway_restart() the code attempts to call mii->mdio_read which is ch9200_mdio_read(). ch9200_mdio_read() utilises a local buffer called "buff", which is initialised with control_read(). However "buff" is conditionally initialised inside control_read(): if (err == size) { memcpy(data, buf, size); } If the condition of "err == size" is not met, then "buff" remains uninitialised. Once this happens the uninitialised "buff" is accessed and returned during ch9200_mdio_read(): return (buff[0] | buff[1] << 8); The problem stems from the fact that ch9200_mdio_read() ignores the return value of control_read(), leading to uinit-access of "buff". To fix this we should check the return value of control_read() and return early on error.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). (CVE-2024-50154)
• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). (CVE-2024-50154)
• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)
• kernel: wifi: iwlwifi: limit printed string from FW file (CVE-2025-21905)
• kernel: RDMA/mlx5: Fix page_size variable overflow (CVE-2025-22091)
• kernel: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() (CVE-2025-22121)
• kernel: ext4: avoid journaling sb update on error if journal is destroying (CVE-2025-22113)
• kernel: RDMA/core: Fix use-after-free when rename device name (CVE-2025-22085)
• kernel: net_sched: hfsc: Fix a UAF vulnerability in class handling (CVE-2025-37797)
• kernel: mm/huge_memory: fix dereferencing invalid pmd migration entry (CVE-2025-37958)
• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)
• kernel: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (CVE-2025-38110)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: padata: fix UAF in padata_reorder (CVE-2025-21727)
• kernel: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() (CVE-2025-21928)
• kernel: HID: intel-ish-hid: Fix use-after-free issue in hid_ishtp_cl_remove() (CVE-2025-21929)
• kernel: memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove (CVE-2025-22020)
• kernel: ext4: avoid journaling sb update on error if journal is destroying (CVE-2025-22113)
• kernel: RDMA/core: Fix use-after-free when rename device name (CVE-2025-22085)
• kernel: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (CVE-2025-37890)
• kernel: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done (CVE-2025-38052)
• kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)
• kernel: net/sched: fix use-after-free in taprio_dev_notifier (CVE-2025-38087)
• kernel: nvme-tcp: sanitize request list handling (CVE-2025-38264)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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

net: ch9200: fix uninitialised access during mii_nway_restart

In mii_nway_restart() the code attempts to call mii->mdio_read which is ch9200_mdio_read(). ch9200_mdio_read() utilises a local buffer called "buff", which is initialised with control_read(). However "buff" is conditionally initialised inside control_read():

    if (err == size) {
            memcpy(data, buf, size);
    }

If the condition of "err == size" is not met, then "buff" remains uninitialised. Once this happens the uninitialised "buff" is accessed and returned during ch9200_mdio_read():

    return (buff[0] | buff[1] << 8);

The problem stems from the fact that ch9200_mdio_read() ignores the return value of control_read(), leading to uinit-access of "buff".

To fix this we should check the return value of control_read() and return early on error.

• net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}
• idpf: fix null-ptr-deref in idpf_features_check {CVE-2025-38053}
• ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead {CVE-2022-49977}
• sched/fair: Fix potential memory corruption in child_cfs_rq_on_list {CVE-2025-21919}
• wifi: iwlwifi: limit printed string from FW file {CVE-2025-21905}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes {CVE-2025-21991}
• ext4: ignore xattrs past end {CVE-2025-37738}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• cifs: potential buffer overflow in handling symlinks {CVE-2022-49058}
• media: uvcvideo: Remove dangling pointers {CVE-2024-58002}

• net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}
• jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted {CVE-2022-50126}
• kernfs: fix potential NULL dereference in __kernfs_remove {CVE-2022-50148}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• xhci: Fix null pointer dereference in remove if xHC has only one roothub {CVE-2022-49962}
• ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead {CVE-2022-49977}
• wifi: iwlwifi: limit printed string from FW file {CVE-2025-21905}
• udmabuf: Set the DMA mask for the udmabuf device (v2) {CVE-2022-49983}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event {CVE-2022-50136}
• iavf: Fix reset error handling {CVE-2022-50053}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• ext4: ignore xattrs past end {CVE-2025-37738}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• media: uvcvideo: Remove dangling pointers {CVE-2024-58002}
• netfilter: flowtable: fix stuck flows on cleanup due to pending work {CVE-2022-50000}
• netfilter: flowtable: add function to invoke garbage collection immediately {CVE-2022-50000}

• net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}
• jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted {CVE-2022-50126}
• kernfs: fix potential NULL dereference in __kernfs_remove {CVE-2022-50148}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• xhci: Fix null pointer dereference in remove if xHC has only one roothub {CVE-2022-49962}
• ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead {CVE-2022-49977}
• wifi: iwlwifi: limit printed string from FW file {CVE-2025-21905}
• iavf: Fix reset error handling {CVE-2022-50053}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• ext4: ignore xattrs past end {CVE-2025-37738}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• media: uvcvideo: Remove dangling pointers {CVE-2024-58002}
• RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event {CVE-2022-50136}
• stmmac: intel: Add a missing clk_disable_unprepare() call in intel_eth_pci_remove() {CVE-2022-50039}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• udmabuf: Set the DMA mask for the udmabuf device (v2) {CVE-2022-49983}
• netfilter: flowtable: fix stuck flows on cleanup due to pending work {CVE-2022-50000}
• netfilter: flowtable: add function to invoke garbage collection immediately {CVE-2022-50000}
• drm/amd/display: clear optc underflow before turn off odm clock {CVE-2022-49969}

• net_sched: hfsc: Fix a UAF vulnerability in class handling {CVE-2025-37797}
• sunrpc: handle SVC_GARBAGE during svc auth processing as auth error {CVE-2025-38089}
• net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}
• ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() {CVE-2025-22121}
• locking/csd_lock: Change csdlock_debug from early_param to __setup {CVE-2022-50091}
• x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes {CVE-2025-21991}
• ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead {CVE-2022-49977}
• NFSv4/pnfs: Fix a use-after-free bug in open {CVE-2022-50072}
• NFSv4: Don't hold the layoutget locks across multiple RPC calls {CVE-2022-49316}
• mm/khugepaged: fix ->anon_vma race {CVE-2023-52935}

• rds: tcp: block BH in TCP callbacks
• kexec: Improve & fix crash_exclude_mem_range() to handle overlapping ranges
• module: correctly exit module_kallsyms_on_each_symbol when fn() != 0
• module: potential uninitialized return in module_kallsyms_on_each_symbol()
• module: use RCU to synchronize find_module
• kallsyms: refactor {,module_}kallsyms_on_each_symbol
• LTS tag: v5.4.295
• scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops
• arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() {CVE-2025-38320}
• perf: Fix sample vs do_exit() {CVE-2025-38424}
• s390/pci: Fix __pcilg_mio_inuser() inline assembly
• rtc: test: Fix invalid format specifier.
• jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() {CVE-2025-38337}
• mm/huge_memory: fix dereferencing invalid pmd migration entry {CVE-2025-37958}
• rtc: Make rtc_time64_to_tm() support dates before 1970
• rtc: Improve performance of rtc_time64_to_tm(). Add tests.
• xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create {CVE-2022-48773}
• posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}
• ARM: dts: am335x-bone-common: Increase MDIO reset deassert delay to 50ms
• ARM: dts: am335x-bone-common: Increase MDIO reset deassert time
• ARM: dts: am335x-bone-common: Add GPIO PHY reset on revision C3 board
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• net: atm: add lec_mutex {CVE-2025-38323}
• calipso: Fix null-ptr-deref in calipso_req_{set,del}attr(). {CVE-2025-38181}
• tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer {CVE-2025-38184}
• tcp: fix tcp_packet_delayed() for tcp_is_non_sack_preventing_reopen() behavior
• atm: atmtcp: Free invalid length skb in atmtcp_c_send(). {CVE-2025-38185}
• mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu(). {CVE-2025-38324}
• wifi: carl9170: do not ping device which has failed to load firmware {CVE-2025-38420}
• aoe: clean device rq_list in aoedev_downdev() {CVE-2025-38326}
• hwmon: (occ) fix unaligned accesses
• drm/nouveau/bl: increase buffer size to avoid truncate warning
• erofs: remove unused trace event erofs_destroy_inode
• ALSA: hda/realtek: enable headset mic on Latitude 5420 Rugged
• ALSA: hda/intel: Add Thinkpad E15 to PM deny list
• Input: sparcspkr - avoid unannotated fall-through
• HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() {CVE-2025-38103}
• atm: Revert atm_account_tx() if copy_from_iter_full() fails. {CVE-2025-38190}
• selinux: fix selinux_xfrm_alloc_user() to set correct ctx_len
• scsi: s390: zfcp: Ensure synchronous unit_add
• scsi: storvsc: Increase the timeouts to storvsc_timeout
• jffs2: check jffs2_prealloc_raw_node_refs() result in few other places {CVE-2025-38328}
• jffs2: check that raw node were preallocated before writing summary {CVE-2025-38194}
• drivers/rapidio/rio_cm.c: prevent possible heap overwrite {CVE-2025-38090}
• powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery
• platform/x86: dell_rbu: Stop overwriting data buffer
• platform: Add Surface platform directory
• Revert "bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first"
• tee: Prevent size calculation wraparound on 32-bit kernels
• ARM: OMAP2+: Fix l4ls clk domain handling in STANDBY
• bus: fsl-mc: increase MC_CMD_COMPLETION_TIMEOUT_MS value
• watchdog: da9052_wdt: respect TWDMIN
• i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}
• sock: Correct error checking condition for (assign|release)_proto_idx()
• scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
• vxlan: Do not treat dst cache initialization errors as fatal
• clk: rockchip: rk3036: mark ddrphy as critical
• wifi: mac80211: do not offer a mesh path if forwarding is disabled
• net: mlx4: add SOF_TIMESTAMPING_TX_SOFTWARE flag when getting ts info
• pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get()
• pinctrl: armada-37xx:…

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

net: ch9200: fix uninitialised access during mii_nway_restart

In mii_nway_restart() the code attempts to call mii->mdio_read which is ch9200_mdio_read(). ch9200_mdio_read() utilises a local buffer called "buff", which is initialised with control_read(). However "buff" is conditionally initialised inside control_read():

    if (err == size) {
            memcpy(data, buf, size);
    }

If the condition of "err == size" is not met, then "buff" remains uninitialised. Once this happens the uninitialised "buff" is accessed and returned during ch9200_mdio_read():

    return (buff[0] | buff[1] << 8);

The problem stems from the fact that ch9200_mdio_read() ignores the return value of control_read(), leading to uinit-access of "buff".

To fix this we should check the return value of control_read() and return early on error.

Vanilla upstream kernel version 6.6.101 fixes bugs and vulnerabilities. For information about the vulnerabilities see the links.

Upstream kernel version 6.6.101 fixes bugs and vulnerabilities. The kmod-virtualbox, kmod-xtables-addons & wireless-regdb packages have been updated to work with this new kernel. For information about the vulnerabilities see the links.

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;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Bus devices;
• Clock framework and drivers;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• GPU drivers;
• HID subsystem;
• InfiniBand drivers;
• Input Device (Miscellaneous) drivers;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• TCM subsystem;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• BTRFS file system;
• File systems infrastructure;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NTFS3 file system;
• DRM display driver;
• Memory Management;
• Mellanox drivers;
• Memory management;
• Netfilter;
• Network sockets;
• IPC subsystem;
• BPF subsystem;
• Perf events;
• Kernel exit() syscall;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Appletalk network protocol;
• Asynchronous Transfer Mode (ATM) subsystem;
• Networking core;
• IPv6 networking;
• MultiProtocol Label Switching driver;
• NetLabel subsystem;
• Netlink;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• TIPC protocol;
• VMware vSockets driver;
• USB sound devices; (CVE-2025-38465, CVE-2025-38386, CVE-2025-38273, CVE-2025-38227, CVE-2025-38107, CVE-2025-37958, CVE-2025-38371, CVE-2025-38328, CVE-2025-38348, CVE-2025-38100, CVE-2025-38336, CVE-2025-38420, CVE-2025-38154, CVE-2025-38542, CVE-2025-38222, CVE-2025-38406, CVE-2025-37948, CVE-2025-38112, CVE-2025-38145, CVE-2025-38163, CVE-2025-38464, CVE-2025-38085, CVE-2025-38342, CVE-2025-38310, CVE-2025-38326, CVE-2025-38418, CVE-2025-38362, CVE-2025-38412, CVE-2025-38219, CVE-2025-38332, CVE-2025-38387, CVE-2025-38262, CVE-2025-38157, CVE-2025-38514, CVE-2025-38466, CVE-2025-38313, CVE-2025-38159, CVE-2024-44939, CVE-2025-38352, CVE-2025-38459, CVE-2025-38419, CVE-2025-38086, CVE-2025-38298, CVE-2025-38146, CVE-2025-38181, CVE-2025-38448, CVE-2025-38231, CVE-2025-38461, CVE-2025-38251, CVE-2025-38391, CVE-2025-38515, CVE-2024-26726, CVE-2025-38462, CVE-2025-38416, CVE-2025-38280, CVE-2025-38226, CVE-2025-38211, CVE-2025-38120, CVE-2025-38377, CVE-2025-38147, CVE-2025-38204, CVE-2025-38345, CVE-2025-38424, CVE-2025-38203, CVE-2025-38443, CVE-2025-38197, CVE-2025-38067, CVE-2025-38400, CVE-2025-38229, CVE-2025-38108, CVE-2025-38319, CVE-2025-38445, CVE-2025-38212, CVE-2025-38184, CVE-2025-38363, CVE-2025-38160, CVE-2024-57883, CVE-2025-38441, CVE-2025-38320, CVE-2025-38393, CVE-2025-38200, CVE-2025-38467, CVE-2025-38444, CVE-2025-38194, CVE-2025-38460, CVE-2025-38167, CVE-2025-38428, CVE-2025-38312, CVE-2025-38111, CVE-2025-38498, CVE-2025-38135, CVE-2025-38237, CVE-2025-38457, CVE-2025-38401, CVE-2025-38206, CVE-2025-38293, CVE-2025-38143, CVE-2025-38161, CVE-2025-38136, CVE-2022-48703, CVE-2025-38513, CVE-2025-38430, CVE-2025-38384, CVE-2025-38346, CVE-2025-38337, CVE-2025-38088, CVE-2025-38257, CVE-2025-38395, CVE-2025-38153,…

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;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Bus devices;
• Clock framework and drivers;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• GPU drivers;
• HID subsystem;
• InfiniBand drivers;
• Input Device (Miscellaneous) drivers;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• TCM subsystem;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• BTRFS file system;
• File systems infrastructure;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NTFS3 file system;
• DRM display driver;
• Memory Management;
• Mellanox drivers;
• Memory management;
• Netfilter;
• Network sockets;
• IPC subsystem;
• BPF subsystem;
• Perf events;
• Kernel exit() syscall;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Appletalk network protocol;
• Asynchronous Transfer Mode (ATM) subsystem;
• Networking core;
• IPv6 networking;
• MultiProtocol Label Switching driver;
• NetLabel subsystem;
• Netlink;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• TIPC protocol;
• VMware vSockets driver;
• USB sound devices; (CVE-2025-38310, CVE-2025-38443, CVE-2025-37963, CVE-2025-38161, CVE-2025-38231, CVE-2025-38229, CVE-2025-38263, CVE-2025-38103, CVE-2025-38249, CVE-2025-38286, CVE-2025-38181, CVE-2025-37948, CVE-2025-38085, CVE-2025-38273, CVE-2025-21888, CVE-2025-38074, CVE-2025-38467, CVE-2025-38257, CVE-2025-38387, CVE-2025-38348, CVE-2025-38465, CVE-2025-38377, CVE-2025-38336, CVE-2025-38173, CVE-2025-38084, CVE-2025-38100, CVE-2025-38293, CVE-2025-38174, CVE-2025-38418, CVE-2025-38107, CVE-2025-38371, CVE-2025-38184, CVE-2025-38262, CVE-2025-38466, CVE-2025-38400, CVE-2025-38145, CVE-2025-38459, CVE-2025-38153, CVE-2025-38163, CVE-2025-38102, CVE-2025-38457, CVE-2024-26726, CVE-2025-38384, CVE-2025-38115, CVE-2025-38328, CVE-2025-38245, CVE-2025-37958, CVE-2025-38212, CVE-2025-38391, CVE-2025-38227, CVE-2025-38439, CVE-2025-38146, CVE-2025-38515, CVE-2025-38160, CVE-2025-38159, CVE-2025-38460, CVE-2025-38420, CVE-2025-38280, CVE-2025-38136, CVE-2025-38200, CVE-2025-38462, CVE-2025-38218, CVE-2025-38458, CVE-2025-38516, CVE-2024-26775, CVE-2025-38108, CVE-2025-38375, CVE-2025-38203, CVE-2025-38401, CVE-2025-38211, CVE-2025-38119, CVE-2025-38337, CVE-2025-38428, CVE-2025-38352, CVE-2025-38120, CVE-2025-38345, CVE-2025-38320, CVE-2025-38395, CVE-2025-38305, CVE-2025-38204, CVE-2025-38285, CVE-2025-38346, CVE-2025-38416, CVE-2025-38226, CVE-2025-38406, CVE-2025-38412, CVE-2025-38122, CVE-2025-38403, CVE-2025-38540, CVE-2025-38138, CVE-2025-38206, CVE-2025-38194, CVE-2025-38386, CVE-2025-38143, CVE-2025-38154, CVE-2025-38298, CVE-2025-38237, CVE-2025-38090, CVE-2025-38332, CVE-2025-38319, CVE-2025-38313, CVE-2025-38135, CVE-2025-38424, CVE-2025-38088, CVE-2025-38362, CVE-2025-38219, CVE-2025-38430, CVE-2025-38197, CVE-2025-38461,…

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;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Bus devices;
• Clock framework and drivers;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• GPU drivers;
• HID subsystem;
• InfiniBand drivers;
• Input Device (Miscellaneous) drivers;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• TCM subsystem;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• BTRFS file system;
• File systems infrastructure;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NTFS3 file system;
• DRM display driver;
• Memory Management;
• Mellanox drivers;
• Memory management;
• Netfilter;
• Network sockets;
• IPC subsystem;
• BPF subsystem;
• Perf events;
• Kernel exit() syscall;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Appletalk network protocol;
• Asynchronous Transfer Mode (ATM) subsystem;
• Networking core;
• IPv6 networking;
• MultiProtocol Label Switching driver;
• NetLabel subsystem;
• Netlink;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• TIPC protocol;
• VMware vSockets driver;
• USB sound devices; (CVE-2025-38399, CVE-2025-38391, CVE-2025-38412, CVE-2025-38393, CVE-2025-38163, CVE-2025-38167, CVE-2025-38319, CVE-2025-38135, CVE-2025-37963, CVE-2025-38226, CVE-2025-38147, CVE-2025-38513, CVE-2025-38161, CVE-2025-38146, CVE-2025-38352, CVE-2025-38458, CVE-2025-38444, CVE-2025-38430, CVE-2025-38418, CVE-2025-38206, CVE-2025-38160, CVE-2025-38461, CVE-2025-38465, CVE-2025-38119, CVE-2025-38459, CVE-2025-38410, CVE-2025-38111, CVE-2025-38222, CVE-2025-38313, CVE-2025-38285, CVE-2025-38067, CVE-2025-38143, CVE-2025-38200, CVE-2024-44939, CVE-2025-38219, CVE-2024-26775, CVE-2025-38090, CVE-2025-38262, CVE-2025-38332, CVE-2025-38345, CVE-2025-38337, CVE-2025-38403, CVE-2025-38085, CVE-2025-38229, CVE-2025-38540, CVE-2025-38362, CVE-2025-38384, CVE-2025-38115, CVE-2025-38136, CVE-2025-38445, CVE-2025-38424, CVE-2025-38328, CVE-2025-38389, CVE-2025-38428, CVE-2025-38516, CVE-2025-38336, CVE-2025-38184, CVE-2025-38293, CVE-2025-38346, CVE-2025-38464, CVE-2025-38251, CVE-2025-38112, CVE-2025-38194, CVE-2025-38375, CVE-2025-38466, CVE-2025-38157, CVE-2025-38457, CVE-2025-38320, CVE-2025-38406, CVE-2025-37948, CVE-2025-38145, CVE-2025-38395, CVE-2025-38218, CVE-2025-38154, CVE-2025-38401, CVE-2025-38103, CVE-2025-38088, CVE-2025-38298, CVE-2025-38108, CVE-2025-38120, CVE-2025-38086, CVE-2025-38415, CVE-2025-38443, CVE-2025-38245, CVE-2025-38400, CVE-2025-38371, CVE-2025-38084, CVE-2022-48703, CVE-2025-38237, CVE-2025-38324, CVE-2025-38515, CVE-2025-38107, CVE-2025-38448, CVE-2025-38153, CVE-2025-38342, CVE-2025-38102, CVE-2025-38173, CVE-2025-38441, CVE-2025-38138, CVE-2025-38257, CVE-2025-38386, CVE-2025-38514, CVE-2025-38363, CVE-2025-38231, CVE-2025-38159, CVE-2025-38203, CVE-2025-38344, CVE-2025-38211, CVE-2025-38286,…

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;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Bus devices;
• Clock framework and drivers;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• GPU drivers;
• HID subsystem;
• InfiniBand drivers;
• Input Device (Miscellaneous) drivers;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• TCM subsystem;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• BTRFS file system;
• File systems infrastructure;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NTFS3 file system;
• DRM display driver;
• Memory Management;
• Mellanox drivers;
• Memory management;
• Netfilter;
• Network sockets;
• IPC subsystem;
• BPF subsystem;
• Perf events;
• Kernel exit() syscall;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Appletalk network protocol;
• Asynchronous Transfer Mode (ATM) subsystem;
• Networking core;
• IPv6 networking;
• MultiProtocol Label Switching driver;
• NetLabel subsystem;
• Netlink;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• TIPC protocol;
• VMware vSockets driver;
• USB sound devices; (CVE-2025-38212, CVE-2025-38377, CVE-2025-38328, CVE-2025-38167, CVE-2025-38119, CVE-2025-38143, CVE-2025-38513, CVE-2025-38257, CVE-2025-38443, CVE-2025-38420, CVE-2025-38067, CVE-2025-38111, CVE-2025-38448, CVE-2025-38107, CVE-2025-38465, CVE-2025-38237, CVE-2025-38174, CVE-2025-38516, CVE-2025-38100, CVE-2025-38120, CVE-2025-38219, CVE-2025-38194, CVE-2025-38085, CVE-2025-38441, CVE-2025-38227, CVE-2024-57883, CVE-2025-38088, CVE-2025-38352, CVE-2025-38159, CVE-2025-38410, CVE-2025-38406, CVE-2025-38204, CVE-2025-38345, CVE-2025-38393, CVE-2025-38074, CVE-2025-38146, CVE-2025-38160, CVE-2025-38102, CVE-2025-37963, CVE-2025-38466, CVE-2025-38286, CVE-2025-38263, CVE-2025-38415, CVE-2025-38386, CVE-2025-38416, CVE-2025-38375, CVE-2025-38136, CVE-2025-38285, CVE-2025-38108, CVE-2025-38251, CVE-2025-38391, CVE-2025-38161, CVE-2025-38157, CVE-2025-38462, CVE-2025-38319, CVE-2025-38395, CVE-2025-38135, CVE-2025-38326, CVE-2025-38090, CVE-2025-38147, CVE-2025-38461, CVE-2025-38540, CVE-2025-21888, CVE-2025-38515, CVE-2025-38445, CVE-2025-38498, CVE-2025-38249, CVE-2025-38312, CVE-2025-38173, CVE-2025-38153, CVE-2025-38400, CVE-2025-38324, CVE-2025-38245, CVE-2025-38313, CVE-2024-26775, CVE-2025-38163, CVE-2025-38387, CVE-2025-38298, CVE-2025-38112, CVE-2025-38231, CVE-2025-38084, CVE-2025-38439, CVE-2025-38211, CVE-2025-38145, CVE-2025-38273, CVE-2025-38203, CVE-2025-38467, CVE-2025-38320, CVE-2025-38444, CVE-2025-38262, CVE-2025-38293, CVE-2025-37948, CVE-2025-38336, CVE-2025-38419, CVE-2025-38458, CVE-2025-38384, CVE-2025-38460, CVE-2025-38115, CVE-2025-38337, CVE-2025-38305, CVE-2025-38399, CVE-2025-38371, CVE-2025-38542, CVE-2025-38332, CVE-2025-38389, CVE-2025-37958, CVE-2025-38346, CVE-2025-38226, CVE-2025-38218,…