CVE-2024-53047

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

mptcp: init: protect sched with rcu_read_lock

Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT creates this splat when an MPTCP socket is created:

============================= WARNING: suspicious RCU usage 6.12.0-rc2+ #11 Not tainted

net/mptcp/sched.c:44 RCU-list traversed in non-reader section!!

other info that might help us debug this:

rcu_scheduler_active = 2, debug_locks = 1 no locks held by mptcp_connect/176.

stack backtrace: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1)) ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28) inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386) ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfx___sys_socket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) __x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)

That's because when the socket is initialised, rcu_read_lock() is not used despite the explicit comment written above the declaration of mptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the warning.

In the Linux kernel, the following vulnerability has been resolved: mptcp: init: protect sched with rcu_read_lock Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT creates this splat when an MPTCP socket is created: ============================= WARNING: suspicious RCU usage 6.12.0-rc2+ #11 Not tainted ----------------------------- net/mptcp/sched.c:44 RCU-list traversed in non-reader section!! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 no locks held by mptcp_connect/176. stack backtrace: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1)) ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28) inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386) ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfx___sys_socket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) __x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) That's because when the socket is initialised, rcu_read_lock() is not used despite the explicit comment written above the declaration of mptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the warning.

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: bpf: support non-r10 register spill/fill to/from stack in precision tracking Use instruction (jump) history to record instructions that performed register spill/fill to/from stack, regardless if this was done through read-only r10 register, or any other register after copying r10 into it and potentially adjusting offset. To make this work reliably, we push extra per-instruction flags into instruction history, encoding stack slot index (spi) and stack frame number in extra 10 bit flags we take away from prev_idx in instruction history. We don't touch idx field for maximum performance, as it's checked most frequently during backtracking. This change removes basically the last remaining practical limitation of precision backtracking logic in BPF verifier. It fixes known deficiencies, but also opens up new opportunities to reduce number of verified states, explored in the subsequent patches. There are only three differences in selftests' BPF object files according to veristat, all in the positive direction (less states). File Program Insns (A) Insns (B) Insns (DIFF) States (A) States (B) States (DIFF) -------------------------------------- ------------- --------- --------- ------------- ---------- ---------- ------------- test_cls_redirect_dynptr.bpf.linked3.o cls_redirect 2987 2864 -123 (-4.12%) 240 231 -9 (-3.75%) xdp_synproxy_kern.bpf.linked3.o syncookie_tc 82848 82661 -187 (-0.23%) 5107 5073 -34 (-0.67%) xdp_synproxy_kern.bpf.linked3.o syncookie_xdp 85116 84964 -152 (-0.18%) 5162 5130 -32 (-0.62%) Note, I avoided renaming jmp_history to more generic insn_hist to minimize number of lines changed and potential merge conflicts between bpf and bpf-next trees. Notice also cur_hist_entry pointer reset to NULL at the beginning of instruction verification loop. This pointer avoids the problem of relying on last jump history entry's insn_idx to determine whether we already have entry for current instruction or not. It can happen that we added jump history entry because current instruction is_jmp_point(), but also we need to add instruction flags for stack access. In this case, we don't want to entries, so we need to reuse last added entry, if it is present. Relying on insn_idx comparison has the same ambiguity problem as the one that was fixed recently in [0], so we avoid that. [0] https://patchwork.kernel.org/project/netdevbpf/patch/[email protected]/(CVE-2023-52920)

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

mptcp: pm: only mark 'subflow' endp as available

Adding the following warning ...

WARN_ON_ONCE(msk->pm.local_addr_used == 0)

... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests.

Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed.

Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is done no matter if a subflow using this ID is currently available, because the subflow could have been closed before.(CVE-2024-45010)

In the Linux…

In the Linux kernel, the following vulnerability has been resolved: mptcp: init: protect sched with rcu_read_lock Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT creates this splat when an MPTCP socket is created: ============================= WARNING: suspicious RCU usage 6.12.0-rc2+ #11 Not tainted ----------------------------- net/mptcp/sched.c:44 RCU-list traversed in non-reader section!! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 no locks held by mptcp_connect/176. stack backtrace: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1)) ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28) inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386) ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfx___sys_socket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) __x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) That's because when the socket is initialised, rcu_read_lock() is not used despite the explicit comment written above the declaration of mptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the warning.

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:

• ARM32 architecture;
• ARM64 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;
• ATA over ethernet (AOE) driver;
• RAM backed block device driver;
• Network block device driver;
• Ublk userspace 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;
• Buffer Sharing and Synchronization framework;
• EDAC drivers;
• FireWire subsystem;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• Qualcomm firmware drivers;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• MMC subsystem;
• MTD block device drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• NVME drivers;
• Parport drivers;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• i.MX PM domains;
• Powercap sysfs driver;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Direct Digital Synthesis drivers;
• Media staging drivers;
• TCM subsystem;
• Thermal drivers;
• Thunderbolt and USB4 drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• 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;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Virtio drivers;
• 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;
• GFS2 file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• File system notification infrastructure;
• NTFS3 file system;
• Proc file system;
• SMB network file system;
• UBI file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Virtio network driver;
• Bluetooth subsystem;
• Network traffic control;
• Network sockets;
• TCP network protocol;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init 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;
• Compressed RAM block device driver;
• 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;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• MMC subsystem;
• 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;
• Voltage and Current Regulator drivers;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Media staging drivers;
• TCM subsystem;
• UFS subsystem;
• DesignWare USB3 driver;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C support driver;
• USB Type-C Port Controller Manager driver;
• USB Type-C Connector System Software Interface driver;
• vDPA drivers;
• VFIO drivers;
• Framebuffer layer;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• EROFS 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;
• StackDepot library;
• Bluetooth subsystem;
• IP tunnels definitions;
• Netfilter;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure;
• Signal handling mechanism;
• Task handling mechanism;
• Timer subsystem;
• KUnit library;
• Memory management;
• 9P file system network protocol;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• Ethtool driver;
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Multipath TCP;
• Packet sockets;
• RxRPC session sockets;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Sun RPC protocol;
• TIPC protocol;
• VMware vSockets driver;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• Integrity Measurement Architecture(IMA) framework;
• Key management;
• ALSA framework;
• FireWire sound drivers;
• HD-audio driver;
• MediaTek ASoC drivers;
• QCOM ASoC drivers;
• SoC audio core drivers;
• STMicroelectronics SoC drivers;
• USB sound devices; (CVE-2024-50288, CVE-2024-56568, CVE-2024-50280, CVE-2024-56677, CVE-2024-56620, CVE-2024-53108, CVE-2024-53115, CVE-2024-53061,…

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;
• Compressed RAM block device driver;
• 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;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• MMC subsystem;
• 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;
• Voltage and Current Regulator drivers;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Media staging drivers;
• TCM subsystem;
• UFS subsystem;
• DesignWare USB3 driver;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C support driver;
• USB Type-C Port Controller Manager driver;
• USB Type-C Connector System Software Interface driver;
• vDPA drivers;
• VFIO drivers;
• Framebuffer layer;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• EROFS 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;
• StackDepot library;
• Bluetooth subsystem;
• IP tunnels definitions;
• Netfilter;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure;
• Signal handling mechanism;
• Task handling mechanism;
• Timer subsystem;
• KUnit library;
• Memory management;
• 9P file system network protocol;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• Ethtool driver;
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Multipath TCP;
• Packet sockets;
• RxRPC session sockets;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Sun RPC protocol;
• TIPC protocol;
• VMware vSockets driver;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• Integrity Measurement Architecture(IMA) framework;
• Key management;
• ALSA framework;
• FireWire sound drivers;
• HD-audio driver;
• MediaTek ASoC drivers;
• QCOM ASoC drivers;
• SoC audio core drivers;
• STMicroelectronics SoC drivers;
• USB sound devices; (CVE-2022-49034, CVE-2024-56632, CVE-2024-53177, CVE-2024-56679, CVE-2024-48881, CVE-2024-56690, CVE-2024-50216, CVE-2024-50269,…

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;
• Compressed RAM block device driver;
• 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;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• MMC subsystem;
• 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;
• Voltage and Current Regulator drivers;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Media staging drivers;
• TCM subsystem;
• UFS subsystem;
• DesignWare USB3 driver;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C support driver;
• USB Type-C Port Controller Manager driver;
• USB Type-C Connector System Software Interface driver;
• vDPA drivers;
• VFIO drivers;
• Framebuffer layer;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• EROFS 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;
• StackDepot library;
• Bluetooth subsystem;
• IP tunnels definitions;
• Netfilter;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure;
• Signal handling mechanism;
• Task handling mechanism;
• Timer subsystem;
• KUnit library;
• Memory management;
• 9P file system network protocol;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• Ethtool driver;
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Multipath TCP;
• Packet sockets;
• RxRPC session sockets;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Sun RPC protocol;
• TIPC protocol;
• VMware vSockets driver;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• Integrity Measurement Architecture(IMA) framework;
• Key management;
• ALSA framework;
• FireWire sound drivers;
• HD-audio driver;
• MediaTek ASoC drivers;
• QCOM ASoC drivers;
• SoC audio core drivers;
• STMicroelectronics SoC drivers;
• USB sound devices; (CVE-2024-50051, CVE-2024-56546, CVE-2024-56551, CVE-2024-53236, CVE-2024-50244, CVE-2024-53043, CVE-2024-56694, CVE-2025-21700,…

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;
• Compressed RAM block device driver;
• 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;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• 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;
• 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;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• 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;
• Network file system (NFS) superblock;
• StackDepot library;
• Bluetooth subsystem;
• IP tunnels definitions;
• Network namespace;
• Netfilter;
• Network traffic control;
• Network sockets;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• Kernel thread helper (kthread);
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure;
• Signal handling mechanism;
• Task handling mechanism;
• Timer subsystem;
• KUnit library;
• Maple Tree data structure library;
• Memory management;
• 9P file system network protocol;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• Ethtool driver;
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Multipath TCP;
• Netlink;
• Packet sockets;…

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;
• Compressed RAM block device driver;
• 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;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• MMC subsystem;
• 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;
• Voltage and Current Regulator drivers;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Media staging drivers;
• TCM subsystem;
• UFS subsystem;
• DesignWare USB3 driver;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C support driver;
• USB Type-C Port Controller Manager driver;
• USB Type-C Connector System Software Interface driver;
• vDPA drivers;
• VFIO drivers;
• Framebuffer layer;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• EROFS 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;
• StackDepot library;
• Bluetooth subsystem;
• IP tunnels definitions;
• Netfilter;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure;
• Signal handling mechanism;
• Task handling mechanism;
• Timer subsystem;
• KUnit library;
• Memory management;
• 9P file system network protocol;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• Ethtool driver;
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Multipath TCP;
• Packet sockets;
• RxRPC session sockets;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Sun RPC protocol;
• TIPC protocol;
• VMware vSockets driver;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• Integrity Measurement Architecture(IMA) framework;
• Key management;
• ALSA framework;
• FireWire sound drivers;
• HD-audio driver;
• MediaTek ASoC drivers;
• QCOM ASoC drivers;
• SoC audio core drivers;
• STMicroelectronics SoC drivers;
• USB sound devices; (CVE-2024-56724, CVE-2024-50108, CVE-2024-56631, CVE-2024-50236, CVE-2022-49034, CVE-2024-50133, CVE-2024-53108, CVE-2024-56605,…

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;
• Compressed RAM block device driver;
• 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;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• LED subsystem;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• MMC subsystem;
• 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;
• Voltage and Current Regulator drivers;
• StarFive reset controller drivers;
• Real Time Clock drivers;
• SCSI subsystem;
• i.MX SoC drivers;
• QCOM SoC drivers;
• Xilinx SoC drivers;
• SPI subsystem;
• Media staging drivers;
• TCM subsystem;
• UFS subsystem;
• DesignWare USB3 driver;
• USB Dual Role (OTG-ready) Controller drivers;
• USB Serial drivers;
• USB Type-C support driver;
• USB Type-C Port Controller Manager driver;
• USB Type-C Connector System Software Interface driver;
• vDPA drivers;
• VFIO drivers;
• Framebuffer layer;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• EROFS 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;
• StackDepot library;
• Bluetooth subsystem;
• IP tunnels definitions;
• Netfilter;
• Tracing infrastructure;
• User-space API (UAPI);
• Kernel init infrastructure;
• io_uring subsystem;
• IPC subsystem;
• DMA mapping infrastructure;
• Kernel fork() syscall;
• KCSAN framework;
• RCU subsystem;
• Arbitrary resource management;
• Scheduler infrastructure;
• Signal handling mechanism;
• Task handling mechanism;
• Timer subsystem;
• KUnit library;
• Memory management;
• 9P file system network protocol;
• CAN network layer;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• Ethtool driver;
• HSR network protocol;
• IEEE802154.4 network protocol;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• Multipath TCP;
• Packet sockets;
• RxRPC session sockets;
• Network traffic control;
• SCTP protocol;
• SMC sockets;
• Sun RPC protocol;
• TIPC protocol;
• VMware vSockets driver;
• Wireless networking;
• eXpress Data Path;
• XFRM subsystem;
• Integrity Measurement Architecture(IMA) framework;
• Key management;
• ALSA framework;
• FireWire sound drivers;
• HD-audio driver;
• MediaTek ASoC drivers;
• QCOM ASoC drivers;
• SoC audio core drivers;
• STMicroelectronics SoC drivers;
• USB sound devices; (CVE-2024-53187, CVE-2024-50268, CVE-2024-53161, CVE-2024-56721, CVE-2024-53059, CVE-2024-53217, CVE-2022-49034, CVE-2024-53061,…

Michael Randrianantenaina discovered that the Bluetooth driver in the Linux Kernel contained an improper access control vulnerability. A nearby attacker could use this to connect a rougue device and possibly execute arbitrary code. (CVE-2024-8805)

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)

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

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

• 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;
• ATA over ethernet (AOE) driver;
• RAM backed block device driver;
• Network block device driver;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• 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;
• EDAC drivers;
• ARM SCMI message protocol;
• ARM SCPI message protocol;
• EFI core;
• iSCSI Boot Firmware Table Attributes driver;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• LED subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• MMC subsystem;
• MTD block device drivers;
• Ethernet bonding driver;
• 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;
• 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;
• USB Device Class drivers;
• 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;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• 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; …

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