CVE-2024-56717

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

net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic()

Packets injected by the CPU should have a SRC_PORT field equal to the CPU port module index in the Analyzer block (ocelot->num_phys_ports).

The blamed commit copied the ocelot_ifh_set_basic() call incorrectly from ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling with "x", it calls with BIT_ULL(x), but the field is not a port mask, but rather a single port index.

[ side note: this is the technical debt of code duplication :( ]

The error used to be silent and doesn't appear to have other user-visible manifestations, but with new changes in the packing library, it now fails loudly as follows:

------------[ cut here ]------------ Cannot store 0x40 inside bits 46-43 - will truncate sja1105 spi2.0: xmit timed out WARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198 sja1105 spi2.0: timed out polling for tstamp CPU: 1 UID: 0 PID: 102 Comm: felix_xmit Tainted: G W N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605 Call trace: __pack+0x90/0x198 (P) __pack+0x90/0x198 (L) packing+0x78/0x98 ocelot_ifh_set_basic+0x260/0x368 ocelot_port_inject_frame+0xa8/0x250 felix_port_deferred_xmit+0x14c/0x258 kthread_worker_fn+0x134/0x350 kthread+0x114/0x138

The code path pertains to the ocelot switchdev driver and to the felix secondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q.

The messenger (packing) is not really to blame, so fix the original commit instead.

In the Linux kernel, the following vulnerability has been resolved: net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic() Packets injected by the CPU should have a SRC_PORT field equal to the CPU port module index in the Analyzer block (ocelot->num_phys_ports). The blamed commit copied the ocelot_ifh_set_basic() call incorrectly from ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling with "x", it calls with BIT_ULL(x), but the field is not a port mask, but rather a single port index. [ side note: this is the technical debt of code duplication :( ] The error used to be silent and doesn't appear to have other user-visible manifestations, but with new changes in the packing library, it now fails loudly as follows: ------------[ cut here ]------------ Cannot store 0x40 inside bits 46-43 - will truncate sja1105 spi2.0: xmit timed out WARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198 sja1105 spi2.0: timed out polling for tstamp CPU: 1 UID: 0 PID: 102 Comm: felix_xmit Tainted: G W N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605 Call trace: __pack+0x90/0x198 (P) __pack+0x90/0x198 (L) packing+0x78/0x98 ocelot_ifh_set_basic+0x260/0x368 ocelot_port_inject_frame+0xa8/0x250 felix_port_deferred_xmit+0x14c/0x258 kthread_worker_fn+0x134/0x350 kthread+0x114/0x138 The code path pertains to the ocelot switchdev driver and to the felix secondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q. The messenger (packing) is not really to blame, so fix the original commit instead.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

bpf: Prevent tailcall infinite loop caused by freplace

There is a potential infinite loop issue that can occur when using a combination of tail calls and freplace.

In an upcoming selftest, the attach target for entry_freplace of tailcall_freplace.c is subprog_tc of tc_bpf2bpf.c, while the tail call in entry_freplace leads to entry_tc. This results in an infinite loop:

entry_tc -> subprog_tc -> entry_freplace --tailcall-> entry_tc.

The problem arises because the tail_call_cnt in entry_freplace resets to zero each time entry_freplace is executed, causing the tail call mechanism to never terminate, eventually leading to a kernel panic.

To fix this issue, the solution is twofold:

1. Prevent updating a program extended by an freplace program to a prog_array map.
2. Prevent extending a program that is already part of a prog_array map with an freplace program.

This ensures that:

• If a program or its subprogram has been extended by an freplace program, it can no longer be updated to a prog_array map.
• If a program has been added to a prog_array map, neither it nor its subprograms can be extended by an freplace program.

Moreover, an extension program should not be tailcalled. As such, return -EINVAL if the program has a type of BPF_PROG_TYPE_EXT when adding it to a prog_array map.

Additionally, fix a minor code style issue by replacing eight spaces with a tab for proper formatting.(CVE-2024-47794)

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

mm/thp: fix deferred split unqueue naming and locking

Recent changes are putting more pressure on THP deferred split queues: under load revealing long-standing races, causing list_del corruptions, "Bad page state"s and worse (I keep BUGs in both of those, so usually don't get to see how badly they end up without). The relevant recent changes being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP splitting.

Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()).

Just omit the folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer has any callers (and will be deleted separately).

Swapout: mem_cgroup_swapout() has been resetting folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling folio_unqueue_deferred_split() before resetting memcg_data.

That goes back to 5.4 commit 87eaceb3faa5 ("mm: thp: make deferred split shrinker memcg aware"): which included a check on swapcache before adding to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 ("mm: split underused THPs") avoids splitting underused THPs in reclaim, which makes swapcache THPs…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

bpf: Prevent tailcall infinite loop caused by freplace

There is a potential infinite loop issue that can occur when using a combination of tail calls and freplace.

In an upcoming selftest, the attach target for entry_freplace of tailcall_freplace.c is subprog_tc of tc_bpf2bpf.c, while the tail call in entry_freplace leads to entry_tc. This results in an infinite loop:

entry_tc -> subprog_tc -> entry_freplace --tailcall-> entry_tc.

The problem arises because the tail_call_cnt in entry_freplace resets to zero each time entry_freplace is executed, causing the tail call mechanism to never terminate, eventually leading to a kernel panic.

To fix this issue, the solution is twofold:

1. Prevent updating a program extended by an freplace program to a prog_array map.
2. Prevent extending a program that is already part of a prog_array map with an freplace program.

This ensures that:

• If a program or its subprogram has been extended by an freplace program, it can no longer be updated to a prog_array map.
• If a program has been added to a prog_array map, neither it nor its subprograms can be extended by an freplace program.

Moreover, an extension program should not be tailcalled. As such, return -EINVAL if the program has a type of BPF_PROG_TYPE_EXT when adding it to a prog_array map.

Additionally, fix a minor code style issue by replacing eight spaces with a tab for proper formatting.(CVE-2024-47794)

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

mm/thp: fix deferred split unqueue naming and locking

Recent changes are putting more pressure on THP deferred split queues: under load revealing long-standing races, causing list_del corruptions, "Bad page state"s and worse (I keep BUGs in both of those, so usually don't get to see how badly they end up without). The relevant recent changes being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP splitting.

Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()).

Just omit the folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer has any callers (and will be deleted separately).

Swapout: mem_cgroup_swapout() has been resetting folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling folio_unqueue_deferred_split() before resetting memcg_data.

That goes back to 5.4 commit 87eaceb3faa5 ("mm: thp: make deferred split shrinker memcg aware"): which included a check on swapcache before adding to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 ("mm: split underused THPs") avoids splitting underused THPs in reclaim, which makes swapcache THPs…

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

In the Linux kernel, the following vulnerability has been resolved: net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic() Packets injected by the CPU should have a SRC_PORT field equal to the CPU port module index in the Analyzer block (ocelot->num_phys_ports). The blamed commit copied the ocelot_ifh_set_basic() call incorrectly from ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling with "x", it calls with BIT_ULL(x), but the field is not a port mask, but rather a single port index. [ side note: this is the technical debt of code duplication :( ] The error used to be silent and doesn't appear to have other user-visible manifestations, but with new changes in the packing library, it now fails loudly as follows: ------------[ cut here ]------------ Cannot store 0x40 inside bits 46-43 - will truncate sja1105 spi2.0: xmit timed out WARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198 sja1105 spi2.0: timed out polling for tstamp CPU: 1 UID: 0 PID: 102 Comm: felix_xmit Tainted: G W N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605 Call trace: __pack+0x90/0x198 (P) __pack+0x90/0x198 (L) packing+0x78/0x98 ocelot_ifh_set_basic+0x260/0x368 ocelot_port_inject_frame+0xa8/0x250 felix_port_deferred_xmit+0x14c/0x258 kthread_worker_fn+0x134/0x350 kthread+0x114/0x138 The code path pertains to the ocelot switchdev driver and to the felix secondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q. The messenger (packing) is not really to blame, so fix the original commit instead.

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

Vanilla upstream kernel version 6.6.74 fixes bugs and vulnerabilities. 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;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• Bluetooth drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVME drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• SPI subsystem;
• UFS subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• File systems infrastructure;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Diskquota system;
• SMB network file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• KASAN memory debugging framework;
• Memory management;
• StackDepot library;
• Bluetooth subsystem;
• LAPB network protocol;
• Netfilter;
• io_uring subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• KCSAN framework;
• Scheduler infrastructure;
• Seccomp subsystem;
• Tracing infrastructure;
• Workqueue subsystem;
• KUnit library;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• TIPC protocol;
• Wireless networking;
• eXpress Data Path;
• SELinux security module;
• ALSA framework;
• Intel ASoC drivers;
• SOF drivers; (CVE-2024-57921, CVE-2024-56614, CVE-2024-56558, CVE-2024-56589, CVE-2024-56662, CVE-2024-56610, CVE-2024-56717, CVE-2024-57890, CVE-2024-55639, CVE-2024-56562, CVE-2025-21633, CVE-2024-56598, CVE-2024-47794, CVE-2024-41935, CVE-2024-57901, CVE-2024-56587, CVE-2024-56581, CVE-2024-56783, CVE-2024-57888, CVE-2024-57809, CVE-2024-57926, CVE-2025-21650, CVE-2024-56634, CVE-2025-21639, CVE-2025-21656, CVE-2024-56578, CVE-2025-21632, CVE-2024-56784, CVE-2025-21644, CVE-2024-56776, CVE-2024-56764, CVE-2024-56652, CVE-2024-56550, CVE-2024-56569, CVE-2024-57904, CVE-2024-49569, CVE-2024-56770, CVE-2024-56606, CVE-2024-57806, CVE-2024-56646, CVE-2024-57895, CVE-2024-57880, CVE-2024-56650, CVE-2024-56591, CVE-2024-56590, CVE-2024-56642, CVE-2024-56713, CVE-2025-21663, CVE-2024-57938, CVE-2024-56760, CVE-2024-56583, CVE-2025-21662, CVE-2024-56629, CVE-2024-47408, CVE-2024-57850, CVE-2024-56777, CVE-2024-56626, CVE-2024-56773, CVE-2024-56647, CVE-2025-21664, CVE-2024-56564, CVE-2024-56597, CVE-2024-56623, CVE-2024-57897, CVE-2024-56670, CVE-2024-56567, CVE-2024-57931, CVE-2024-56761, CVE-2024-57935, CVE-2024-53690, CVE-2025-21640, CVE-2024-56608, CVE-2024-57878, CVE-2025-21648, CVE-2024-57898, CVE-2024-57889, CVE-2024-56644, CVE-2024-56763, CVE-2024-57900,…

Attila Szász discovered that the HFS+ file system implementation in the Linux Kernel contained a heap overflow vulnerability. An attacker could use a specially crafted file system image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2025-0927)

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;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• Bluetooth drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVME drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• SPI subsystem;
• UFS subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• File systems infrastructure;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Diskquota system;
• SMB network file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• KASAN memory debugging framework;
• Memory management;
• StackDepot library;
• Bluetooth subsystem;
• LAPB network protocol;
• Network namespace;
• Netfilter;
• io_uring subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• KCSAN framework;
• Scheduler infrastructure;
• Seccomp subsystem;
• Tracing infrastructure;
• Workqueue subsystem;
• KUnit library;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• TIPC protocol;
• Wireless networking;
• eXpress Data Path;
• SELinux security module;
• ALSA framework;
• Intel ASoC drivers;
• SOF drivers; (CVE-2024-56712, CVE-2024-56761, CVE-2025-21661, CVE-2024-56565, CVE-2024-57804, CVE-2024-57887, CVE-2025-21642, CVE-2024-56779, CVE-2025-21656, CVE-2024-57890, CVE-2024-36476, CVE-2024-57843, CVE-2024-56594, CVE-2024-41932, CVE-2025-21653, CVE-2024-56567, CVE-2024-56665, CVE-2024-54191, CVE-2024-57893, CVE-2024-57932, CVE-2024-56656, CVE-2024-57945, CVE-2024-57931, CVE-2024-56599, CVE-2024-57897, CVE-2024-57903, CVE-2024-57918, CVE-2024-57795, CVE-2024-56662, CVE-2025-21639, CVE-2024-55881, CVE-2024-57889, CVE-2024-57884, CVE-2024-57934, CVE-2024-39282, CVE-2024-56718, CVE-2024-56644, CVE-2024-56760, CVE-2024-43098, CVE-2024-47143, CVE-2024-55642, CVE-2024-56634, CVE-2024-56564, CVE-2024-56768, CVE-2024-56649, CVE-2024-57919, CVE-2024-56620, CVE-2024-56625, CVE-2024-56655, CVE-2024-56772, CVE-2025-21637, CVE-2024-56617, CVE-2024-57879, CVE-2024-56715, CVE-2024-56550, CVE-2024-50051, CVE-2024-56673, CVE-2024-51729, CVE-2025-21664,…

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;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• Bluetooth drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NVME drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• SPI subsystem;
• UFS subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• File systems infrastructure;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Diskquota system;
• SMB network file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• KASAN memory debugging framework;
• Memory management;
• StackDepot library;
• Bluetooth subsystem;
• LAPB network protocol;
• Netfilter;
• io_uring subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• KCSAN framework;
• Scheduler infrastructure;
• Seccomp subsystem;
• Tracing infrastructure;
• Workqueue subsystem;
• KUnit library;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• TIPC protocol;
• Wireless networking;
• eXpress Data Path;
• SELinux security module;
• ALSA framework;
• Intel ASoC drivers;
• SOF drivers; (CVE-2024-47794, CVE-2025-21653, CVE-2024-55642, CVE-2024-56580, CVE-2024-36476, CVE-2024-56623, CVE-2024-56773, CVE-2024-48873, CVE-2024-47141, CVE-2024-57910, CVE-2024-56759, CVE-2024-54460, CVE-2024-57839, CVE-2024-56625, CVE-2024-55916, CVE-2025-21664, CVE-2025-21652, CVE-2024-56624, CVE-2024-56574, CVE-2024-50051, CVE-2025-21655, CVE-2024-56578, CVE-2024-56782, CVE-2024-57939, CVE-2024-57935, CVE-2024-56647, CVE-2024-57905, CVE-2024-57921, CVE-2024-56660, CVE-2025-21650, CVE-2025-21631, CVE-2024-56642, CVE-2024-56552, CVE-2024-57934, CVE-2024-56621, CVE-2024-57881, CVE-2024-41932, CVE-2024-56770, CVE-2024-57897, CVE-2024-56785, CVE-2024-56664, CVE-2024-57945, CVE-2024-57938, CVE-2024-56636, CVE-2024-56572, CVE-2024-43098, CVE-2024-56760, CVE-2024-57916, CVE-2024-56714, CVE-2025-21660, CVE-2024-57906, CVE-2025-21638, CVE-2024-53687, CVE-2024-56652, CVE-2024-51729, CVE-2024-49571, CVE-2024-57883, CVE-2024-54191, CVE-2024-56712, CVE-2024-49568, CVE-2024-57932, CVE-2024-57893, CVE-2024-56645, CVE-2024-56719, CVE-2024-56641, CVE-2024-57802, CVE-2024-56775, CVE-2024-56627, CVE-2024-56638, CVE-2024-57929, CVE-2024-56615, CVE-2024-56566, CVE-2024-56620, CVE-2024-56577, CVE-2025-21656, CVE-2024-57887, CVE-2024-52319, CVE-2024-56657, CVE-2024-57872,…

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2024-56372, CVE-2025-21639, CVE-2024-57897, CVE-2024-56770, CVE-2024-57898, CVE-2025-21655, CVE-2024-56667, CVE-2024-41013, CVE-2024-57888, CVE-2025-21658, CVE-2024-57911, CVE-2024-56654, CVE-2024-57904, CVE-2024-56664, CVE-2024-57806, CVE-2024-56758, CVE-2024-57912, CVE-2025-21649, CVE-2024-56369, CVE-2025-21656, CVE-2025-21643, CVE-2024-57884, CVE-2025-21640, CVE-2024-56769, CVE-2024-57939, CVE-2025-21635, CVE-2024-57902, CVE-2024-36476, CVE-2025-21646, CVE-2024-57887, CVE-2024-57882, CVE-2024-57792, CVE-2024-56759, CVE-2024-57901, CVE-2024-56764, CVE-2025-21654, CVE-2024-57899, CVE-2025-21664, CVE-2024-56715, CVE-2024-56760, CVE-2024-57926, CVE-2024-57938, CVE-2025-21637, CVE-2024-55881, CVE-2024-57916, CVE-2024-57908, CVE-2024-57910, CVE-2024-57892, CVE-2024-57890, CVE-2024-56662, CVE-2024-57793, CVE-2024-47408, CVE-2024-49568, CVE-2024-57946, CVE-2024-53690, CVE-2024-56716, CVE-2024-57801, CVE-2024-56670, CVE-2024-56709, CVE-2024-57885, CVE-2024-57791, CVE-2024-38608, CVE-2024-56763, CVE-2024-57906, CVE-2024-47736, CVE-2024-56761, CVE-2024-56659, CVE-2025-21636, CVE-2024-57913, CVE-2024-56710, CVE-2025-21660, CVE-2024-57945, CVE-2024-39282, CVE-2024-53687, CVE-2024-57907, CVE-2024-53179, CVE-2025-21659, CVE-2024-57805, CVE-2024-57889, CVE-2024-57940, CVE-2025-21645, CVE-2024-56660, CVE-2024-56718, CVE-2024-57802, CVE-2024-56767, CVE-2024-56717, CVE-2024-58087, CVE-2025-21647, CVE-2025-21650, CVE-2024-57895, CVE-2025-21632, CVE-2024-54193, CVE-2024-57893, CVE-2025-21652, CVE-2025-21634, CVE-2024-56652, CVE-2024-57929, CVE-2024-57804, CVE-2024-57925, CVE-2024-57932, CVE-2024-54683, CVE-2025-21663, CVE-2024-56665, CVE-2024-54455, CVE-2025-21642, CVE-2024-57931, CVE-2025-21971, CVE-2024-56656, CVE-2025-21651, CVE-2024-49571, CVE-2025-21631, CVE-2024-56675, CVE-2024-53125, CVE-2025-21938, CVE-2024-57879, CVE-2024-56657, CVE-2024-57807, CVE-2024-57841, CVE-2024-57903, CVE-2024-53685, CVE-2024-57896, CVE-2024-57900, CVE-2024-57883, CVE-2024-58237, CVE-2025-21638, CVE-2024-55639, CVE-2025-21653, CVE-2025-21648, CVE-2024-54460, CVE-2024-57933, CVE-2024-55916, CVE-2024-57917, CVE-2025-21662)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2024-56372, CVE-2025-21639, CVE-2024-57897, CVE-2024-56770, CVE-2024-57898, CVE-2025-21655, CVE-2024-56667, CVE-2024-41013, CVE-2024-57888, CVE-2025-21658, CVE-2024-57911, CVE-2024-56654, CVE-2024-57904, CVE-2024-56664, CVE-2024-57806, CVE-2024-56758, CVE-2024-57912, CVE-2025-21649, CVE-2024-56369, CVE-2025-21656, CVE-2025-21643, CVE-2024-57884, CVE-2025-21640, CVE-2024-56769, CVE-2024-57939, CVE-2025-21635, CVE-2024-57902, CVE-2024-36476, CVE-2025-21646, CVE-2024-57887, CVE-2024-57882, CVE-2024-57792, CVE-2024-56759, CVE-2024-57901, CVE-2024-56764, CVE-2025-21654, CVE-2024-57899, CVE-2025-21664, CVE-2024-56715, CVE-2024-56760, CVE-2024-57926, CVE-2024-57938, CVE-2025-21637, CVE-2024-55881, CVE-2024-57916, CVE-2024-57908, CVE-2024-57910, CVE-2024-57892, CVE-2024-57890, CVE-2024-56662, CVE-2024-57793, CVE-2024-47408, CVE-2024-49568, CVE-2024-57946, CVE-2024-53690, CVE-2024-56716, CVE-2024-57801, CVE-2024-56670, CVE-2024-56709, CVE-2024-57885, CVE-2024-57791, CVE-2024-38608, CVE-2024-56763, CVE-2024-57906, CVE-2024-47736, CVE-2024-56761, CVE-2024-56659, CVE-2025-21636, CVE-2024-57913, CVE-2024-56710, CVE-2025-21660, CVE-2024-57945, CVE-2024-39282, CVE-2024-53687, CVE-2024-57907, CVE-2024-53179, CVE-2025-21659, CVE-2024-57805, CVE-2024-57889, CVE-2024-57940, CVE-2025-21645, CVE-2024-56660, CVE-2024-56718, CVE-2024-57802, CVE-2024-56767, CVE-2024-56717, CVE-2024-58087, CVE-2025-21647, CVE-2025-21650, CVE-2024-57895, CVE-2025-21632, CVE-2024-54193, CVE-2024-57893, CVE-2025-21652, CVE-2025-21634, CVE-2024-56652, CVE-2024-57929, CVE-2024-57804, CVE-2024-57925, CVE-2024-57932, CVE-2024-54683, CVE-2025-21663, CVE-2024-56665, CVE-2024-54455, CVE-2025-21642, CVE-2024-57931, CVE-2025-21971, CVE-2024-56656, CVE-2025-21651, CVE-2024-49571, CVE-2025-21631, CVE-2024-56675, CVE-2024-53125, CVE-2025-21938, CVE-2024-57879, CVE-2024-56657, CVE-2024-57807, CVE-2024-57841, CVE-2024-57903, CVE-2024-53685, CVE-2024-57896, CVE-2024-57900, CVE-2024-57883, CVE-2024-58237, CVE-2025-21638, CVE-2024-55639, CVE-2025-21653, CVE-2025-21648, CVE-2024-54460, CVE-2024-57933, CVE-2024-55916, CVE-2024-57917, CVE-2025-21662)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2025-21648, CVE-2025-21645, CVE-2024-56767, CVE-2025-21664, CVE-2025-21636, CVE-2024-57898, CVE-2024-56667, CVE-2024-57912, CVE-2024-47408, CVE-2024-56761, CVE-2024-56665, CVE-2024-57887, CVE-2024-54683, CVE-2024-56662, CVE-2024-57910, CVE-2024-38608, CVE-2024-56710, CVE-2025-21656, CVE-2024-57885, CVE-2024-53125, CVE-2024-56675, CVE-2024-57895, CVE-2024-56660, CVE-2025-21638, CVE-2024-57932, CVE-2024-57807, CVE-2024-56759, CVE-2024-57883, CVE-2025-21643, CVE-2024-54193, CVE-2024-57879, CVE-2024-54460, CVE-2024-41013, CVE-2024-56654, CVE-2024-55916, CVE-2024-57897, CVE-2024-58087, CVE-2024-57904, CVE-2024-57893, CVE-2025-21652, CVE-2024-57925, CVE-2024-47736, CVE-2024-57802, CVE-2024-49571, CVE-2024-57916, CVE-2024-57801, CVE-2025-21647, CVE-2024-56763, CVE-2024-57903, CVE-2024-57899, CVE-2024-57908, CVE-2024-57900, CVE-2024-57911, CVE-2024-57902, CVE-2024-57938, CVE-2024-56760, CVE-2025-21642, CVE-2025-21971, CVE-2024-57933, CVE-2024-57917, CVE-2024-53179, CVE-2024-57896, CVE-2024-57906, CVE-2024-56716, CVE-2024-39282, CVE-2024-57806, CVE-2025-21938, CVE-2024-55881, CVE-2024-57931, CVE-2024-56717, CVE-2024-56369, CVE-2025-21640, CVE-2024-57888, CVE-2024-57804, CVE-2024-57907, CVE-2024-53687, CVE-2024-57940, CVE-2024-57929, CVE-2025-21637, CVE-2024-57805, CVE-2024-56372, CVE-2025-21646, CVE-2024-57913, CVE-2024-57901, CVE-2024-57889, CVE-2024-56770, CVE-2024-57945, CVE-2024-56659, CVE-2024-57946, CVE-2024-57890, CVE-2024-36476, CVE-2024-57882, CVE-2024-53685, CVE-2024-57791, CVE-2024-55639, CVE-2024-56718, CVE-2024-57792, CVE-2025-21662, CVE-2024-57793, CVE-2024-54455, CVE-2025-21632, CVE-2024-56715, CVE-2024-56652, CVE-2024-57939, CVE-2024-56657, CVE-2025-21658, CVE-2025-21655, CVE-2025-21635, CVE-2024-56656, CVE-2025-21660, CVE-2025-21634, CVE-2025-21631, CVE-2024-57892, CVE-2024-57884, CVE-2024-58237, CVE-2025-21659, CVE-2024-57926, CVE-2024-53690, CVE-2025-21654, CVE-2024-57841, CVE-2025-21639, CVE-2025-21663, CVE-2024-56670, CVE-2024-56758, CVE-2024-56764, CVE-2024-56709, CVE-2024-49568, CVE-2024-56769, CVE-2025-21653, CVE-2025-21651, CVE-2025-21650, CVE-2024-56664, CVE-2025-21649)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2024-57895, CVE-2024-57801, CVE-2025-21653, CVE-2025-21664, CVE-2024-57911, CVE-2024-57890, CVE-2024-56372, CVE-2024-57931, CVE-2024-57841, CVE-2024-56758, CVE-2024-57946, CVE-2024-54460, CVE-2024-55639, CVE-2025-21636, CVE-2025-21656, CVE-2024-57917, CVE-2024-53685, CVE-2024-55881, CVE-2024-57910, CVE-2024-56369, CVE-2024-57929, CVE-2024-57940, CVE-2024-54455, CVE-2025-21631, CVE-2024-56656, CVE-2025-21643, CVE-2024-57807, CVE-2024-47736, CVE-2024-56670, CVE-2025-21660, CVE-2024-56667, CVE-2024-41013, CVE-2024-56710, CVE-2025-21659, CVE-2024-57792, CVE-2024-57893, CVE-2024-57913, CVE-2024-57897, CVE-2024-57907, CVE-2024-57916, CVE-2025-21647, CVE-2024-56665, CVE-2025-21649, CVE-2024-57938, CVE-2024-56709, CVE-2024-57945, CVE-2025-21654, CVE-2024-56657, CVE-2024-49571, CVE-2024-54683, CVE-2024-56664, CVE-2024-58087, CVE-2024-54193, CVE-2024-57802, CVE-2025-21637, CVE-2024-56761, CVE-2024-57892, CVE-2024-56675, CVE-2025-21645, CVE-2024-57908, CVE-2024-58237, CVE-2024-57887, CVE-2024-53687, CVE-2025-21650, CVE-2024-57888, CVE-2024-57902, CVE-2024-57906, CVE-2024-56764, CVE-2024-57882, CVE-2024-56652, CVE-2025-21652, CVE-2025-21662, CVE-2024-57879, CVE-2024-56662, CVE-2024-56660, CVE-2025-21632, CVE-2024-47408, CVE-2025-21642, CVE-2025-21655, CVE-2025-21640, CVE-2025-21663, CVE-2024-57933, CVE-2024-57899, CVE-2024-57884, CVE-2024-56654, CVE-2024-57806, CVE-2024-57901, CVE-2024-57926, CVE-2024-39282, CVE-2024-56770, CVE-2024-57889, CVE-2024-56769, CVE-2024-53690, CVE-2024-57904, CVE-2025-21971, CVE-2024-57885, CVE-2024-56718, CVE-2024-56767, CVE-2024-38608, CVE-2024-56760, CVE-2024-56763, CVE-2024-57912, CVE-2024-36476, CVE-2024-57793, CVE-2025-21638, CVE-2024-56716, CVE-2024-57804, CVE-2024-57932, CVE-2024-57900, CVE-2025-21651, CVE-2024-57925, CVE-2024-53125, CVE-2024-56717, CVE-2025-21938, CVE-2025-21639, CVE-2024-57883, CVE-2024-56715, CVE-2024-57805, CVE-2024-55916, CVE-2024-53179, CVE-2024-56759, CVE-2024-57939, CVE-2025-21646, CVE-2024-57898, CVE-2024-57791, CVE-2025-21634, CVE-2025-21635, CVE-2024-56659, CVE-2024-57903, CVE-2025-21648, CVE-2024-57896, CVE-2024-49568, CVE-2025-21658)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2024-57913, CVE-2024-47408, CVE-2024-57884, CVE-2024-57801, CVE-2025-21664, CVE-2024-57912, CVE-2025-21634, CVE-2024-53125, CVE-2024-57900, CVE-2024-57911, CVE-2024-56716, CVE-2024-56715, CVE-2024-57892, CVE-2025-21640, CVE-2025-21646, CVE-2024-57889, CVE-2024-56758, CVE-2024-56767, CVE-2024-57926, CVE-2024-56670, CVE-2024-57940, CVE-2024-56717, CVE-2024-56759, CVE-2024-57887, CVE-2025-21654, CVE-2024-57938, CVE-2024-57841, CVE-2024-39282, CVE-2024-56761, CVE-2025-21649, CVE-2024-56652, CVE-2024-56665, CVE-2024-57896, CVE-2024-56667, CVE-2024-57902, CVE-2024-54455, CVE-2025-21656, CVE-2024-56709, CVE-2025-21635, CVE-2024-57792, CVE-2025-21642, CVE-2025-21660, CVE-2024-53690, CVE-2024-57904, CVE-2024-53685, CVE-2025-21938, CVE-2024-55881, CVE-2024-57793, CVE-2024-56659, CVE-2025-21632, CVE-2024-56656, CVE-2025-21636, CVE-2024-47736, CVE-2024-57899, CVE-2024-57916, CVE-2024-56664, CVE-2025-21971, CVE-2025-21659, CVE-2024-57910, CVE-2024-57802, CVE-2024-57806, CVE-2025-21655, CVE-2024-54193, CVE-2024-57885, CVE-2025-21658, CVE-2024-57945, CVE-2025-21650, CVE-2024-58237, CVE-2024-57804, CVE-2024-57888, CVE-2025-21637, CVE-2024-57882, CVE-2024-57883, CVE-2024-56675, CVE-2025-21663, CVE-2024-49568, CVE-2024-58087, CVE-2024-56764, CVE-2024-57903, CVE-2024-57917, CVE-2024-57893, CVE-2025-21648, CVE-2025-21631, CVE-2024-57890, CVE-2024-56718, CVE-2025-21638, CVE-2024-56372, CVE-2024-49571, CVE-2025-21662, CVE-2024-56770, CVE-2024-57807, CVE-2024-57925, CVE-2024-57898, CVE-2025-21653, CVE-2024-57895, CVE-2024-56657, CVE-2024-54683, CVE-2024-56769, CVE-2024-38608, CVE-2024-57931, CVE-2025-21652, CVE-2024-57908, CVE-2024-56760, CVE-2024-57929, CVE-2024-36476, CVE-2024-55639, CVE-2025-21645, CVE-2024-57907, CVE-2024-54460, CVE-2025-21643, CVE-2024-56660, CVE-2024-53687, CVE-2025-21639, CVE-2024-57932, CVE-2024-56654, CVE-2024-57805, CVE-2024-56662, CVE-2025-21647, CVE-2024-56710, CVE-2024-57901, CVE-2024-56369, CVE-2024-57897, CVE-2024-57939, CVE-2024-57791, CVE-2024-57879, CVE-2024-57946, CVE-2024-55916, CVE-2024-41013, CVE-2025-21651, CVE-2024-53179, CVE-2024-57933, CVE-2024-56763, CVE-2024-57906)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2024-57901, CVE-2024-57889, CVE-2024-53687, CVE-2024-57804, CVE-2024-56709, CVE-2025-21631, CVE-2024-57908, CVE-2025-21645, CVE-2024-47736, CVE-2024-57896, CVE-2024-38608, CVE-2025-21637, CVE-2024-57898, CVE-2024-53179, CVE-2024-56710, CVE-2024-57802, CVE-2025-21659, CVE-2024-57903, CVE-2024-56764, CVE-2024-57892, CVE-2024-56717, CVE-2024-57938, CVE-2024-55881, CVE-2024-56718, CVE-2025-21647, CVE-2024-39282, CVE-2024-57879, CVE-2025-21643, CVE-2024-57792, CVE-2024-56657, CVE-2024-53685, CVE-2024-54455, CVE-2024-56656, CVE-2025-21638, CVE-2024-57907, CVE-2024-54193, CVE-2024-57806, CVE-2025-21655, CVE-2024-56670, CVE-2024-57904, CVE-2024-56369, CVE-2024-57945, CVE-2024-56759, CVE-2024-56716, CVE-2025-21651, CVE-2024-57911, CVE-2024-56372, CVE-2024-36476, CVE-2024-57888, CVE-2024-41013, CVE-2024-57882, CVE-2025-21636, CVE-2025-21971, CVE-2024-57841, CVE-2024-56760, CVE-2024-57805, CVE-2024-56758, CVE-2025-21648, CVE-2024-57917, CVE-2024-57913, CVE-2025-21658, CVE-2024-57926, CVE-2024-57939, CVE-2024-57791, CVE-2024-57883, CVE-2024-58087, CVE-2024-56665, CVE-2024-57887, CVE-2025-21635, CVE-2024-56662, CVE-2024-57893, CVE-2024-57916, CVE-2024-56675, CVE-2024-56763, CVE-2024-56664, CVE-2024-53690, CVE-2025-21663, CVE-2024-56761, CVE-2024-57910, CVE-2025-21660, CVE-2024-57885, CVE-2024-57899, CVE-2025-21650, CVE-2025-21888, CVE-2024-57801, CVE-2024-58237, CVE-2024-56767, CVE-2024-57895, CVE-2024-57912, CVE-2024-56654, CVE-2025-21646, CVE-2024-54683, CVE-2024-57931, CVE-2024-49568, CVE-2025-21639, CVE-2025-21632, CVE-2024-56769, CVE-2024-57807, CVE-2025-21656, CVE-2024-55639, CVE-2024-56652, CVE-2024-57933, CVE-2024-57793, CVE-2025-21662, CVE-2024-57940, CVE-2024-56715, CVE-2024-57906, CVE-2024-57900, CVE-2024-56660, CVE-2024-57897, CVE-2024-49571, CVE-2024-57890, CVE-2025-21642, CVE-2025-21634, CVE-2025-21938, CVE-2024-57929, CVE-2025-21664, CVE-2024-53125, CVE-2024-54460, CVE-2024-57925, CVE-2025-21652, CVE-2025-21653, CVE-2024-55916, CVE-2024-47408, CVE-2024-57902, CVE-2025-21654, CVE-2025-21649, CVE-2024-56770, CVE-2024-57932, CVE-2024-57946, CVE-2025-21640, CVE-2024-57884, CVE-2024-56667, CVE-2024-56659)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2025-21660, CVE-2025-21659, CVE-2024-56718, CVE-2024-56675, CVE-2025-21631, CVE-2025-21664, CVE-2025-21655, CVE-2025-21662, CVE-2024-57804, CVE-2025-21656, CVE-2024-57910, CVE-2025-21647, CVE-2025-21634, CVE-2024-56716, CVE-2024-56709, CVE-2024-56770, CVE-2024-57888, CVE-2024-57793, CVE-2024-56670, CVE-2024-57931, CVE-2025-21640, CVE-2025-21648, CVE-2024-57913, CVE-2024-56710, CVE-2024-44964, CVE-2024-57911, CVE-2025-21654, CVE-2024-57890, CVE-2024-56654, CVE-2024-56767, CVE-2025-21650, CVE-2024-54460, CVE-2025-21635, CVE-2024-57791, CVE-2024-49568, CVE-2024-57879, CVE-2024-57929, CVE-2024-56715, CVE-2024-57899, CVE-2024-53687, CVE-2024-57900, CVE-2024-57903, CVE-2024-54455, CVE-2024-56763, CVE-2024-58087, CVE-2025-21638, CVE-2024-57892, CVE-2024-57884, CVE-2024-57792, CVE-2024-57904, CVE-2024-56759, CVE-2024-56659, CVE-2024-57885, CVE-2024-57889, CVE-2024-56657, CVE-2024-56667, CVE-2024-47408, CVE-2024-57805, CVE-2025-21637, CVE-2024-57893, CVE-2024-57946, CVE-2024-57806, CVE-2024-36476, CVE-2025-21646, CVE-2024-56369, CVE-2024-57917, CVE-2025-21649, CVE-2024-54193, CVE-2024-56717, CVE-2024-41013, CVE-2024-55916, CVE-2024-57933, CVE-2024-57907, CVE-2024-54683, CVE-2024-57887, CVE-2024-56760, CVE-2024-56652, CVE-2024-57940, CVE-2024-57906, CVE-2024-57939, CVE-2024-56372, CVE-2024-56665, CVE-2024-57925, CVE-2025-21938, CVE-2024-57895, CVE-2024-58237, CVE-2024-56664, CVE-2024-56660, CVE-2024-55639, CVE-2025-21632, CVE-2024-57841, CVE-2024-39282, CVE-2025-21651, CVE-2024-53125, CVE-2024-57807, CVE-2025-21643, CVE-2024-57883, CVE-2024-57898, CVE-2024-57897, CVE-2024-53179, CVE-2024-57932, CVE-2024-57916, CVE-2024-53685, CVE-2024-57908, CVE-2025-21652, CVE-2025-21658, CVE-2024-57926, CVE-2024-57801, CVE-2024-55881, CVE-2024-57901, CVE-2025-21653, CVE-2025-21642, CVE-2024-57882, CVE-2024-57912, CVE-2024-56662, CVE-2025-21639, CVE-2025-21971, CVE-2024-47736, CVE-2024-56761, CVE-2024-57945, CVE-2025-21663, CVE-2024-49571, CVE-2024-56758, CVE-2024-53690, CVE-2024-38608, CVE-2024-56656, CVE-2025-21645, CVE-2024-56764, CVE-2024-57896, CVE-2024-57938, CVE-2024-57902, CVE-2025-21636, CVE-2024-56769, CVE-2024-57802)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2024-57945, CVE-2024-56717, CVE-2024-57806, CVE-2025-21659, CVE-2024-57899, CVE-2024-57933, CVE-2024-56675, CVE-2025-21653, CVE-2024-44964, CVE-2024-57892, CVE-2024-56760, CVE-2024-57906, CVE-2024-57792, CVE-2024-54455, CVE-2025-21656, CVE-2024-56656, CVE-2024-57884, CVE-2025-21638, CVE-2024-56758, CVE-2025-21663, CVE-2024-54460, CVE-2024-57911, CVE-2024-55639, CVE-2024-57890, CVE-2025-21632, CVE-2024-57896, CVE-2024-56657, CVE-2024-54683, CVE-2025-21640, CVE-2025-21655, CVE-2025-21651, CVE-2024-57940, CVE-2024-56709, CVE-2024-57904, CVE-2024-47408, CVE-2024-53687, CVE-2025-21639, CVE-2024-57897, CVE-2025-21647, CVE-2024-57907, CVE-2025-21652, CVE-2024-56662, CVE-2024-57882, CVE-2024-56763, CVE-2025-21938, CVE-2024-57802, CVE-2024-36476, CVE-2024-57938, CVE-2024-57883, CVE-2024-57879, CVE-2024-57908, CVE-2024-57939, CVE-2024-57805, CVE-2024-56664, CVE-2024-56761, CVE-2024-56659, CVE-2025-21631, CVE-2024-56715, CVE-2025-21664, CVE-2024-56710, CVE-2024-56372, CVE-2024-57932, CVE-2024-57898, CVE-2025-21971, CVE-2024-47736, CVE-2024-41013, CVE-2024-57931, CVE-2024-56759, CVE-2024-57893, CVE-2025-21635, CVE-2024-53690, CVE-2024-57807, CVE-2024-56652, CVE-2024-57926, CVE-2024-57901, CVE-2024-57793, CVE-2024-39282, CVE-2024-49568, CVE-2024-57903, CVE-2024-57913, CVE-2024-53685, CVE-2024-57912, CVE-2024-56667, CVE-2024-54193, CVE-2024-55881, CVE-2024-56369, CVE-2024-58237, CVE-2024-57929, CVE-2024-53179, CVE-2024-56718, CVE-2025-21650, CVE-2025-21642, CVE-2025-21636, CVE-2025-21649, CVE-2025-21643, CVE-2024-58087, CVE-2025-21662, CVE-2025-21634, CVE-2024-57791, CVE-2025-21660, CVE-2024-49571, CVE-2024-56716, CVE-2024-57804, CVE-2024-57801, CVE-2025-21648, CVE-2024-56769, CVE-2025-21637, CVE-2024-57895, CVE-2024-57910, CVE-2024-57885, CVE-2024-56665, CVE-2024-55916, CVE-2024-57917, CVE-2024-57900, CVE-2024-57841, CVE-2025-21654, CVE-2024-56660, CVE-2025-21646, CVE-2024-57925, CVE-2024-57888, CVE-2025-21645, CVE-2025-21658, CVE-2024-57887, CVE-2024-56767, CVE-2024-57902, CVE-2024-56764, CVE-2024-57916, CVE-2024-56654, CVE-2024-57946, CVE-2024-56670, CVE-2024-56770, CVE-2024-57889, CVE-2024-38608, CVE-2024-53125)

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:

• RISC-V architecture;
• x86 architecture;
• Block layer subsystem;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• Ublk userspace block driver;
• Virtio block driver;
• Bluetooth drivers;
• DMA engine subsystem;
• GPU drivers;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Multiple devices driver;
• Media drivers;
• Microchip PCI driver;
• Network drivers;
• Mellanox network drivers;
• Microsoft Azure Network Adapter (MANA) driver;
• STMicroelectronics network drivers;
• PCI subsystem;
• Pin controllers subsystem;
• x86 platform drivers;
• Power supply drivers;
• SCSI subsystem;
• USB Gadget drivers;
• TDX Guest driver;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• EROFS file system;
• File systems infrastructure;
• Network file systems library;
• NILFS2 file system;
• Overlay file system;
• SMB network file system;
• VLANs driver;
• Memory management;
• LAPB network protocol;
• io_uring subsystem;
• BPF subsystem;
• Control group (cgroup);
• Tracing infrastructure;
• Workqueue subsystem;
• Bluetooth subsystem;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Multipath TCP;
• Netfilter;
• NET/ROM layer;
• Packet sockets;
• RDS protocol;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Wireless networking;
• SELinux security module;
• ALSA framework;
• SOF drivers; (CVE-2024-56653, CVE-2024-57932, CVE-2024-54455, CVE-2024-57938, CVE-2024-57896, CVE-2024-53179, CVE-2024-57903, CVE-2025-21640, CVE-2024-56654, CVE-2024-57906, CVE-2024-53690, CVE-2025-21648, CVE-2024-57913, CVE-2025-21655, CVE-2024-57907, CVE-2025-21634, CVE-2024-57926, CVE-2025-21659, CVE-2024-54460, CVE-2024-57898, CVE-2024-56769, CVE-2024-36476, CVE-2025-21938, CVE-2025-21637, CVE-2024-57888, CVE-2024-57901, CVE-2024-57887, CVE-2024-57940, CVE-2024-49571, CVE-2024-57889, CVE-2024-55639, CVE-2024-57899, CVE-2024-56759, CVE-2024-41013, CVE-2024-57895, CVE-2024-57933, CVE-2024-56662, CVE-2024-56767, CVE-2025-21639, CVE-2024-56715, CVE-2024-57883, CVE-2025-21636, CVE-2024-57931, CVE-2025-21642, CVE-2024-53685, CVE-2024-56659, CVE-2025-21971, CVE-2024-56716, CVE-2025-21652, CVE-2024-57792, CVE-2025-21638, CVE-2024-56764, CVE-2024-55916, CVE-2024-57916, CVE-2024-56718, CVE-2024-57929, CVE-2024-57900, CVE-2025-21660, CVE-2024-57879, CVE-2024-56758, CVE-2024-57908, CVE-2025-21664, CVE-2024-56652, CVE-2024-57882, CVE-2024-39282, CVE-2025-21663, CVE-2024-47736, CVE-2024-54193, CVE-2025-21650, CVE-2024-56665, CVE-2024-57793, CVE-2024-58087, CVE-2025-21658, CVE-2025-21643, CVE-2024-54683, CVE-2024-56667, CVE-2024-56664, CVE-2024-56770, CVE-2024-57946, CVE-2024-57904, CVE-2024-56709, CVE-2024-56369, CVE-2024-58237, CVE-2024-57885, CVE-2024-56763, CVE-2024-56657, CVE-2025-21645, CVE-2024-57893, CVE-2025-21631, CVE-2024-57791, CVE-2024-57910, CVE-2024-57902, CVE-2024-57806, CVE-2025-21656, CVE-2024-53125, CVE-2024-56761, CVE-2024-56717, CVE-2024-47408, CVE-2025-21654, CVE-2025-21649, CVE-2024-57807, CVE-2024-56675, CVE-2025-21653, CVE-2024-57897, CVE-2024-53687, CVE-2024-56760, CVE-2025-21635, CVE-2025-21632, CVE-2024-57890, CVE-2025-21647, CVE-2024-57917, CVE-2024-56372, CVE-2024-56656, CVE-2024-57912, CVE-2024-57841, CVE-2025-21953, CVE-2024-56710, CVE-2024-57884, CVE-2024-57804, CVE-2025-21888, CVE-2024-56660, CVE-2024-57805, CVE-2024-57801, CVE-2024-38608, CVE-2024-57945, CVE-2024-55881, CVE-2024-57802, CVE-2024-57892, CVE-2025-21646, CVE-2024-56670, CVE-2025-21651, CVE-2024-57939, CVE-2024-57925, CVE-2024-57911, CVE-2025-21662, CVE-2024-49568)

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;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• SuperH RISC architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• RAM backed block device driver;
• Ublk userspace block driver;
• Virtio block driver;
• Compressed RAM block device driver;
• Bluetooth drivers;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DMA engine subsystem;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• iSCSI Boot Firmware Table Attributes driver;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• NVME drivers;
• Parport drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• i.MX SoC drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Direct Digital Synthesis drivers;
• Media staging drivers;
• TCM subsystem;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C support driver;
• USB Type-C Port Controller Manager driver;
• TI TPS6598x USB Power Delivery controller driver;
• USB Type-C Connector System Software Interface driver;
• vDPA drivers;
• VFIO drivers;
• Framebuffer layer;
• TDX Guest driver;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system;
• Proc file system;
• Diskquota system;
• SMB network file system;
• UBI file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• Kernel Samepage Merging mechanism;
• Memory management;
• Network file system (NFS) superblock;
• Kernel stack handling interfaces;
• StackDepot library;
• Task handling mechanism;
• userfaultfd() syscall;
• Bluetooth subsystem;
• IP tunnels definitions;
• LAPB network protocol;
• Network namespace;
• Netfilter;
• Network traffic control;
• Network sockets;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• Kernel thread helper (kthread);
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure; -…

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;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• SuperH RISC architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Drivers core;
• RAM backed block device driver;
• Ublk userspace block driver;
• Virtio block driver;
• Compressed RAM block device driver;
• Bluetooth drivers;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• CXL (Compute Express Link) drivers;
• DAX dirext access to differentiated memory framework;
• DMA engine subsystem;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• iSCSI Boot Firmware Table Attributes driver;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• Microsoft Hyper-V drivers;
• Hardware monitoring drivers;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Microchip PCI driver;
• MMC subsystem;
• MTD block device drivers;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• NVME drivers;
• Parport drivers;
• PCI subsystem;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Power supply drivers;
• Voltage and Current Regulator drivers;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• i.MX SoC drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Direct Digital Synthesis drivers;
• Media staging drivers;
• TCM subsystem;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C support driver;
• USB Type-C Port Controller Manager driver;
• TI TPS6598x USB Power Delivery controller driver;
• USB Type-C Connector System Software Interface driver;
• vDPA drivers;
• VFIO drivers;
• Framebuffer layer;
• TDX Guest driver;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• EROFS file system;
• Ext4 file system;
• F2FS file system;
• JFFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• NTFS3 file system;
• Overlay file system;
• Proc file system;
• Diskquota system;
• SMB network file system;
• UBI file system;
• DRM display driver;
• BPF subsystem;
• VLANs driver;
• Kernel Samepage Merging mechanism;
• Memory management;
• Network file system (NFS) superblock;
• Kernel stack handling interfaces;
• StackDepot library;
• Task handling mechanism;
• userfaultfd() syscall;
• Bluetooth subsystem;
• IP tunnels definitions;
• LAPB network protocol;
• Network namespace;
• Netfilter;
• Network traffic control;
• Network sockets;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• Control group (cgroup);
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• Kernel thread helper (kthread);
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure; -…