CVE-2025-38285

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

pfifo_tail_enqueue: Drop new packet when sch->limit == 0

Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return NET_XMIT_CN status code.

Weird behaviour: In case we set sch->limit == 0 and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return NET_XMIT_CN status code.

The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B.

• Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's say Qdisc_A's type is hfsc. Enqueue packet to this qdisc will trigger hfsc_enqueue.
• Qdisc_B's type is pfifo_head_drop. Enqueue packet to this qdisc will trigger pfifo_tail_enqueue.
• Qdisc_B is configured to have sch->limit == 0.
• Qdisc_A is configured to route the enqueued's packet to Qdisc_B.

Enqueue packet through Qdisc_A will lead to:

• hfsc_enqueue(Qdisc_A) -> pfifo_tail_enqueue(Qdisc_B)
• Qdisc_B->q.qlen += 1
• pfifo_tail_enqueue() return NET_XMIT_CN
• hfsc_enqueue() check for NET_XMIT_SUCCESS and see NET_XMIT_CN => hfsc_enqueue() don't increase qlen of Qdisc_A.

The whole process lead to a situation where Qdisc_A->q.qlen == 0 and Qdisc_B->q.qlen == 1. Replace 'hfsc' with other type (for example: 'drr') still lead to the same problem. This violate the design where parent's qlen should equal to the sum of its childrens'qlen.

Bug impact: This issue can be used for user->kernel privilege escalation when it is reachable.(CVE-2025-21702)

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

mptcp: always handle address removal under msk socket lock

Syzkaller reported a lockdep splat in the PM control path:

WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 sock_owned_by_me include/net/sock.h:1711 [inline] WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 msk_owned_by_me net/mptcp/protocol.h:363 [inline] WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788 Modules linked in: CPU: 0 UID: 0 PID: 6693 Comm: syz.0.205 Not tainted 6.14.0-rc2-syzkaller-00303-gad1b832bf1cf #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 RIP: 0010:sock_owned_by_me include/net/sock.h:1711 [inline] RIP: 0010:msk_owned_by_me net/mptcp/protocol.h:363 [inline] RIP: 0010:mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788 Code: 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 ca 7b d3 f5 eb b9 e8 c3 7b d3 f5 90 0f 0b 90 e9 dd fb ff ff e8 b5 7b d3 f5 90 <0f> 0b 90 e9 3e fb ff ff 44 89 f1 80 e1 07 38 c1 0f 8c eb fb ff ff RSP: 0000:ffffc900034f6f60 EFLAGS: 00010283 RAX: ffffffff8bee3c2b RBX: 0000000000000001 RCX: 0000000000080000 RDX: ffffc90004d42000 RSI: 000000000000a407 RDI: 000000000000a408 RBP: ffffc900034f7030 R08: ffffffff8bee37f6 R09: 0100000000000000 R10: dffffc0000000000 R11: ffffed100bcc62e4 R12: ffff88805e6316e0 R13: ffff88805e630c00 R14: dffffc0000000000 R15: ffff88805e630c00 FS: 00007f7e9a7e96c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2fd18ff8 CR3: 0000000032c24000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3:…

The Linux Kernel, the operating system core itself.

Security Fix(es):

Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. There is a security vulnerability in Linux kernel, which originates from a qlen count error in sch_hfsc, which may cause inconsistent queue statistics.(CVE-2025-38000)

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

media: cxusb: no longer judge rbuf when the write fails

syzbot reported a uninit-value in cxusb_i2c_xfer. [1]

Only when the write operation of usb_bulk_msg() in dvb_usb_generic_rw() succeeds and rlen is greater than 0, the read operation of usb_bulk_msg() will be executed to read rlen bytes of data from the dvb device into the rbuf.

In this case, although rlen is 1, the write operation failed which resulted in the dvb read operation not being executed, and ultimately variable i was not initialized.

[1] BUG: KMSAN: uninit-value in cxusb_gpio_tuner drivers/media/usb/dvb-usb/cxusb.c:124 [inline] BUG: KMSAN: uninit-value in cxusb_i2c_xfer+0x153a/0x1a60 drivers/media/usb/dvb-usb/cxusb.c:196 cxusb_gpio_tuner drivers/media/usb/dvb-usb/cxusb.c:124 [inline] cxusb_i2c_xfer+0x153a/0x1a60 drivers/media/usb/dvb-usb/cxusb.c:196 __i2c_transfer+0xe25/0x3150 drivers/i2c/i2c-core-base.c:-1 i2c_transfer+0x317/0x4a0 drivers/i2c/i2c-core-base.c:2315 i2c_transfer_buffer_flags+0x125/0x1e0 drivers/i2c/i2c-core-base.c:2343 i2c_master_send include/linux/i2c.h:109 [inline] i2cdev_write+0x210/0x280 drivers/i2c/i2c-dev.c:183 do_loop_readv_writev fs/read_write.c:848 [inline] vfs_writev+0x963/0x14e0 fs/read_write.c:1057 do_writev+0x247/0x5c0 fs/read_write.c:1101 __do_sys_writev fs/read_write.c:1169 [inline] __se_sys_writev fs/read_write.c:1166 [inline] __x64_sys_writev+0x98/0xe0 fs/read_write.c:1166 x64_sys_call+0x2229/0x3c80 arch/x86/include/generated/asm/syscalls_64.h:21 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2025-38229)

A vulnerability has been found in Linux Kernel up to 6.15.2 (Operating System) and classified as critical.The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).As an impact it is known to affect confidentiality, integrity, and availability.Upgrading to version 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15.3 or 6.16-rc1 eliminates this vulnerability. Applying the patch 44ebe361abb322d2afd77930fa767a99f271c4d1/147ea936fc6fa8fe0c93f0df918803a5375ca535/ee90be48edb3dac612e0b7f5332482a9e8be2696/e167414beabb1e941fe563a96becc98627d5bdf6/6d8f39875a10a194051c3eaefebc7ac06a34aaf3/c98cdf6795a36bca163ebb40411fef1687b9eb13/18e8cbbae79cb35bdce8a01c889827b9799c762e/3880cdbed1c4607e378f58fa924c5d6df900d1d3 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-38285)

A vulnerability was found in Linux Kernel up to 6.16-rc2 (Operating System). It has been declared as problematic.The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer.As an impact it is known to affect confidentiality.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 64773b3ea09235168a549a195cba43bb867c4a17/67abac27d806e8f9d4226ec1528540cf73af673a/92750bfe7b0d8dbcaf578c091a65eda1c5f9ad38/01f91d415a8375d85e0c7d3615cd4a168308bb7c/21da6d3561f373898349ca7167c9811c020da695/22f935bc86bdfbde04009f05eee191d220cd8c89/422e565b7889ebfd9c8705a3fc786642afe61fca/39dfc971e42d886e7df01371cd1bef505076d84c is able to eliminate this problem. The bugfix is ready…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

pfifo_tail_enqueue: Drop new packet when sch->limit == 0

Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return NET_XMIT_CN status code.

Weird behaviour: In case we set sch->limit == 0 and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return NET_XMIT_CN status code.

The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B.

• Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's say Qdisc_A's type is hfsc. Enqueue packet to this qdisc will trigger hfsc_enqueue.
• Qdisc_B's type is pfifo_head_drop. Enqueue packet to this qdisc will trigger pfifo_tail_enqueue.
• Qdisc_B is configured to have sch->limit == 0.
• Qdisc_A is configured to route the enqueued's packet to Qdisc_B.

Enqueue packet through Qdisc_A will lead to:

• hfsc_enqueue(Qdisc_A) -> pfifo_tail_enqueue(Qdisc_B)
• Qdisc_B->q.qlen += 1
• pfifo_tail_enqueue() return NET_XMIT_CN
• hfsc_enqueue() check for NET_XMIT_SUCCESS and see NET_XMIT_CN => hfsc_enqueue() don't increase qlen of Qdisc_A.

The whole process lead to a situation where Qdisc_A->q.qlen == 0 and Qdisc_B->q.qlen == 1. Replace 'hfsc' with other type (for example: 'drr') still lead to the same problem. This violate the design where parent's qlen should equal to the sum of its childrens'qlen.

Bug impact: This issue can be used for user->kernel privilege escalation when it is reachable.(CVE-2025-21702)

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

netem: Update sch->q.qlen before qdisc_tree_reduce_backlog()

qdisc_tree_reduce_backlog() notifies parent qdisc only if child qdisc becomes empty, therefore we need to reduce the backlog of the child qdisc before calling it. Otherwise it would miss the opportunity to call cops->qlen_notify(), in the case of DRR, it resulted in UAF since DRR uses ->qlen_notify() to maintain its active list.(CVE-2025-21703)

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

mptcp: always handle address removal under msk socket lock

Syzkaller reported a lockdep splat in the PM control path:

WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 sock_owned_by_me include/net/sock.h:1711 [inline] WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 msk_owned_by_me net/mptcp/protocol.h:363 [inline] WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788 Modules linked in: CPU: 0 UID: 0 PID: 6693 Comm: syz.0.205 Not tainted 6.14.0-rc2-syzkaller-00303-gad1b832bf1cf #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 RIP: 0010:sock_owned_by_me include/net/sock.h:1711 [inline] RIP: 0010:msk_owned_by_me net/mptcp/protocol.h:363 [inline] RIP: 0010:mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788 Code: 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 ca 7b d3 f5 eb b9 e8 c3 7b d3 f5 90 0f 0b 90 e9 dd fb ff ff e8 b5 7b d3 f5 90 <0f> 0b 90 e9 3e fb ff ff 44 89 f1 80 e1 07 38 c1 0f 8c eb fb ff ff RSP: 0000:ffffc900034f6f60 EFLAGS: 00010283 RAX: ffffffff8bee3c2b RBX: 0000000000000001 RCX: 0000000000080000 RDX: ffffc90004d42000 RSI: 000000000000a407 RDI:…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ext4: update s_journal_inum if it changes after journal replay

When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the journal through the old s_journal_inum. And the new s_journal_inum bypasses some of the checks in ext4_get_journal(), which may trigger a null pointer dereference problem. So if s_journal_inum changes after the journal replay, we ignore the change, and rewrite the current journal_inum to the superblock.(CVE-2023-53091)

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

vxlan: Fix nexthop hash size

The nexthop code expects a 31 bit hash, such as what is returned by fib_multipath_hash() and rt6_multipath_hash(). Passing the 32 bit hash returned by skb_get_hash() can lead to problems related to the fact that 'int hash' is a negative number when the MSB is set.

In the case of hash threshold nexthop groups, nexthop_select_path_hthr() will disproportionately select the first nexthop group entry. In the case of resilient nexthop groups, nexthop_select_path_res() may do an out of bounds access in nh_buckets[], for example: hash = -912054133 num_nh_buckets = 2 bucket_index = 65535

which leads to the following panic:

BUG: unable to handle page fault for address: ffffc900025910c8 PGD 100000067 P4D 100000067 PUD 10026b067 PMD 0 Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI CPU: 4 PID: 856 Comm: kworker/4:3 Not tainted 6.5.0-rc2+ #34 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:nexthop_select_path+0x197/0xbf0 Code: c1 e4 05 be 08 00 00 00 4c 8b 35 a4 14 7e 01 4e 8d 6c 25 00 4a 8d 7c 25 08 48 01 dd e8 c2 25 15 ff 49 8d 7d 08 e8 39 13 15 ff <4d> 89 75 08 48 89 ef e8 7d 12 15 ff 48 8b 5d 00 e8 14 55 2f 00 85 RSP: 0018:ffff88810c36f260 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 00000000002000c0 RCX: ffffffffaf02dd77 RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffffc900025910c8 RBP: ffffc900025910c0 R08: 0000000000000001 R09: fffff520004b2219 R10: ffffc900025910cf R11: 31392d2068736168 R12: 00000000002000c0 R13: ffffc900025910c0 R14: 00000000fffef608 R15: ffff88811840e900 FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc900025910c8 CR3: 0000000129d00000 CR4: 0000000000750ee0 PKRU: 55555554 Call Trace: <TASK> ? __die+0x23/0x70 ? page_fault_oops+0x1ee/0x5c0 ? __pfx_is_prefetch.constprop.0+0x10/0x10 ? __pfx_page_fault_oops+0x10/0x10 ? search_bpf_extables+0xfe/0x1c0 ? fixup_exception+0x3b/0x470 ? exc_page_fault+0xf6/0x110 ? asm_exc_page_fault+0x26/0x30 ? nexthop_select_path+0x197/0xbf0 ? nexthop_select_path+0x197/0xbf0 ? lock_is_held_type+0xe7/0x140 vxlan_xmit+0x5b2/0x2340 ? __lock_acquire+0x92b/0x3370 ? __pfx_vxlan_xmit+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_register_lock_class+0x10/0x10 ? skb_network_protocol+0xce/0x2d0 ? dev_hard_start_xmit+0xca/0x350 ? __pfx_vxlan_xmit+0x10/0x10 dev_hard_start_xmit+0xca/0x350 __dev_queue_xmit+0x513/0x1e20 ? __pfx___dev_queue_xmit+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? mark_held_locks+0x44/0x90 ? skb_push+0x4c/0x80 ? eth_header+0x81/0xe0 ? __pfx_eth_header+0x10/0x10 ? neigh_resolve_output+0x215/0x310 ? ip6_finish_output2+0x2ba/0xc90 ip6_finish_output2+0x2ba/0xc90 ? lock_release+0x236/0x3e0 ? ip6_mtu+0xbb/0x240 ? __pfx_ip6_finish_output2+0x10/0x10 ? find_held_lock+0x83/0xa0 ? lock_is_held_type+0xe7/0x140 ip6_finish_output+0x1ee/0x780 ip6_output+0x138/0x460 ? __pfx_ip6_output+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_ip6_finish_output+0x10/0x10 NF_HOOK.constprop.0+0xc0/0x420 ? __pfx_NF_HOOK.constprop.0+0x10/0x10 ?…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

ext4: update s_journal_inum if it changes after journal replay

When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the journal through the old s_journal_inum. And the new s_journal_inum bypasses some of the checks in ext4_get_journal(), which may trigger a null pointer dereference problem. So if s_journal_inum changes after the journal replay, we ignore the change, and rewrite the current journal_inum to the superblock.(CVE-2023-53091)

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

scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write

During the sysfs firmware write process, a use-after-free read warning is logged from the lpfc_wr_object() routine:

BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc] Use-after-free read at 0x0000000000cf164d (in kfence-#111): lpfc_wr_object+0x235/0x310 [lpfc] lpfc_write_firmware.cold+0x206/0x30d [lpfc] lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc] lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc] kernfs_fop_write_iter+0x121/0x1b0 new_sync_write+0x11c/0x1b0 vfs_write+0x1ef/0x280 ksys_write+0x5f/0xe0 do_syscall_64+0x59/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

The driver accessed wr_object pointer data, which was initialized into mailbox payload memory, after the mailbox object was released back to the mailbox pool.

Fix by moving the mailbox free calls to the end of the routine ensuring that we don't reference internal mailbox memory after release.(CVE-2023-53282)

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

start_kernel: Add __no_stack_protector function attribute

Back during the discussion of commit a9a3ed1eff36 ("x86: Fix early boot crash on gcc-10, third try") we discussed the need for a function attribute to control the omission of stack protectors on a per-function basis; at the time Clang had support for no_stack_protector but GCC did not. This was fixed in gcc-11. Now that the function attribute is available, let's start using it.

Callers of boot_init_stack_canary need to use this function attribute unless they're compiled with -fno-stack-protector, otherwise the canary stored in the stack slot of the caller will differ upon the call to boot_init_stack_canary. This will lead to a call to __stack_chk_fail() then panic.(CVE-2023-53491)

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

Bluetooth: Fix hci_suspend_sync crash

If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier may still be accessing it, it can cause the program to crash. Here's the call trace: <4>[102152.653246] Call Trace: <4>[102152.653254] hci_suspend_sync+0x109/0x301 [bluetooth] <4>[102152.653259] hci_suspend_dev+0x78/0xcd [bluetooth] <4>[102152.653263] hci_suspend_notifier+0x42/0x7a [bluetooth] <4>[102152.653268] notifier_call_chain+0x43/0x6b <4>[102152.653271] __blocking_notifier_call_chain+0x48/0x69 <4>[102152.653273] __pm_notifier_call_chain+0x22/0x39 <4>[102152.653276] pm_suspend+0x287/0x57c <4>[102152.653278] state_store+0xae/0xe5 <4>[102152.653281] kernfs_fop_write+0x109/0x173 <4>[102152.653284] __vfs_write+0x16f/0x1a2 <4>[102152.653287] ? selinux_file_permission+0xca/0x16f <4>[102152.653289] ? security_file_permission+0x36/0x109 <4>[102152.653291] vfs_write+0x114/0x21d <4>[102152.653293] __x64_sys_write+0x7b/0xdb <4>[102152.653296] do_syscall_64+0x59/0x194 <4>[102152.653299] entry_SYSCALL_64_after_hwframe+0x5c/0xc1

This patch holds the reference count of the hci_dev object while processing it in…

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

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

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

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

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix WARN() in get_bpf_raw_tp_regs syzkaller reported an issue: WARNING: CPU: 3 PID: 5971 at kernel/trace/bpf_trace.c:1861 get_bpf_raw_tp_regs+0xa4/0x100 kernel/trace/bpf_trace.c:1861 Modules linked in: CPU: 3 UID: 0 PID: 5971 Comm: syz-executor205 Not tainted 6.15.0-rc5-syzkaller-00038-g707df3375124 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:get_bpf_raw_tp_regs+0xa4/0x100 kernel/trace/bpf_trace.c:1861 RSP: 0018:ffffc90003636fa8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffffff81c6bc4c RDX: ffff888032efc880 RSI: ffffffff81c6bc83 RDI: 0000000000000005 RBP: ffff88806a730860 R08: 0000000000000005 R09: 0000000000000003 R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000004 R13: 0000000000000001 R14: ffffc90003637008 R15: 0000000000000900 FS: 0000000000000000(0000) GS:ffff8880d6cdf000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7baee09130 CR3: 0000000029f5a000 CR4: 0000000000352ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1934 [inline] bpf_get_stack_raw_tp+0x24/0x160 kernel/trace/bpf_trace.c:1931 bpf_prog_ec3b2eefa702d8d3+0x43/0x47 bpf_dispatcher_nop_func include/linux/bpf.h:1316 [inline] __bpf_prog_run include/linux/filter.h:718 [inline] bpf_prog_run include/linux/filter.h:725 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:2363 [inline] bpf_trace_run3+0x23f/0x5a0 kernel/trace/bpf_trace.c:2405 __bpf_trace_mmap_lock_acquire_returned+0xfc/0x140 include/trace/events/mmap_lock.h:47 __traceiter_mmap_lock_acquire_returned+0x79/0xc0 include/trace/events/mmap_lock.h:47 __do_trace_mmap_lock_acquire_returned include/trace/events/mmap_lock.h:47 [inline] trace_mmap_lock_acquire_returned include/trace/events/mmap_lock.h:47 [inline] __mmap_lock_do_trace_acquire_returned+0x138/0x1f0 mm/mmap_lock.c:35 __mmap_lock_trace_acquire_returned include/linux/mmap_lock.h:36 [inline] mmap_read_trylock include/linux/mmap_lock.h:204 [inline] stack_map_get_build_id_offset+0x535/0x6f0 kernel/bpf/stackmap.c:157 __bpf_get_stack+0x307/0xa10 kernel/bpf/stackmap.c:483 ____bpf_get_stack kernel/bpf/stackmap.c:499 [inline] bpf_get_stack+0x32/0x40 kernel/bpf/stackmap.c:496 ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1941 [inline] bpf_get_stack_raw_tp+0x124/0x160 kernel/trace/bpf_trace.c:1931 bpf_prog_ec3b2eefa702d8d3+0x43/0x47 Tracepoint like trace_mmap_lock_acquire_returned may cause nested call as the corner case show above, which will be resolved with more general method in the future. As a result, WARN_ON_ONCE will be triggered. As Alexei suggested, remove the WARN_ON_ONCE first.

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

bpf: Fix WARN() in get_bpf_raw_tp_regs

syzkaller reported an issue:

WARNING: CPU: 3 PID: 5971 at kernel/trace/bpf_trace.c:1861 get_bpf_raw_tp_regs+0xa4/0x100 kernel/trace/bpf_trace.c:1861 Modules linked in: CPU: 3 UID: 0 PID: 5971 Comm: syz-executor205 Not tainted 6.15.0-rc5-syzkaller-00038-g707df3375124 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:get_bpf_raw_tp_regs+0xa4/0x100 kernel/trace/bpf_trace.c:1861 RSP: 0018:ffffc90003636fa8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffffff81c6bc4c RDX: ffff888032efc880 RSI: ffffffff81c6bc83 RDI: 0000000000000005 RBP: ffff88806a730860 R08: 0000000000000005 R09: 0000000000000003 R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000004 R13: 0000000000000001 R14: ffffc90003637008 R15: 0000000000000900 FS: 0000000000000000(0000) GS:ffff8880d6cdf000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7baee09130 CR3: 0000000029f5a000 CR4: 0000000000352ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1934 [inline] bpf_get_stack_raw_tp+0x24/0x160 kernel/trace/bpf_trace.c:1931 bpf_prog_ec3b2eefa702d8d3+0x43/0x47 bpf_dispatcher_nop_func include/linux/bpf.h:1316 [inline] __bpf_prog_run include/linux/filter.h:718 [inline] bpf_prog_run include/linux/filter.h:725 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:2363 [inline] bpf_trace_run3+0x23f/0x5a0 kernel/trace/bpf_trace.c:2405 __bpf_trace_mmap_lock_acquire_returned+0xfc/0x140 include/trace/events/mmap_lock.h:47 __traceiter_mmap_lock_acquire_returned+0x79/0xc0 include/trace/events/mmap_lock.h:47 __do_trace_mmap_lock_acquire_returned include/trace/events/mmap_lock.h:47 [inline] trace_mmap_lock_acquire_returned include/trace/events/mmap_lock.h:47 [inline] __mmap_lock_do_trace_acquire_returned+0x138/0x1f0 mm/mmap_lock.c:35 __mmap_lock_trace_acquire_returned include/linux/mmap_lock.h:36 [inline] mmap_read_trylock include/linux/mmap_lock.h:204 [inline] stack_map_get_build_id_offset+0x535/0x6f0 kernel/bpf/stackmap.c:157 __bpf_get_stack+0x307/0xa10 kernel/bpf/stackmap.c:483 ____bpf_get_stack kernel/bpf/stackmap.c:499 [inline] bpf_get_stack+0x32/0x40 kernel/bpf/stackmap.c:496 ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1941 [inline] bpf_get_stack_raw_tp+0x124/0x160 kernel/trace/bpf_trace.c:1931 bpf_prog_ec3b2eefa702d8d3+0x43/0x47

Tracepoint like trace_mmap_lock_acquire_returned may cause nested call as the corner case show above, which will be resolved with more general method in the future. As a result, WARN_ON_ONCE will be triggered. As Alexei suggested, remove the WARN_ON_ONCE first.

• 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:…

• crypto: algif_aead - Fix minimum RX size check for decryption {CVE-2026-31431}
• crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl {CVE-2026-31431}
• crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec {CVE-2026-31431}
• crypto: authencesn - Fix src offset when decrypting in-place {CVE-2026-31431}
• crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption {CVE-2026-31431}
• crypto: authenc - use memcpy_sglist() instead of null skcipher {CVE-2026-31431}
• crypto: algif_aead - snapshot IV for async AEAD requests {CVE-2026-31431}
• crypto: algif_aead - Revert to operating out-of-place {CVE-2026-31431}
• crypto: algif_aead - use memcpy_sglist() instead of null skcipher {CVE-2026-31431}
• crypto: scatterwalk - Backport memcpy_sglist() {CVE-2026-31431}
• wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() {CVE-2022-50551}
• bonding: limit BOND_MODE_8023AD to Ethernet devices {CVE-2026-23099}
• libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}
• scsi: qla2xxx: Fix bsg_done() causing double free {CVE-2025-71238}
• ftrace: Fix use-after-free for dynamic ftrace_ops {CVE-2022-49892}
• intel_th: msu: Fix vmalloced buffers {CVE-2022-50142}
• vt: Clear selection before changing the font {CVE-2022-49948}
• ACPICA: Fix error code path in acpi_ds_call_control_method() {CVE-2022-50411}
• usbnet: Run unregister_netdev() before unbind_all() {CVE-2022-50220}
• ipvs: fix WARNING in ip_vs_app_net_cleanup() {CVE-2022-49917}
• bpf: Propagate error from htab_lock_bucket() to userspace {CVE-2022-50490}
• binfmt_misc: fix shift-out-of-bounds in check_special_flags {CVE-2022-50497}
• module: fix [e_shstrndx].sh_size=0 OOB access {CVE-2022-49444}
• ceph: avoid putting the realm twice when decoding snaps fails {CVE-2022-49770}
• tracing: Fix potential double free in create_var_ref() {CVE-2022-49410}
• powercap: intel_rapl: fix UBSAN shift-out-of-bounds issue {CVE-2022-50366}
• Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times {CVE-2022-50419}
• xsk: Fix xsk_diag use-after-free error during socket cleanup {CVE-2023-53426}
• svcrdma: bound check rq_pages index in inline path {CVE-2025-71068}
• net: hns3: add VLAN id validation before using {CVE-2025-71112}
• net: mdio: fix undefined behavior in bit shift for __mdiobus_register {CVE-2022-49907}
• capabilities: fix undefined behavior in bit shift for CAP_TO_MASK {CVE-2022-49870}
• ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS {CVE-2022-50315}
• i2c: piix4: Fix adapter not be removed in piix4_remove() {CVE-2022-49900}
• team: fix check for port enabled in team_queue_override_port_prio_changed() {CVE-2025-71091}
• staging: vme_user: Fix possible UAF in tsi148_dma_list_add {CVE-2022-50384}
• ALSA: ctxfi: Fix potential OOB access in audio mixer handling {CVE-2026-23076}
• ftrace: Add cond_resched() to ftrace_graph_set_hash() {CVE-2025-37940}
• net: stmmac: Fix accessing freed irq affinity_hint {CVE-2025-23155}
• ext4: set goal start correctly in ext4_mb_normalize_request {CVE-2023-54021}
• netfilter: ipset: fix region locking in hash types {CVE-2025-37997}
• openvswitch: Fix unsafe attribute parsing in output_userspace() {CVE-2025-37998}
• wifi: brcm80211: fmac: Add error handling for brcmf_usb_dl_writeimage() {CVE-2025-37990}
• nfs: handle failure of nfs_get_lock_context in unlock path {CVE-2025-38023}
• drm/amd/pm: Prevent division by zero {CVE-2025-37767}
• netfilter: ctnetlink: remove refcounting in expectation dumpers {CVE-2025-39764}
• tracing: Fix null pointer dereference in tracing_err_log_open() {CVE-2023-53167}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• scsi: qla2xxx: Pointer may be dereferenced {CVE-2023-53150}
• net: pktgen: fix access outside of user given buffer in pktgen_thread_write() {CVE-2025-38061}
• dm cache: prevent BUG_ON by blocking retries on failed device resumes {CVE-2025-38066} -…

• crypto: algif_aead - Fix minimum RX size check for decryption {CVE-2026-31431}
• crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl {CVE-2026-31431}
• crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec {CVE-2026-31431}
• crypto: authencesn - Fix src offset when decrypting in-place {CVE-2026-31431}
• crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption {CVE-2026-31431}
• crypto: authenc - use memcpy_sglist() instead of null skcipher {CVE-2026-31431}
• crypto: algif_aead - snapshot IV for async AEAD requests {CVE-2026-31431}
• crypto: algif_aead - Revert to operating out-of-place {CVE-2026-31431}
• crypto: algif_aead - use memcpy_sglist() instead of null skcipher {CVE-2026-31431}
• crypto: scatterwalk - Backport memcpy_sglist() {CVE-2026-31431}
• scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() {CVE-2026-23216}
• VMCI: Fix use-after-free when removing resource in vmci_resource_remove() {CVE-2024-46738}
• ptp: fix integer overflow in max_vclocks_store {CVE-2024-40994}
• xsk: Fix xsk_diag use-after-free error during socket cleanup {CVE-2023-53426}
• net: hns3: add VLAN id validation before using {CVE-2025-71112}
• scsi: qla2xxx: Fix improper freeing of purex item {CVE-2025-68741}
• tracing: Consider the NULL character when validating the event length {CVE-2024-50131}
• capabilities: fix undefined behavior in bit shift for CAP_TO_MASK {CVE-2022-49870}
• scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() {CVE-2022-50422}
• netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() {CVE-2026-23111}
• team: fix check for port enabled in team_queue_override_port_prio_changed() {CVE-2025-71091}
• i2c: piix4: Fix adapter not be removed in piix4_remove() {CVE-2022-49900}
• libceph: replace overzealous BUG_ON in osdmap_apply_incremental() {CVE-2026-22990}
• RDMA/mlx5: Initialize obj_event->obj_sub_list before xa_insert {CVE-2025-38387}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• drm/tegra: Fix a possible null pointer dereference {CVE-2025-38363}
• ACPICA: fix acpi operand cache leak in dswstate.c {CVE-2025-38345}
• ACPICA: fix acpi parse and parseext cache leaks {CVE-2025-38344}
• jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() {CVE-2025-38337}
• x86/sgx: Prevent attempts to reclaim poisoned pages {CVE-2025-38334}
• mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu(). {CVE-2025-38324}
• drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table {CVE-2025-38319}
• fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() {CVE-2025-38312}
• seg6: Fix validation of nexthop addresses {CVE-2025-38310}
• bpf: Fix WARN() in get_bpf_raw_tp_regs {CVE-2025-38285}
• atm: clip: prevent NULL deref in clip_push() {CVE-2025-38251}
• nfsd: Initialize ssc before laundromat_work to prevent NULL dereference {CVE-2025-38231}
• ext4: inline: fix len overflow in ext4_prepare_inline_data {CVE-2025-38222}
• fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var {CVE-2025-38215}
• fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var {CVE-2025-38214}
• atm: Revert atm_account_tx() if copy_from_iter_full() fails. {CVE-2025-38190}
• tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer {CVE-2025-38184}
• calipso: Fix null-ptr-deref in calipso_req_{set,del}attr(). {CVE-2025-38181}
• thunderbolt: Do not double dequeue a configuration request {CVE-2025-38174}
• bpf: fix ktls panic with sockmap {CVE-2025-38166}
• gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO {CVE-2025-38122}
• net_sched: sch_sfq: fix a potential crash on gso_skb handling {CVE-2025-38115}
• x86/iopl: Cure TIF_IO_BITMAP inconsistencies {CVE-2025-38100}
• dma-buf: insert memory barrier before updating num_fences {CVE-2025-38095}
• net_sched: prio: fix a race in prio_tune() {CVE-2025-38083} -…

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

bpf: Fix WARN() in get_bpf_raw_tp_regs

syzkaller reported an issue:

WARNING: CPU: 3 PID: 5971 at kernel/trace/bpf_trace.c:1861 get_bpf_raw_tp_regs+0xa4/0x100 kernel/trace/bpf_trace.c:1861 Modules linked in: CPU: 3 UID: 0 PID: 5971 Comm: syz-executor205 Not tainted 6.15.0-rc5-syzkaller-00038-g707df3375124 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:get_bpf_raw_tp_regs+0xa4/0x100 kernel/trace/bpf_trace.c:1861 RSP: 0018:ffffc90003636fa8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffffff81c6bc4c RDX: ffff888032efc880 RSI: ffffffff81c6bc83 RDI: 0000000000000005 RBP: ffff88806a730860 R08: 0000000000000005 R09: 0000000000000003 R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000004 R13: 0000000000000001 R14: ffffc90003637008 R15: 0000000000000900 FS: 0000000000000000(0000) GS:ffff8880d6cdf000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7baee09130 CR3: 0000000029f5a000 CR4: 0000000000352ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1934 [inline] bpf_get_stack_raw_tp+0x24/0x160 kernel/trace/bpf_trace.c:1931 bpf_prog_ec3b2eefa702d8d3+0x43/0x47 bpf_dispatcher_nop_func include/linux/bpf.h:1316 [inline] __bpf_prog_run include/linux/filter.h:718 [inline] bpf_prog_run include/linux/filter.h:725 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:2363 [inline] bpf_trace_run3+0x23f/0x5a0 kernel/trace/bpf_trace.c:2405 __bpf_trace_mmap_lock_acquire_returned+0xfc/0x140 include/trace/events/mmap_lock.h:47 __traceiter_mmap_lock_acquire_returned+0x79/0xc0 include/trace/events/mmap_lock.h:47 __do_trace_mmap_lock_acquire_returned include/trace/events/mmap_lock.h:47 [inline] trace_mmap_lock_acquire_returned include/trace/events/mmap_lock.h:47 [inline] __mmap_lock_do_trace_acquire_returned+0x138/0x1f0 mm/mmap_lock.c:35 __mmap_lock_trace_acquire_returned include/linux/mmap_lock.h:36 [inline] mmap_read_trylock include/linux/mmap_lock.h:204 [inline] stack_map_get_build_id_offset+0x535/0x6f0 kernel/bpf/stackmap.c:157 __bpf_get_stack+0x307/0xa10 kernel/bpf/stackmap.c:483 ____bpf_get_stack kernel/bpf/stackmap.c:499 [inline] bpf_get_stack+0x32/0x40 kernel/bpf/stackmap.c:496 ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1941 [inline] bpf_get_stack_raw_tp+0x124/0x160 kernel/trace/bpf_trace.c:1931 bpf_prog_ec3b2eefa702d8d3+0x43/0x47

Tracepoint like trace_mmap_lock_acquire_returned may cause nested call as the corner case show above, which will be resolved with more general method in the future. As a result, WARN_ON_ONCE will be triggered. As Alexei suggested, remove the WARN_ON_ONCE first.

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;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Android drivers;
• Bluetooth drivers;
• Bus devices;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• InfiniBand drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• NI-700 PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• SCSI subsystem;
• ASPEED SoC drivers;
• SPI subsystem;
• TCM subsystem;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB core drivers;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C Port Controller Manager driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• Virtio drivers;
• BTRFS file system;
• EROFS file system;
• F2FS file system;
• File systems infrastructure;
• Network file systems library;
• NTFS3 file system;
• SMB network file system;
• Codetag library;
• BPF subsystem;
• LZO compression library;
• Mellanox drivers;
• IPv4 networking;
• Bluetooth subsystem;
• Network sockets;
• XFRM subsystem;
• Digital Audio (PCM) driver;
• Tracing infrastructure;
• io_uring subsystem;
• Padata parallel execution mechanism;
• DVFS energy model driver;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Memory management;
• KASAN memory debugging framework;
• CAN network layer;
• Networking core;
• IPv6 networking;
• Netfilter;
• NetLabel subsystem;
• Open vSwitch;
• Network traffic control;
• TIPC protocol;
• TLS protocol;
• ALSA framework;
• sma1307 audio codecs;
• Intel ASoC drivers;
• MediaTek ASoC drivers;
• USB sound devices; (CVE-2025-38122, CVE-2025-38119, CVE-2025-38071, CVE-2025-38310, CVE-2025-38166, CVE-2025-38055, CVE-2025-38292, CVE-2025-38078, CVE-2025-38134, CVE-2025-38063, CVE-2025-38282, CVE-2025-38059, CVE-2025-38112, CVE-2025-38082, CVE-2025-38296, CVE-2025-38126, CVE-2025-38136, CVE-2025-38075, CVE-2025-38042, CVE-2025-38113, CVE-2025-38003, CVE-2025-38318, CVE-2025-38156, CVE-2025-38290, CVE-2025-38102, CVE-2025-38076, CVE-2025-38097, CVE-2025-38313, CVE-2025-38298, CVE-2025-38300, CVE-2025-38169, CVE-2025-38131, CVE-2025-38301, CVE-2025-38050, CVE-2025-38139, CVE-2025-38305, CVE-2025-38317, CVE-2025-38045, CVE-2025-38040, CVE-2025-38279, CVE-2025-38123, CVE-2025-38074, CVE-2025-38111, CVE-2025-38117, CVE-2025-38069, CVE-2025-38035, CVE-2025-38128, CVE-2025-38277, CVE-2025-38061, CVE-2025-38306, CVE-2025-38051, CVE-2025-38124, CVE-2025-38291, CVE-2025-38130, CVE-2025-38319, CVE-2025-38272, CVE-2025-38175, CVE-2025-38176, CVE-2025-38070, CVE-2025-38032, CVE-2025-38151, CVE-2025-38107, CVE-2025-38103, CVE-2025-38274, CVE-2025-38163, CVE-2025-38293, CVE-2025-38064, CVE-2025-38498, CVE-2025-38039, CVE-2025-38173, CVE-2025-38038, CVE-2025-38135, CVE-2025-38149, CVE-2025-38142, CVE-2025-38414, CVE-2025-38120, CVE-2025-38106, CVE-2025-38092, CVE-2025-38091, CVE-2025-38415, CVE-2025-38294, CVE-2025-38043, CVE-2025-38147, CVE-2025-38037, CVE-2025-38108, CVE-2025-38088, CVE-2025-38316, CVE-2025-38312, CVE-2025-38352,…

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;
• Cryptographic API;
• ACPI drivers;
• Android drivers;
• Bluetooth drivers;
• Bus devices;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• InfiniBand drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• NI-700 PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• SCSI subsystem;
• ASPEED SoC drivers;
• SPI subsystem;
• TCM subsystem;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB core drivers;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C Port Controller Manager driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• Virtio drivers;
• BTRFS file system;
• EROFS file system;
• F2FS file system;
• File systems infrastructure;
• Network file systems library;
• NTFS3 file system;
• SMB network file system;
• Codetag library;
• BPF subsystem;
• LZO compression library;
• Mellanox drivers;
• IPv4 networking;
• Bluetooth subsystem;
• Network sockets;
• XFRM subsystem;
• Digital Audio (PCM) driver;
• Tracing infrastructure;
• io_uring subsystem;
• Padata parallel execution mechanism;
• DVFS energy model driver;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Memory management;
• KASAN memory debugging framework;
• CAN network layer;
• Networking core;
• IPv6 networking;
• Netfilter;
• NetLabel subsystem;
• Open vSwitch;
• Network traffic control;
• TIPC protocol;
• TLS protocol;
• ALSA framework;
• sma1307 audio codecs;
• Intel ASoC drivers;
• MediaTek ASoC drivers;
• USB sound devices; (CVE-2025-38112, CVE-2025-38283, CVE-2025-38120, CVE-2025-38091, CVE-2025-38124, CVE-2025-38031, CVE-2025-38288, CVE-2025-38047, CVE-2025-38295, CVE-2025-38284, CVE-2025-38281, CVE-2025-38151, CVE-2025-38058, CVE-2025-38059, CVE-2025-38299, CVE-2025-38065, CVE-2025-38107, CVE-2025-38143, CVE-2025-38113, CVE-2025-38289, CVE-2025-38160, CVE-2025-38311, CVE-2025-38052, CVE-2025-38131, CVE-2025-38268, CVE-2025-38066, CVE-2025-38129, CVE-2025-38127, CVE-2025-38317, CVE-2025-38158, CVE-2025-38039, CVE-2025-38064, CVE-2025-38306, CVE-2025-38291, CVE-2025-38162, CVE-2025-38111, CVE-2025-38147, CVE-2025-38415, CVE-2025-38290, CVE-2025-38294, CVE-2025-38499, CVE-2025-38167, CVE-2025-38098, CVE-2025-38298, CVE-2025-38279, CVE-2025-38278, CVE-2025-38149, CVE-2025-38073, CVE-2025-38100, CVE-2025-38033, CVE-2025-38080, CVE-2025-38314, CVE-2025-38166, CVE-2025-38154, CVE-2025-38050, CVE-2025-38123, CVE-2025-38070, CVE-2025-38169, CVE-2025-38077, CVE-2025-38082, CVE-2025-38061, CVE-2025-38032, CVE-2025-38092, CVE-2025-38176, CVE-2025-38044, CVE-2025-38277, CVE-2025-38305, CVE-2025-38034, CVE-2025-38293, CVE-2025-38115, CVE-2025-38057, CVE-2025-38126, CVE-2025-38312, CVE-2025-38117, CVE-2025-38141, CVE-2025-38155, CVE-2025-38161, CVE-2025-38142, CVE-2025-38036, CVE-2025-38165, CVE-2025-38069, CVE-2025-38106, CVE-2025-38267, CVE-2025-38138, CVE-2025-38119, CVE-2025-38282, CVE-2025-38275, CVE-2025-38081, CVE-2025-38414,…

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;
• Cryptographic API;
• ACPI drivers;
• Android drivers;
• Bluetooth drivers;
• Bus devices;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• InfiniBand drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• NI-700 PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• SCSI subsystem;
• ASPEED SoC drivers;
• SPI subsystem;
• TCM subsystem;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB core drivers;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C Port Controller Manager driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• Virtio drivers;
• BTRFS file system;
• EROFS file system;
• F2FS file system;
• File systems infrastructure;
• Network file systems library;
• NTFS3 file system;
• SMB network file system;
• Codetag library;
• BPF subsystem;
• LZO compression library;
• Mellanox drivers;
• IPv4 networking;
• Bluetooth subsystem;
• Network sockets;
• XFRM subsystem;
• Digital Audio (PCM) driver;
• Tracing infrastructure;
• io_uring subsystem;
• Padata parallel execution mechanism;
• DVFS energy model driver;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Memory management;
• KASAN memory debugging framework;
• CAN network layer;
• Networking core;
• IPv6 networking;
• Netfilter;
• NetLabel subsystem;
• Open vSwitch;
• Network traffic control;
• TIPC protocol;
• TLS protocol;
• ALSA framework;
• sma1307 audio codecs;
• Intel ASoC drivers;
• MediaTek ASoC drivers;
• USB sound devices; (CVE-2025-38115, CVE-2025-38004, CVE-2025-38035, CVE-2025-38057, CVE-2025-38314, CVE-2025-38317, CVE-2025-38074, CVE-2025-38113, CVE-2025-38130, CVE-2025-38175, CVE-2025-38155, CVE-2025-38062, CVE-2025-38050, CVE-2025-38159, CVE-2025-38352, CVE-2025-38101, CVE-2025-38034, CVE-2025-38061, CVE-2025-38288, CVE-2025-38153, CVE-2025-38043, CVE-2025-38268, CVE-2025-38415, CVE-2025-38291, CVE-2025-38270, CVE-2025-38044, CVE-2025-38146, CVE-2025-38048, CVE-2025-38069, CVE-2025-38298, CVE-2025-38058, CVE-2025-38161, CVE-2025-38158, CVE-2025-38059, CVE-2025-38066, CVE-2025-38047, CVE-2025-38040, CVE-2025-38112, CVE-2025-38042, CVE-2025-38107, CVE-2025-38296, CVE-2025-38278, CVE-2025-39890, CVE-2025-38088, CVE-2025-38174, CVE-2025-38118, CVE-2025-38117, CVE-2025-38110, CVE-2025-38305, CVE-2025-38136, CVE-2025-38063, CVE-2025-38498, CVE-2025-38499, CVE-2025-38106, CVE-2025-38292, CVE-2025-38163, CVE-2025-38169, CVE-2025-38032, CVE-2025-38310, CVE-2025-38302, CVE-2025-38092, CVE-2025-38052, CVE-2025-38282, CVE-2025-38082, CVE-2025-38036, CVE-2025-38054, CVE-2025-38105, CVE-2025-38265, CVE-2025-38116, CVE-2025-38060, CVE-2025-38154, CVE-2025-38280, CVE-2025-38176, CVE-2025-38156, CVE-2025-38289, CVE-2025-38166, CVE-2025-38080, CVE-2025-38098, CVE-2025-38127, CVE-2025-38125, CVE-2025-38172, CVE-2025-38142, CVE-2025-38096, CVE-2025-38055, CVE-2025-38138, CVE-2025-38126, CVE-2025-38073, CVE-2025-38173, CVE-2025-38031,…

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;
• Cryptographic API;
• ACPI drivers;
• Android drivers;
• Bluetooth drivers;
• Bus devices;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• InfiniBand drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• NI-700 PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• SCSI subsystem;
• ASPEED SoC drivers;
• SPI subsystem;
• TCM subsystem;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB core drivers;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C Port Controller Manager driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• Virtio drivers;
• BTRFS file system;
• EROFS file system;
• F2FS file system;
• File systems infrastructure;
• Network file systems library;
• NTFS3 file system;
• SMB network file system;
• Codetag library;
• BPF subsystem;
• LZO compression library;
• Mellanox drivers;
• IPv4 networking;
• Bluetooth subsystem;
• Network sockets;
• XFRM subsystem;
• Digital Audio (PCM) driver;
• Tracing infrastructure;
• io_uring subsystem;
• Padata parallel execution mechanism;
• DVFS energy model driver;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Memory management;
• KASAN memory debugging framework;
• CAN network layer;
• Networking core;
• IPv6 networking;
• Netfilter;
• NetLabel subsystem;
• Open vSwitch;
• Network traffic control;
• TIPC protocol;
• TLS protocol;
• ALSA framework;
• sma1307 audio codecs;
• Intel ASoC drivers;
• MediaTek ASoC drivers;
• USB sound devices; (CVE-2025-38155, CVE-2025-38145, CVE-2025-38072, CVE-2025-38306, CVE-2025-38004, CVE-2025-38053, CVE-2025-38293, CVE-2025-38045, CVE-2025-38105, CVE-2025-38079, CVE-2025-38161, CVE-2025-38031, CVE-2025-38114, CVE-2025-38033, CVE-2025-38274, CVE-2025-38265, CVE-2025-38135, CVE-2025-38075, CVE-2025-38313, CVE-2025-38064, CVE-2025-38118, CVE-2025-38299, CVE-2025-38123, CVE-2025-38112, CVE-2025-38073, CVE-2025-38070, CVE-2025-38138, CVE-2025-38303, CVE-2025-38148, CVE-2025-38035, CVE-2025-38157, CVE-2025-38131, CVE-2025-38107, CVE-2025-38108, CVE-2025-38071, CVE-2025-38081, CVE-2025-38301, CVE-2025-38415, CVE-2025-38034, CVE-2025-38294, CVE-2025-38314, CVE-2025-38285, CVE-2025-38147, CVE-2025-38113, CVE-2025-38352, CVE-2025-38170, CVE-2025-38103, CVE-2025-38282, CVE-2025-38290, CVE-2025-38117, CVE-2025-38078, CVE-2025-38122, CVE-2025-38176, CVE-2025-38082, CVE-2025-38289, CVE-2025-38124, CVE-2025-38039, CVE-2025-38281, CVE-2025-38126, CVE-2025-38111, CVE-2025-38080, CVE-2025-38088, CVE-2025-38048, CVE-2025-38269, CVE-2025-38003, CVE-2025-38102, CVE-2025-38140, CVE-2025-38316, CVE-2025-38268, CVE-2025-38132, CVE-2025-38286, CVE-2025-38159, CVE-2025-38120, CVE-2025-38295, CVE-2025-38077, CVE-2025-38297, CVE-2025-38174, CVE-2025-38160, CVE-2025-38119, CVE-2025-38099, CVE-2025-38134, CVE-2025-38051, CVE-2025-38061, CVE-2025-38317, CVE-2025-38142, CVE-2025-38175, CVE-2025-38091, CVE-2025-38311, CVE-2025-38066,…

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;
• Cryptographic API;
• ACPI drivers;
• Android drivers;
• Bluetooth drivers;
• Bus devices;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• InfiniBand drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• NI-700 PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• SCSI subsystem;
• ASPEED SoC drivers;
• SPI subsystem;
• TCM subsystem;
• TTY drivers;
• UFS subsystem;
• USB core drivers;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C Port Controller Manager driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• Virtio drivers;
• BTRFS file system;
• EROFS file system;
• F2FS file system;
• File systems infrastructure;
• Network file systems library;
• NTFS3 file system;
• SMB network file system;
• Codetag library;
• BPF subsystem;
• LZO compression library;
• Mellanox drivers;
• IPv4 networking;
• Bluetooth subsystem;
• Network sockets;
• XFRM subsystem;
• Digital Audio (PCM) driver;
• Tracing infrastructure;
• io_uring subsystem;
• Padata parallel execution mechanism;
• DVFS energy model driver;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Memory management;
• KASAN memory debugging framework;
• CAN network layer;
• Networking core;
• IPv6 networking;
• Netfilter;
• NetLabel subsystem;
• Open vSwitch;
• Network traffic control;
• TIPC protocol;
• TLS protocol;
• ALSA framework;
• sma1307 audio codecs;
• Intel ASoC drivers;
• MediaTek ASoC drivers;
• USB sound devices; (CVE-2025-38141, CVE-2025-38039, CVE-2025-38283, CVE-2025-38272, CVE-2025-38290, CVE-2025-38168, CVE-2025-38134, CVE-2025-38158, CVE-2025-38097, CVE-2025-38078, CVE-2025-38161, CVE-2025-38116, CVE-2025-38312, CVE-2025-38067, CVE-2025-38129, CVE-2025-38119, CVE-2025-38061, CVE-2025-38352, CVE-2025-38269, CVE-2025-38163, CVE-2025-38315, CVE-2025-38301, CVE-2025-38115, CVE-2025-38032, CVE-2025-38127, CVE-2025-38029, CVE-2025-38277, CVE-2025-38075, CVE-2025-38300, CVE-2025-38059, CVE-2025-38047, CVE-2025-38118, CVE-2025-38038, CVE-2025-38278, CVE-2025-38169, CVE-2025-38074, CVE-2025-38292, CVE-2025-38295, CVE-2025-38294, CVE-2025-38154, CVE-2025-38165, CVE-2025-38069, CVE-2025-38120, CVE-2025-38098, CVE-2025-38050, CVE-2025-38068, CVE-2025-38063, CVE-2025-38034, CVE-2025-38123, CVE-2025-38092, CVE-2025-38103, CVE-2025-38170, CVE-2025-38313, CVE-2025-38062, CVE-2025-38159, CVE-2025-38147, CVE-2025-38415, CVE-2025-38045, CVE-2025-38279, CVE-2025-38302, CVE-2025-38162, CVE-2025-38414, CVE-2025-38146, CVE-2025-38035, CVE-2025-38040, CVE-2025-38073, CVE-2025-38054, CVE-2025-38099, CVE-2025-38291, CVE-2025-38126, CVE-2025-38088, CVE-2025-38310, CVE-2025-38176, CVE-2025-38102, CVE-2025-38149, CVE-2025-38124, CVE-2025-38003, CVE-2025-38140, CVE-2025-38100, CVE-2025-38081, CVE-2025-38319, CVE-2025-38142, CVE-2025-38303, CVE-2025-38155, CVE-2025-38044, CVE-2025-38316, CVE-2025-38052, CVE-2025-38317, CVE-2025-38151, CVE-2025-38164, CVE-2025-38148,…

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,…

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-38067, CVE-2025-38337, CVE-2025-38204, CVE-2025-38085, CVE-2025-38514, CVE-2025-38313, CVE-2025-38273, CVE-2025-38143, CVE-2025-38203, CVE-2025-38200, CVE-2025-38362, CVE-2025-38439, CVE-2025-38346, CVE-2025-38465, CVE-2024-57883, CVE-2025-38181, CVE-2025-38229, CVE-2025-38401, CVE-2025-38115, CVE-2025-38159, CVE-2025-38420, CVE-2025-38516, CVE-2025-38371, CVE-2025-38445, CVE-2025-38395, CVE-2025-38161, CVE-2025-38147, CVE-2025-38163, CVE-2025-38384, CVE-2025-38498, CVE-2024-26775, CVE-2025-38231, CVE-2025-38305, CVE-2025-38135, CVE-2025-38112, CVE-2025-38375, CVE-2025-38403, CVE-2025-38515, CVE-2025-38363, CVE-2025-38377, CVE-2025-38387, CVE-2025-38298, CVE-2025-38344, CVE-2025-21888, CVE-2025-38107, CVE-2025-38160, CVE-2025-38174, CVE-2025-38319, CVE-2025-38464, CVE-2025-38102, CVE-2025-38400, CVE-2025-38245, CVE-2025-38153, CVE-2025-38310, CVE-2025-38513, CVE-2025-38167, CVE-2025-38459, CVE-2025-38206, CVE-2025-38345, CVE-2025-38249, CVE-2025-38119, CVE-2025-38336, CVE-2025-38154, CVE-2025-38457, CVE-2025-38136, CVE-2025-38103, CVE-2025-38352, CVE-2025-38145, CVE-2025-38146, CVE-2025-38393, CVE-2025-38184, CVE-2025-38460, CVE-2025-38227, CVE-2025-38443, CVE-2025-38293, CVE-2025-38257, CVE-2025-38462, CVE-2025-38328, CVE-2025-38090, CVE-2025-38389, CVE-2025-38324, CVE-2025-38430, CVE-2025-37948, CVE-2025-38263, CVE-2025-38218, CVE-2025-37963, CVE-2025-38226, CVE-2025-38415, CVE-2025-38418, CVE-2025-38074, CVE-2025-38458, CVE-2025-38391, CVE-2022-48703, CVE-2025-38219, CVE-2025-38412, CVE-2025-37958, CVE-2025-38194, CVE-2025-38280, CVE-2025-38285, CVE-2025-38138, CVE-2025-38251, CVE-2025-38222, CVE-2025-38461, CVE-2025-38100, CVE-2025-38326, CVE-2025-38320, CVE-2025-38386, CVE-2025-38542, CVE-2025-38237,…

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;
• SMB network 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-38181, CVE-2025-38200, CVE-2025-38115, CVE-2025-38375, CVE-2025-38457, CVE-2025-38371, CVE-2025-38145, CVE-2025-38540, CVE-2025-38305, CVE-2025-38443, CVE-2025-38222, CVE-2025-38143, CVE-2025-38173, CVE-2025-38466, CVE-2025-38458, CVE-2025-38293, CVE-2025-38412, CVE-2025-38418, CVE-2025-38513, CVE-2025-38459, CVE-2025-38084, CVE-2022-48703, CVE-2025-38419, CVE-2025-38336, CVE-2025-37963, CVE-2025-38204, CVE-2025-38227, CVE-2025-38088, CVE-2025-38401, CVE-2025-38107, CVE-2025-38285, CVE-2025-37958, CVE-2025-38389, CVE-2025-38444, CVE-2025-38465, CVE-2025-38206, CVE-2025-38326, CVE-2025-38103, CVE-2024-44939, CVE-2025-38154, CVE-2025-38348, CVE-2025-38229, CVE-2025-38514, CVE-2025-38231, CVE-2025-38136, CVE-2024-26775, CVE-2025-38439, CVE-2025-38386, CVE-2025-38219, CVE-2025-38163, CVE-2025-38498, CVE-2025-38312, CVE-2025-38074, CVE-2025-38328, CVE-2025-38430, CVE-2025-38102, CVE-2024-57883, CVE-2025-38406, CVE-2025-38515, CVE-2025-38363, CVE-2025-38319, CVE-2025-38395, CVE-2025-38111, CVE-2025-38462, CVE-2025-38184, CVE-2025-38324, CVE-2025-38197, CVE-2025-38100, CVE-2025-38112, CVE-2025-38384, CVE-2025-38420, CVE-2025-38403, CVE-2025-38415, CVE-2025-38067, CVE-2025-38157, CVE-2025-38146, CVE-2025-38310, CVE-2025-38377, CVE-2025-38174, CVE-2025-38135, CVE-2025-38320, CVE-2025-38387, CVE-2025-21888, CVE-2025-38516, CVE-2025-38448, CVE-2025-38441, CVE-2025-38313, CVE-2025-38410, CVE-2025-38424, CVE-2025-38161, CVE-2025-38090, CVE-2025-38362, CVE-2025-38138, CVE-2025-38160, CVE-2025-38218, CVE-2025-38460, CVE-2025-38542, CVE-2025-38122, CVE-2025-38086, CVE-2025-38245, CVE-2025-38391, CVE-2025-38400, CVE-2025-38467, CVE-2025-38280, CVE-2025-38273, CVE-2025-38147, CVE-2025-38257, CVE-2025-38263,…

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;
• SMB network 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-38389, CVE-2025-38146, CVE-2025-38237, CVE-2025-38107, CVE-2025-38229, CVE-2025-38211, CVE-2025-38313, CVE-2025-21888, CVE-2025-38122, CVE-2025-38514, CVE-2025-38280, CVE-2025-38375, CVE-2025-38084, CVE-2025-38410, CVE-2025-38459, CVE-2025-38119, CVE-2025-38391, CVE-2025-38293, CVE-2025-38086, CVE-2025-38085, CVE-2025-38231, CVE-2025-38324, CVE-2025-38227, CVE-2025-38153, CVE-2025-38439, CVE-2025-38263, CVE-2025-38387, CVE-2025-38542, CVE-2025-37948, CVE-2025-38462, CVE-2025-38498, CVE-2025-38320, CVE-2025-38262, CVE-2025-38218, CVE-2025-38412, CVE-2025-38424, CVE-2025-38384, CVE-2025-38377, CVE-2025-38102, CVE-2025-38163, CVE-2024-26726, CVE-2025-38386, CVE-2025-38400, CVE-2024-57883, CVE-2025-38145, CVE-2025-38157, CVE-2025-38399, CVE-2025-38419, CVE-2025-38464, CVE-2025-38251, CVE-2025-38444, CVE-2025-38428, CVE-2024-44939, CVE-2025-37954, CVE-2024-26775, CVE-2025-38147, CVE-2025-38286, CVE-2025-38516, CVE-2025-38154, CVE-2025-38336, CVE-2025-38467, CVE-2025-38067, CVE-2025-38206, CVE-2025-38090, CVE-2025-38312, CVE-2022-48703, CVE-2025-38161, CVE-2025-38328, CVE-2025-38540, CVE-2025-38401, CVE-2025-38513, CVE-2025-37963, CVE-2025-38219, CVE-2025-38305, CVE-2025-38415, CVE-2025-38143, CVE-2025-38515, CVE-2025-38418, CVE-2025-38135, CVE-2025-38445, CVE-2025-38222, CVE-2025-38200, CVE-2025-38403, CVE-2025-38181, CVE-2025-38461, CVE-2025-38458, CVE-2025-38173, CVE-2025-38448, CVE-2025-38346, CVE-2025-38466, CVE-2025-38249, CVE-2025-38457, CVE-2025-38160, CVE-2025-38138, CVE-2025-38088, CVE-2025-38167, CVE-2025-38184, CVE-2025-38319, CVE-2025-38395, CVE-2025-38194, CVE-2025-38416, CVE-2025-38363, CVE-2025-38245, CVE-2025-38348, CVE-2025-38326, CVE-2025-38441, CVE-2025-38103, CVE-2025-37958,…

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;
• SMB network 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-38067, CVE-2025-38371, CVE-2025-38153, CVE-2025-38160, CVE-2024-57883, CVE-2025-38406, CVE-2025-38263, CVE-2025-38352, CVE-2025-38147, CVE-2025-38464, CVE-2025-38362, CVE-2025-38227, CVE-2025-38462, CVE-2025-38332, CVE-2025-38326, CVE-2025-38226, CVE-2025-38167, CVE-2025-38085, CVE-2025-38459, CVE-2025-38345, CVE-2025-38103, CVE-2025-38540, CVE-2025-38161, CVE-2025-38138, CVE-2025-38159, CVE-2024-26775, CVE-2025-38249, CVE-2025-38090, CVE-2025-38319, CVE-2025-38135, CVE-2025-38184, CVE-2025-38465, CVE-2025-38222, CVE-2025-38445, CVE-2025-38328, CVE-2025-38111, CVE-2025-38457, CVE-2025-38466, CVE-2025-38403, CVE-2025-38346, CVE-2025-38441, CVE-2025-38285, CVE-2025-38444, CVE-2025-38377, CVE-2025-38218, CVE-2025-38305, CVE-2025-38211, CVE-2025-38100, CVE-2025-38424, CVE-2025-38336, CVE-2025-38237, CVE-2025-38245, CVE-2025-38348, CVE-2025-38415, CVE-2025-37963, CVE-2025-38163, CVE-2025-38231, CVE-2025-38461, CVE-2025-38084, CVE-2025-38107, CVE-2025-38200, CVE-2025-38393, CVE-2025-38498, CVE-2025-38115, CVE-2025-38399, CVE-2025-38312, CVE-2025-37958, CVE-2025-38286, CVE-2025-38174, CVE-2025-38136, CVE-2025-38086, CVE-2025-38460, CVE-2025-38229, CVE-2025-38108, CVE-2025-38337, CVE-2025-38389, CVE-2025-38513, CVE-2025-38420, CVE-2025-38194, CVE-2025-38273, CVE-2025-38395, CVE-2025-38430, CVE-2025-38375, CVE-2025-38154, CVE-2025-38146, CVE-2025-38298, CVE-2025-38342, CVE-2025-38181, CVE-2024-44939, CVE-2025-38280, CVE-2025-38386, CVE-2025-38320, CVE-2025-38514, CVE-2025-38391, CVE-2025-38400, CVE-2025-38212, CVE-2025-38088, CVE-2025-38204, CVE-2024-26726, CVE-2025-38122, CVE-2025-38203, CVE-2025-38443, CVE-2025-38418, CVE-2025-38363, CVE-2025-38262, CVE-2025-21888, CVE-2025-38416, CVE-2025-38219,…

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-38420, CVE-2025-38173, CVE-2025-38305, CVE-2025-38312, CVE-2025-38458, CVE-2024-26726, CVE-2025-38416, CVE-2025-38363, CVE-2025-38107, CVE-2025-38174, CVE-2025-38310, CVE-2025-38406, CVE-2025-38439, CVE-2025-38245, CVE-2025-38163, CVE-2025-38111, CVE-2025-38467, CVE-2025-38515, CVE-2025-38391, CVE-2025-21888, CVE-2025-38108, CVE-2025-38395, CVE-2025-38212, CVE-2025-38153, CVE-2025-38226, CVE-2025-38375, CVE-2025-37958, CVE-2025-38444, CVE-2022-48703, CVE-2025-38280, CVE-2025-38345, CVE-2025-38384, CVE-2025-38362, CVE-2025-38326, CVE-2025-38348, CVE-2025-37752, CVE-2025-38324, CVE-2025-38298, CVE-2025-38206, CVE-2025-38219, CVE-2025-38145, CVE-2025-38200, CVE-2025-38293, CVE-2025-38461, CVE-2025-38514, CVE-2025-38389, CVE-2025-38319, CVE-2025-38344, CVE-2025-38160, CVE-2025-38159, CVE-2025-38424, CVE-2025-38412, CVE-2025-38346, CVE-2025-38466, CVE-2024-27407, CVE-2025-38211, CVE-2025-38419, CVE-2025-38227, CVE-2025-38120, CVE-2025-38143, CVE-2025-38122, CVE-2025-38197, CVE-2025-38285, CVE-2025-38273, CVE-2025-38112, CVE-2025-38403, CVE-2025-38249, CVE-2025-38448, CVE-2025-38203, CVE-2025-38085, CVE-2024-44939, CVE-2025-38119, CVE-2025-38184, CVE-2025-38443, CVE-2025-38084, CVE-2025-38194, CVE-2025-38459, CVE-2025-38231, CVE-2025-38229, CVE-2025-38418, CVE-2025-38415, CVE-2024-57883, CVE-2025-38513, CVE-2025-38460, CVE-2025-38377, CVE-2025-38147, CVE-2025-38371, CVE-2025-38428, CVE-2025-38237, CVE-2025-38542, CVE-2025-38100, CVE-2025-38251, CVE-2025-38430, CVE-2025-38336, CVE-2025-38103, CVE-2025-38342, CVE-2025-38154, CVE-2025-38540, CVE-2025-38161, CVE-2025-38399, CVE-2024-57996, CVE-2025-38350, CVE-2025-38516, CVE-2025-38262, CVE-2025-38393, CVE-2025-38204, CVE-2024-26775, CVE-2025-38464, CVE-2025-38135,…

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;
• Cryptographic API;
• ACPI drivers;
• Android drivers;
• Bluetooth drivers;
• Bus devices;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• InfiniBand drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• NI-700 PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• SCSI subsystem;
• ASPEED SoC drivers;
• SPI subsystem;
• TCM subsystem;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB core drivers;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C Port Controller Manager driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• Virtio drivers;
• BTRFS file system;
• EROFS file system;
• F2FS file system;
• File systems infrastructure;
• Network file systems library;
• NTFS3 file system;
• SMB network file system;
• Codetag library;
• BPF subsystem;
• LZO compression library;
• Mellanox drivers;
• IPv4 networking;
• Bluetooth subsystem;
• Network sockets;
• XFRM subsystem;
• Digital Audio (PCM) driver;
• Tracing infrastructure;
• io_uring subsystem;
• Padata parallel execution mechanism;
• DVFS energy model driver;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Memory management;
• KASAN memory debugging framework;
• CAN network layer;
• Networking core;
• IPv6 networking;
• Netfilter;
• NetLabel subsystem;
• Open vSwitch;
• Network traffic control;
• TIPC protocol;
• TLS protocol;
• ALSA framework;
• sma1307 audio codecs;
• Intel ASoC drivers;
• MediaTek ASoC drivers;
• USB sound devices; (CVE-2025-38137, CVE-2025-38141, CVE-2025-38035, CVE-2025-38298, CVE-2025-38042, CVE-2025-38140, CVE-2025-38138, CVE-2025-38316, CVE-2025-38304, CVE-2025-38165, CVE-2025-38306, CVE-2025-38082, CVE-2025-38132, CVE-2025-38498, CVE-2025-38158, CVE-2025-38154, CVE-2025-38064, CVE-2025-38129, CVE-2025-38096, CVE-2025-38352, CVE-2025-38303, CVE-2025-38122, CVE-2025-38048, CVE-2025-38296, CVE-2025-38149, CVE-2025-38319, CVE-2025-38078, CVE-2025-38066, CVE-2025-38099, CVE-2025-38291, CVE-2025-38267, CVE-2025-38268, CVE-2025-38126, CVE-2025-38076, CVE-2025-38077, CVE-2025-38101, CVE-2025-38071, CVE-2025-38163, CVE-2025-38285, CVE-2025-38265, CVE-2025-38125, CVE-2025-38302, CVE-2025-38172, CVE-2025-38292, CVE-2025-38279, CVE-2025-38170, CVE-2025-38062, CVE-2025-38074, CVE-2025-38050, CVE-2025-38116, CVE-2025-38414, CVE-2025-38173, CVE-2025-38033, CVE-2025-38112, CVE-2025-38091, CVE-2025-38290, CVE-2025-39890, CVE-2025-38156, CVE-2025-38289, CVE-2025-38275, CVE-2025-38295, CVE-2025-38123, CVE-2025-38300, CVE-2025-38067, CVE-2025-38131, CVE-2025-38294, CVE-2025-38105, CVE-2025-38107, CVE-2025-38106, CVE-2025-38069, CVE-2025-38041, CVE-2025-38111, CVE-2025-38312, CVE-2025-38092, CVE-2025-38054, CVE-2025-38166, CVE-2025-38044, CVE-2025-38159, CVE-2025-38061, CVE-2025-38115, CVE-2025-38058, CVE-2025-38036, CVE-2025-38100, CVE-2025-38075, CVE-2025-38160, CVE-2025-38102, CVE-2025-38269, CVE-2025-38108, CVE-2025-38119,…

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;
• Cryptographic API;
• ACPI drivers;
• Android drivers;
• Bluetooth drivers;
• Bus devices;
• Clock framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• InfiniBand drivers;
• IOMMU subsystem;
• Multiple devices driver;
• Media drivers;
• VMware VMCI Driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• NVMEM (Non Volatile Memory) drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• NI-700 PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• PTP clock framework;
• SCSI subsystem;
• ASPEED SoC drivers;
• SPI subsystem;
• TCM subsystem;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB core drivers;
• USB Gadget drivers;
• Renesas USBHS Controller drivers;
• USB Type-C Port Controller Manager driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• Virtio drivers;
• BTRFS file system;
• EROFS file system;
• F2FS file system;
• File systems infrastructure;
• Network file systems library;
• NTFS3 file system;
• SMB network file system;
• Codetag library;
• BPF subsystem;
• LZO compression library;
• Mellanox drivers;
• IPv4 networking;
• Bluetooth subsystem;
• Network sockets;
• XFRM subsystem;
• Digital Audio (PCM) driver;
• Tracing infrastructure;
• io_uring subsystem;
• Padata parallel execution mechanism;
• DVFS energy model driver;
• Restartable seuqences system call mechanism;
• Timer subsystem;
• Memory management;
• KASAN memory debugging framework;
• CAN network layer;
• Networking core;
• IPv6 networking;
• Netfilter;
• NetLabel subsystem;
• Open vSwitch;
• Network traffic control;
• TIPC protocol;
• TLS protocol;
• ALSA framework;
• sma1307 audio codecs;
• Intel ASoC drivers;
• MediaTek ASoC drivers;
• USB sound devices; (CVE-2025-38081, CVE-2025-38142, CVE-2025-38157, CVE-2025-38174, CVE-2025-38156, CVE-2025-38044, CVE-2025-38414, CVE-2025-38041, CVE-2025-38124, CVE-2025-38122, CVE-2025-38285, CVE-2025-38317, CVE-2025-38159, CVE-2025-38352, CVE-2025-38117, CVE-2025-38040, CVE-2025-38292, CVE-2025-38301, CVE-2025-38149, CVE-2025-38299, CVE-2025-38116, CVE-2025-38100, CVE-2025-38107, CVE-2025-38063, CVE-2025-38069, CVE-2025-38130, CVE-2025-38032, CVE-2025-38113, CVE-2025-38287, CVE-2025-38138, CVE-2025-38004, CVE-2025-38097, CVE-2025-38270, CVE-2025-38311, CVE-2025-38499, CVE-2025-38050, CVE-2025-38064, CVE-2025-38278, CVE-2025-38297, CVE-2025-38091, CVE-2025-38065, CVE-2025-38114, CVE-2025-38048, CVE-2025-38096, CVE-2025-38112, CVE-2025-38148, CVE-2025-38101, CVE-2025-38062, CVE-2025-38057, CVE-2025-38029, CVE-2025-38105, CVE-2025-38277, CVE-2025-38053, CVE-2025-38302, CVE-2025-38169, CVE-2025-38307, CVE-2025-38153, CVE-2025-38106, CVE-2025-38293, CVE-2025-38267, CVE-2025-38314, CVE-2025-38291, CVE-2025-38284, CVE-2025-38141, CVE-2025-38052, CVE-2025-38079, CVE-2025-38088, CVE-2025-38164, CVE-2025-38288, CVE-2025-38289, CVE-2025-38074, CVE-2025-38073, CVE-2025-38274, CVE-2025-38167, CVE-2025-38129, CVE-2025-38082, CVE-2025-38109, CVE-2025-38003, CVE-2025-38042, CVE-2025-38319, CVE-2025-38165, CVE-2025-38102, CVE-2025-38045, CVE-2025-38154, CVE-2025-38127, CVE-2025-38034, CVE-2025-38051, CVE-2025-38143, CVE-2025-38061,…

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system;…

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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:

• ARM32 architecture;
• ARM64 architecture;
• MIPS architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• HW tracing;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• Amlogic Meson DDR PMU;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• Powercap sysfs driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• SPI subsystem;
• small TFT LCD display modules;
• Media staging drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• Cadence USB3 driver;
• ChipIdea USB driver;
• USB Device Class drivers;
• USB core drivers;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Type-C support driver;
• USB Type-C Connector System Software Interface driver;
• VFIO drivers;
• Virtio Host (VHOST) subsystem;
• Backlight driver;
• Framebuffer layer;
• TSM Common Guest driver;
• Virtio drivers;
• Xen hypervisor drivers;
• File systems infrastructure;
• BTRFS file system;
• Ceph distributed file system;
• EFI Variable file system;
• Ext4 file system;
• F2FS file system;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system; …