CVE-2024-49885

In the Linux kernel, the following vulnerability has been resolved: mm, slub: avoid zeroing kmalloc redzone Since commit 946fa0dbf2d8 ("mm/slub: extend redzone check to extra allocated kmalloc space than requested"), setting orig_size treats the wasted space (object_size - orig_size) as a redzone. However with init_on_free=1 we clear the full object->size, including the redzone. Additionally we clear the object metadata, including the stored orig_size, making it zero, which makes check_object() treat the whole object as a redzone. These issues lead to the following BUG report with "slub_debug=FUZ init_on_free=1": [ 0.000000] ============================================================================= [ 0.000000] BUG kmalloc-8 (Not tainted): kmalloc Redzone overwritten [ 0.000000] ----------------------------------------------------------------------------- [ 0.000000] [ 0.000000] 0xffff000010032858-0xffff00001003285f @offset=2136. First byte 0x0 instead of 0xcc [ 0.000000] FIX kmalloc-8: Restoring kmalloc Redzone 0xffff000010032858-0xffff00001003285f=0xcc [ 0.000000] Slab 0xfffffdffc0400c80 objects=36 used=23 fp=0xffff000010032a18 flags=0x3fffe0000000200(workingset|node=0|zone=0|lastcpupid=0x1ffff) [ 0.000000] Object 0xffff000010032858 @offset=2136 fp=0xffff0000100328c8 [ 0.000000] [ 0.000000] Redzone ffff000010032850: cc cc cc cc cc cc cc cc ........ [ 0.000000] Object ffff000010032858: cc cc cc cc cc cc cc cc ........ [ 0.000000] Redzone ffff000010032860: cc cc cc cc cc cc cc cc ........ [ 0.000000] Padding ffff0000100328b4: 00 00 00 00 00 00 00 00 00 00 00 00 ............ [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-rc3-next-20240814-00004-g61844c55c3f4 #144 [ 0.000000] Hardware name: NXP i.MX95 19X19 board (DT) [ 0.000000] Call trace: [ 0.000000] dump_backtrace+0x90/0xe8 [ 0.000000] show_stack+0x18/0x24 [ 0.000000] dump_stack_lvl+0x74/0x8c [ 0.000000] dump_stack+0x18/0x24 [ 0.000000] print_trailer+0x150/0x218 [ 0.000000] check_object+0xe4/0x454 [ 0.000000] free_to_partial_list+0x2f8/0x5ec To address the issue, use orig_size to clear the used area. And restore the value of orig_size after clear the remaining area. When CONFIG_SLUB_DEBUG not defined, (get_orig_size()' directly returns s->object_size. So when using memset to init the area, the size can simply be orig_size, as orig_size returns object_size when CONFIG_SLUB_DEBUG not enabled. And orig_size can never be bigger than object_size.

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: mm, slub: avoid zeroing kmalloc redzone Since commit 946fa0dbf2d8 ("mm/slub: extend redzone check to extra allocated kmalloc space than requested"), setting orig_size treats the wasted space (object_size - orig_size) as a redzone. However with init_on_free=1 we clear the full object->size, including the redzone. Additionally we clear the object metadata, including the stored orig_size, making it zero, which makes check_object() treat the whole object as a redzone. These issues lead to the following BUG report with "slub_debug=FUZ init_on_free=1": [ 0.000000] ============================================================================= [ 0.000000] BUG kmalloc-8 (Not tainted): kmalloc Redzone overwritten [ 0.000000] ----------------------------------------------------------------------------- [ 0.000000] [ 0.000000] 0xffff000010032858-0xffff00001003285f @offset=2136. First byte 0x0 instead of 0xcc [ 0.000000] FIX kmalloc-8: Restoring kmalloc Redzone 0xffff000010032858-0xffff00001003285f=0xcc [ 0.000000] Slab 0xfffffdffc0400c80 objects=36 used=23 fp=0xffff000010032a18 flags=0x3fffe0000000200(workingset|node=0|zone=0|lastcpupid=0x1ffff) [ 0.000000] Object 0xffff000010032858 @offset=2136 fp=0xffff0000100328c8 [ 0.000000] [ 0.000000] Redzone ffff000010032850: cc cc cc cc cc cc cc cc ........ [ 0.000000] Object ffff000010032858: cc cc cc cc cc cc cc cc ........ [ 0.000000] Redzone ffff000010032860: cc cc cc cc cc cc cc cc ........ [ 0.000000] Padding ffff0000100328b4: 00 00 00 00 00 00 00 00 00 00 00 00 ............ [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-rc3-next-20240814-00004-g61844c55c3f4 #144 [ 0.000000] Hardware name: NXP i.MX95 19X19 board (DT) [ 0.000000] Call trace: [ 0.000000] dump_backtrace+0x90/0xe8 [ 0.000000] show_stack+0x18/0x24 [ 0.000000] dump_stack_lvl+0x74/0x8c [ 0.000000] dump_stack+0x18/0x24 [ 0.000000] print_trailer+0x150/0x218 [ 0.000000] check_object+0xe4/0x454 [ 0.000000] free_to_partial_list+0x2f8/0x5ec To address the issue, use orig_size to clear the used area. And restore the value of orig_size after clear the remaining area. When CONFIG_SLUB_DEBUG not defined, (get_orig_size()' directly returns s->object_size. So when using memset to init the area, the size can simply be orig_size, as orig_size returns object_size when CONFIG_SLUB_DEBUG not enabled. And orig_size can never be bigger than object_size.

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

mm, slub: avoid zeroing kmalloc redzone

Since commit 946fa0dbf2d8 ("mm/slub: extend redzone check to extra allocated kmalloc space than requested"), setting orig_size treats the wasted space (object_size - orig_size) as a redzone. However with init_on_free=1 we clear the full object->size, including the redzone.

Additionally we clear the object metadata, including the stored orig_size, making it zero, which makes check_object() treat the whole object as a redzone.

These issues lead to the following BUG report with "slub_debug=FUZ init_on_free=1":

[ 0.000000] ============================================================================= [ 0.000000] BUG kmalloc-8 (Not tainted): kmalloc Redzone overwritten [ 0.000000] ----------------------------------------------------------------------------- [ 0.000000] [ 0.000000] 0xffff000010032858-0xffff00001003285f @offset=2136. First byte 0x0 instead of 0xcc [ 0.000000] FIX kmalloc-8: Restoring kmalloc Redzone 0xffff000010032858-0xffff00001003285f=0xcc [ 0.000000] Slab 0xfffffdffc0400c80 objects=36 used=23 fp=0xffff000010032a18 flags=0x3fffe0000000200(workingset|node=0|zone=0|lastcpupid=0x1ffff) [ 0.000000] Object 0xffff000010032858 @offset=2136 fp=0xffff0000100328c8 [ 0.000000] [ 0.000000] Redzone ffff000010032850: cc cc cc cc cc cc cc cc ........ [ 0.000000] Object ffff000010032858: cc cc cc cc cc cc cc cc ........ [ 0.000000] Redzone ffff000010032860: cc cc cc cc cc cc cc cc ........ [ 0.000000] Padding ffff0000100328b4: 00 00 00 00 00 00 00 00 00 00 00 00 ............ [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-rc3-next-20240814-00004-g61844c55c3f4 #144 [ 0.000000] Hardware name: NXP i.MX95 19X19 board (DT) [ 0.000000] Call trace: [ 0.000000] dump_backtrace+0x90/0xe8 [ 0.000000] show_stack+0x18/0x24 [ 0.000000] dump_stack_lvl+0x74/0x8c [ 0.000000] dump_stack+0x18/0x24 [ 0.000000] print_trailer+0x150/0x218 [ 0.000000] check_object+0xe4/0x454 [ 0.000000] free_to_partial_list+0x2f8/0x5ec

To address the issue, use orig_size to clear the used area. And restore the value of orig_size after clear the remaining area.

When CONFIG_SLUB_DEBUG not defined, (get_orig_size()' directly returns s->object_size. So when using memset to init the area, the size can simply be orig_size, as orig_size returns object_size when CONFIG_SLUB_DEBUG not enabled. And orig_size can never be bigger than object_size.

These are all security issues fixed in the kernel-devel-6.11.8-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the kernel-devel-longterm-6.12.11-1.1 package on the GA media of openSUSE Tumbleweed.

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• TPM device driver;
• Hardware crypto device drivers;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• USB Device Class drivers;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• SMB network file system;
• BPF subsystem;
• Virtio network driver;
• TCP network protocol;
• Perf events;
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Tracing infrastructure;
• Memory management;
• Bluetooth subsystem;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• NCSI (Network Controller Sideband Interface) driver;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AudioScience HPI driver;
• KVM core; (CVE-2024-47748, CVE-2024-49935, CVE-2024-49892, CVE-2024-49960, CVE-2024-49886, CVE-2024-47757, CVE-2024-47741, CVE-2024-49879, CVE-2024-49983, CVE-2024-47687, CVE-2024-49948, CVE-2024-49902, CVE-2024-49969, CVE-2024-49903, CVE-2024-47675, CVE-2024-47713, CVE-2024-47750, CVE-2024-49951, CVE-2024-49936, CVE-2024-49913, CVE-2024-47684, CVE-2024-49917, CVE-2024-47693, CVE-2024-49871, CVE-2024-47740, CVE-2024-49927, CVE-2024-47698, CVE-2024-49996, CVE-2024-47682, CVE-2024-49889, CVE-2024-49888, CVE-2024-47737, CVE-2024-49881, CVE-2023-52917, CVE-2024-47695, CVE-2024-50015, CVE-2024-49965, CVE-2024-50179, CVE-2024-47677, CVE-2024-50013, CVE-2024-49855, CVE-2024-47751, CVE-2024-49895, CVE-2024-49930, CVE-2024-49905, CVE-2024-47709, CVE-2024-49953, CVE-2024-49896, CVE-2024-47688, CVE-2024-47712, CVE-2024-49907, CVE-2024-49955, CVE-2024-49933, CVE-2024-49880, CVE-2024-49860, CVE-2024-50176, CVE-2024-47727, CVE-2024-47673, CVE-2024-49878, CVE-2024-49862, CVE-2024-49911, CVE-2024-47734, CVE-2024-49995, CVE-2024-49924, CVE-2024-49925, CVE-2024-47749, CVE-2024-49945, CVE-2024-49950, CVE-2024-49891, CVE-2024-49915, CVE-2024-50006, CVE-2024-49962, CVE-2024-49952, CVE-2024-49982, CVE-2024-49939, CVE-2024-49985, CVE-2024-49928, CVE-2024-47692, CVE-2024-49884, CVE-2024-47756, CVE-2024-49918, CVE-2024-49976, CVE-2024-47671, CVE-2024-49859, CVE-2024-47705, CVE-2024-49864, CVE-2024-47733, CVE-2024-49961, CVE-2024-49973, CVE-2024-49989, CVE-2024-47719, CVE-2024-47685, CVE-2024-49988, CVE-2024-49975, CVE-2024-47681, CVE-2024-49944, CVE-2024-47718, CVE-2024-47689, CVE-2024-50008, CVE-2024-49959, CVE-2024-49868, CVE-2024-47743, CVE-2024-49885,…

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• TPM device driver;
• Hardware crypto device drivers;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• USB Device Class drivers;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• SMB network file system;
• BPF subsystem;
• Virtio network driver;
• TCP network protocol;
• Perf events;
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Tracing infrastructure;
• Memory management;
• Bluetooth subsystem;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• NCSI (Network Controller Sideband Interface) driver;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AudioScience HPI driver;
• KVM core; (CVE-2024-49852, CVE-2024-50175, CVE-2024-47709, CVE-2024-47671, CVE-2024-50179, CVE-2024-47743, CVE-2024-47687, CVE-2024-49934, CVE-2024-47700, CVE-2024-49892, CVE-2024-49866, CVE-2024-50012, CVE-2024-49860, CVE-2024-49948, CVE-2024-49882, CVE-2024-47744, CVE-2024-49905, CVE-2024-47728, CVE-2024-49874, CVE-2024-47678, CVE-2024-47688, CVE-2024-47737, CVE-2024-49859, CVE-2024-49947, CVE-2024-49994, CVE-2024-49986, CVE-2024-49917, CVE-2024-50000, CVE-2024-49962, CVE-2024-47733, CVE-2024-47741, CVE-2024-47685, CVE-2024-47752, CVE-2024-49960, CVE-2024-47754, CVE-2024-47675, CVE-2024-49958, CVE-2024-47748, CVE-2024-47679, CVE-2024-47690, CVE-2024-47740, CVE-2024-47672, CVE-2024-49883, CVE-2024-49928, CVE-2024-49961, CVE-2024-47677, CVE-2024-47706, CVE-2024-49955, CVE-2024-49907, CVE-2024-47745, CVE-2024-49963, CVE-2024-47723, CVE-2024-49897, CVE-2024-49927, CVE-2024-50008, CVE-2024-47713, CVE-2024-49894, CVE-2024-49903, CVE-2024-47747, CVE-2024-47705, CVE-2024-49976, CVE-2024-53144, CVE-2024-49983, CVE-2024-49937, CVE-2024-49953, CVE-2024-41016, CVE-2024-49969, CVE-2024-49982, CVE-2024-50007, CVE-2024-50015, CVE-2024-49889, CVE-2024-49923, CVE-2024-49850, CVE-2024-47720, CVE-2024-49973, CVE-2024-49991, CVE-2024-49901, CVE-2024-49881, CVE-2024-49911, CVE-2024-47710, CVE-2024-49981, CVE-2024-49918, CVE-2024-49861, CVE-2024-49959, CVE-2024-50005, CVE-2024-47701, CVE-2024-49855, CVE-2024-49987, CVE-2024-47704, CVE-2024-49977, CVE-2024-47670, CVE-2024-47707, CVE-2024-47735, CVE-2024-49996, CVE-2024-49868, CVE-2024-47749, CVE-2024-49985, CVE-2024-47753, CVE-2024-49877, CVE-2024-47716, CVE-2024-47731, CVE-2024-49880, CVE-2024-47715, CVE-2024-49931, CVE-2024-49856, CVE-2024-49929, CVE-2024-47689, CVE-2024-49885, CVE-2024-50002, CVE-2024-49999, CVE-2024-47734, CVE-2024-49909, CVE-2024-49871, CVE-2024-49915, CVE-2024-50013, CVE-2024-47682, CVE-2024-49864, CVE-2024-49949, CVE-2024-49933, CVE-2024-49975, CVE-2024-49863, CVE-2024-49867,…

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• TPM device driver;
• Hardware crypto device drivers;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• USB Device Class drivers;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• SMB network file system;
• BPF subsystem;
• Virtio network driver;
• TCP network protocol;
• Perf events;
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Tracing infrastructure;
• Memory management;
• Bluetooth subsystem;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• NCSI (Network Controller Sideband Interface) driver;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AudioScience HPI driver;
• KVM core; (CVE-2024-47718, CVE-2024-49942, CVE-2024-49897, CVE-2024-49871, CVE-2024-47687, CVE-2024-47692, CVE-2024-47740, CVE-2024-47691, CVE-2024-49973, CVE-2024-49958, CVE-2024-49889, CVE-2024-49927, CVE-2024-49883, CVE-2024-49885, CVE-2024-49912, CVE-2024-47686, CVE-2024-49985, CVE-2024-47732, CVE-2024-47685, CVE-2024-49935, CVE-2024-49995, CVE-2024-47731, CVE-2024-49931, CVE-2024-49886, CVE-2024-53144, CVE-2024-49917, CVE-2024-49868, CVE-2024-49999, CVE-2024-47684, CVE-2024-50013, CVE-2024-49962, CVE-2024-49981, CVE-2024-49858, CVE-2024-49878, CVE-2024-49852, CVE-2024-49928, CVE-2024-50006, CVE-2024-49988, CVE-2024-47697, CVE-2024-49923, CVE-2024-47704, CVE-2024-49947, CVE-2024-47751, CVE-2024-47672, CVE-2024-47737, CVE-2024-49909, CVE-2024-49992, CVE-2024-49944, CVE-2024-49950, CVE-2024-49850, CVE-2024-49951, CVE-2024-49996, CVE-2024-49934, CVE-2024-47705, CVE-2024-47741, CVE-2024-49957, CVE-2024-47682, CVE-2024-49976, CVE-2024-49895, CVE-2024-47689, CVE-2024-49937, CVE-2024-47702, CVE-2024-49959, CVE-2024-47719, CVE-2024-49922, CVE-2024-47743, CVE-2024-47696, CVE-2024-50017, CVE-2024-49864, CVE-2024-47747, CVE-2024-47748, CVE-2024-47701, CVE-2024-49915, CVE-2024-49877, CVE-2024-41016, CVE-2024-49961, CVE-2024-47730, CVE-2024-49924, CVE-2024-49974, CVE-2024-49875, CVE-2024-49918, CVE-2024-47712, CVE-2024-50014, CVE-2024-47679, CVE-2024-49894, CVE-2024-49911, CVE-2024-49855, CVE-2024-49948, CVE-2024-49955, CVE-2023-52917, CVE-2024-50015, CVE-2024-47754, CVE-2024-49929, CVE-2024-50005, CVE-2024-47742, CVE-2024-49991, CVE-2024-49913, CVE-2024-49980, CVE-2024-47749, CVE-2024-49975, CVE-2024-47671, CVE-2024-47677, CVE-2024-47727, CVE-2024-47716, CVE-2024-47707, CVE-2024-49870, CVE-2024-47703, CVE-2024-47710, CVE-2024-49977, CVE-2024-49997, CVE-2024-49853, CVE-2024-47681, CVE-2024-49986, CVE-2024-49969, CVE-2024-50000, CVE-2024-47690, CVE-2024-47709, CVE-2024-47713, CVE-2024-47720, CVE-2024-49879, CVE-2024-47699, CVE-2024-47714,…

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• TPM device driver;
• Hardware crypto device drivers;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• USB Device Class drivers;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• SMB network file system;
• BPF subsystem;
• Virtio network driver;
• TCP network protocol;
• Perf events;
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Tracing infrastructure;
• Memory management;
• Bluetooth subsystem;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• NCSI (Network Controller Sideband Interface) driver;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AudioScience HPI driver;
• KVM core; (CVE-2024-47709, CVE-2024-49889, CVE-2024-49931, CVE-2024-50008, CVE-2024-49969, CVE-2024-49975, CVE-2024-49958, CVE-2024-47756, CVE-2024-49944, CVE-2024-47707, CVE-2024-47693, CVE-2024-47686, CVE-2024-47734, CVE-2024-47750, CVE-2024-50179, CVE-2024-49942, CVE-2024-49864, CVE-2024-49891, CVE-2024-49965, CVE-2024-49905, CVE-2024-47719, CVE-2024-49877, CVE-2024-47688, CVE-2024-47691, CVE-2024-47710, CVE-2024-47748, CVE-2024-49948, CVE-2024-49998, CVE-2024-47673, CVE-2024-47738, CVE-2024-47701, CVE-2024-47705, CVE-2024-49930, CVE-2024-49985, CVE-2024-50016, CVE-2024-53144, CVE-2023-52917, CVE-2024-47690, CVE-2024-47675, CVE-2024-50176, CVE-2024-49922, CVE-2024-47704, CVE-2024-49982, CVE-2024-47741, CVE-2024-49991, CVE-2024-49902, CVE-2024-49883, CVE-2024-49892, CVE-2024-50002, CVE-2024-49945, CVE-2024-49959, CVE-2024-47732, CVE-2024-49856, CVE-2024-47677, CVE-2024-49978, CVE-2024-49966, CVE-2024-49937, CVE-2024-47744, CVE-2024-49890, CVE-2024-47739, CVE-2024-50012, CVE-2024-47742, CVE-2024-49980, CVE-2024-47706, CVE-2024-49994, CVE-2024-50017, CVE-2024-47697, CVE-2024-49996, CVE-2024-49953, CVE-2024-49871, CVE-2024-47723, CVE-2024-49987, CVE-2024-49917, CVE-2024-49888, CVE-2024-49866, CVE-2024-50005, CVE-2024-47681, CVE-2024-49870, CVE-2024-49898, CVE-2024-49981, CVE-2024-49947, CVE-2024-49918, CVE-2024-49983, CVE-2024-47698, CVE-2024-49850, CVE-2024-50007, CVE-2024-49900, CVE-2024-49923, CVE-2024-49909, CVE-2024-47687, CVE-2024-50015, CVE-2024-47715, CVE-2024-47745, CVE-2024-49926, CVE-2024-49879, CVE-2024-49986, CVE-2024-49929, CVE-2024-49949, CVE-2024-49976, CVE-2024-47749, CVE-2024-47689, CVE-2024-47720, CVE-2024-47743, CVE-2024-49878, CVE-2024-49935, CVE-2024-49955, CVE-2024-49997, CVE-2024-49860, CVE-2024-47703, CVE-2024-50175, CVE-2024-49855, CVE-2024-49861, CVE-2024-49951, CVE-2024-49863, CVE-2024-49882, CVE-2024-50000, CVE-2024-49912, CVE-2024-49974, CVE-2024-49977, CVE-2024-47752, CVE-2024-47700, CVE-2024-49911,…

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• TPM device driver;
• Hardware crypto device drivers;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• USB Device Class drivers;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• SMB network file system;
• BPF subsystem;
• Virtio network driver;
• TCP network protocol;
• Perf events;
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Tracing infrastructure;
• Memory management;
• Bluetooth subsystem;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• NCSI (Network Controller Sideband Interface) driver;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Wireless networking;
• AudioScience HPI driver;
• KVM core; (CVE-2024-47678, CVE-2024-49952, CVE-2024-47682, CVE-2024-47679, CVE-2024-47748, CVE-2024-47728, CVE-2024-49953, CVE-2024-49883, CVE-2024-47742, CVE-2024-50000, CVE-2024-47733, CVE-2024-47752, CVE-2024-49927, CVE-2024-47713, CVE-2024-49853, CVE-2024-49998, CVE-2024-47672, CVE-2024-49900, CVE-2024-49884, CVE-2024-49876, CVE-2024-47673, CVE-2024-49958, CVE-2024-50274, CVE-2024-49980, CVE-2024-47703, CVE-2024-49891, CVE-2024-47716, CVE-2024-49903, CVE-2024-49868, CVE-2024-47699, CVE-2024-50015, CVE-2024-49896, CVE-2024-49867, CVE-2024-50016, CVE-2024-49862, CVE-2024-49947, CVE-2024-47714, CVE-2024-50179, CVE-2024-50006, CVE-2024-49881, CVE-2024-49933, CVE-2024-49882, CVE-2024-47709, CVE-2024-47686, CVE-2024-49859, CVE-2024-49992, CVE-2024-49957, CVE-2024-47691, CVE-2024-49936, CVE-2024-49878, CVE-2024-49879, CVE-2024-49997, CVE-2024-47697, CVE-2024-49963, CVE-2024-49938, CVE-2024-47723, CVE-2024-47700, CVE-2024-49999, CVE-2024-49923, CVE-2024-49991, CVE-2024-50013, CVE-2024-47730, CVE-2024-47718, CVE-2024-47671, CVE-2024-49977, CVE-2024-53144, CVE-2024-49922, CVE-2024-49985, CVE-2024-47712, CVE-2024-49962, CVE-2024-49907, CVE-2024-49886, CVE-2024-49976, CVE-2024-49902, CVE-2024-47732, CVE-2024-49995, CVE-2024-49942, CVE-2024-47706, CVE-2024-47747, CVE-2024-49949, CVE-2024-49911, CVE-2024-49929, CVE-2024-47737, CVE-2024-47720, CVE-2024-47756, CVE-2024-47688, CVE-2024-47753, CVE-2024-49937, CVE-2024-47684, CVE-2024-47690, CVE-2024-49897, CVE-2024-47705, CVE-2024-49852, CVE-2024-49930, CVE-2024-47681, CVE-2024-50175, CVE-2024-49863, CVE-2024-49969, CVE-2024-49894, CVE-2024-49928, CVE-2024-47698, CVE-2024-47710, CVE-2024-49931, CVE-2024-50008, CVE-2024-49939, CVE-2024-49915, CVE-2024-47757, CVE-2024-49912, CVE-2024-47696, CVE-2024-47702, CVE-2024-49877, CVE-2024-49974, CVE-2024-49919, CVE-2024-49888, CVE-2024-49871, CVE-2024-47685, CVE-2024-47734, CVE-2024-49965, CVE-2024-47707, CVE-2024-49987, CVE-2024-47745, CVE-2024-50001,…

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:

• ARM32 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• TPM device driver;
• Hardware crypto device drivers;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• I2C subsystem;
• I3C subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• USB Device Class drivers;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS file system;
• JFS file system;
• Network file systems library;
• Network file system (NFS) server daemon;
• NILFS2 file system;
• SMB network file system;
• BPF subsystem;
• Virtio network driver;
• TCP network protocol;
• Perf events;
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Tracing infrastructure;
• Memory management;
• Bluetooth subsystem;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• NCSI (Network Controller Sideband Interface) driver;
• Netfilter;
• RxRPC session sockets;
• Network traffic control;
• SCTP protocol;
• TIPC protocol;
• VMware vSockets driver;
• Wireless networking;
• AudioScience HPI driver;
• KVM core; (CVE-2024-49867, CVE-2024-47675, CVE-2024-49999, CVE-2024-49884, CVE-2024-49992, CVE-2024-49945, CVE-2024-49889, CVE-2024-49890, CVE-2024-49900, CVE-2024-49934, CVE-2024-49976, CVE-2024-49878, CVE-2024-50008, CVE-2024-49919, CVE-2024-47698, CVE-2024-47731, CVE-2024-47673, CVE-2024-49959, CVE-2024-47715, CVE-2024-49912, CVE-2024-47702, CVE-2024-50007, CVE-2024-49953, CVE-2024-49929, CVE-2024-47730, CVE-2024-49966, CVE-2024-47756, CVE-2024-47687, CVE-2024-50002, CVE-2024-49911, CVE-2024-47714, CVE-2024-47704, CVE-2024-50017, CVE-2024-47709, CVE-2024-49858, CVE-2024-47712, CVE-2024-49870, CVE-2024-49883, CVE-2024-47672, CVE-2024-49963, CVE-2024-49926, CVE-2024-49860, CVE-2024-47748, CVE-2024-49928, CVE-2024-49931, CVE-2024-47749, CVE-2024-49913, CVE-2024-49957, CVE-2024-49948, CVE-2024-47732, CVE-2024-47753, CVE-2024-47727, CVE-2024-49896, CVE-2024-47707, CVE-2024-47743, CVE-2024-49915, CVE-2024-47695, CVE-2024-49960, CVE-2024-49935, CVE-2024-49868, CVE-2024-49918, CVE-2024-49969, CVE-2024-53164, CVE-2024-49879, CVE-2024-50012, CVE-2024-50000, CVE-2024-49974, CVE-2024-49998, CVE-2024-49933, CVE-2024-47733, CVE-2024-49924, CVE-2024-47757, CVE-2024-47699, CVE-2024-49983, CVE-2024-50016, CVE-2024-49907, CVE-2024-49965, CVE-2024-49859, CVE-2024-50013, CVE-2024-49871, CVE-2024-49994, CVE-2024-49850, CVE-2024-49947, CVE-2024-49955, CVE-2024-49962, CVE-2024-47692, CVE-2024-53141, CVE-2024-50014, CVE-2024-47689, CVE-2024-49874, CVE-2024-50005, CVE-2024-47741, CVE-2024-49880, CVE-2024-47738, CVE-2024-47745, CVE-2024-49917, CVE-2024-47728, CVE-2024-49856, CVE-2024-49925, CVE-2024-47671, CVE-2023-52917, CVE-2024-47679, CVE-2024-49975, CVE-2024-47734, CVE-2024-47720, CVE-2024-47686, CVE-2024-49892, CVE-2024-49936, CVE-2024-49888, CVE-2024-49909, CVE-2024-49986, CVE-2024-49930, CVE-2024-47740, CVE-2024-49923, CVE-2024-47754, CVE-2024-50179, CVE-2024-49978, CVE-2024-47735,…

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:

• ARM32 architecture;
• ARM64 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• TPM device driver;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• Parport drivers;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• Pin controllers subsystem;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• Direct Digital Synthesis drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• TI TPS6598x USB Power Delivery controller driver;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS 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;
• SMB network file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Virtio network driver;
• Network traffic control;
• Network sockets;
• TCP network protocol;
• User-space API (UAPI);
• io_uring subsystem;
• Perf events;
• Kernel thread helper (kthread);
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Maple Tree data structure library;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• NCSI (Network Controller Sideband Interface) driver;
• Netfilter;
• Netlink;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• AudioScience HPI driver;
• KVM core; (CVE-2024-49994, CVE-2024-47740, CVE-2024-49936, CVE-2024-47716, CVE-2024-47733, CVE-2024-50075, CVE-2024-49870, CVE-2024-50007, CVE-2024-49897, CVE-2024-49915, CVE-2024-47756, CVE-2024-47700,…

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:

• ARM32 architecture;
• ARM64 architecture;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• TPM device driver;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• Parport drivers;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• Pin controllers subsystem;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• Direct Digital Synthesis drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• TI TPS6598x USB Power Delivery controller driver;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS 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;
• SMB network file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Virtio network driver;
• Network traffic control;
• Network sockets;
• TCP network protocol;
• User-space API (UAPI);
• io_uring subsystem;
• Perf events;
• Kernel thread helper (kthread);
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Maple Tree data structure library;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• NCSI (Network Controller Sideband Interface) driver;
• Netfilter;
• Netlink;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• AudioScience HPI driver;
• KVM core; (CVE-2024-49994, CVE-2024-47740, CVE-2024-49936, CVE-2024-47716, CVE-2024-47733, CVE-2024-50075, CVE-2024-49870, CVE-2024-50007, CVE-2024-49897, CVE-2024-49915, CVE-2024-47756, CVE-2024-47700,…

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)

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• TPM device driver;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• Parport drivers;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• Pin controllers subsystem;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• Direct Digital Synthesis drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• TI TPS6598x USB Power Delivery controller driver;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS 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;
• SMB network file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Virtio network driver;
• Network traffic control;
• Network sockets;
• TCP network protocol;
• User-space API (UAPI);
• io_uring subsystem;
• Perf events;
• Kernel thread helper (kthread);
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Maple Tree data structure library;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• NCSI (Network Controller Sideband Interface) driver;
• Netfilter;
• Netlink;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• AudioScience HPI driver;
• KVM core; (CVE-2024-49927, CVE-2024-47719, CVE-2024-49878, CVE-2024-50200, CVE-2024-50013, CVE-2024-50187, CVE-2024-49852, CVE-2024-49913, CVE-2024-50080, CVE-2024-49903, CVE-2024-47745, CVE-2024-50184, CVE-2024-50117, CVE-2024-49863, CVE-2024-49973, CVE-2024-47727, CVE-2024-53170, CVE-2024-49933, CVE-2024-49900, CVE-2024-50095, CVE-2024-49928, CVE-2024-49858, CVE-2024-47731, CVE-2024-49896, CVE-2024-53104, CVE-2024-49972,…

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)

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• TPM device driver;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• Parport drivers;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• Pin controllers subsystem;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• Direct Digital Synthesis drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• TI TPS6598x USB Power Delivery controller driver;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS 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;
• SMB network file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Virtio network driver;
• Network traffic control;
• Network sockets;
• TCP network protocol;
• User-space API (UAPI);
• io_uring subsystem;
• Perf events;
• Kernel thread helper (kthread);
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Maple Tree data structure library;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• NCSI (Network Controller Sideband Interface) driver;
• Netfilter;
• Netlink;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• AudioScience HPI driver;
• KVM core; (CVE-2024-49952, CVE-2024-49920, CVE-2024-49945, CVE-2024-50180, CVE-2024-49944, CVE-2024-49987, CVE-2024-50148, CVE-2024-49959, CVE-2024-50063, CVE-2024-50083, CVE-2024-49878, CVE-2024-49870, CVE-2024-49863, CVE-2024-49921, CVE-2024-49992, CVE-2024-47691, CVE-2024-49913, CVE-2024-47712, CVE-2024-49948, CVE-2024-49976, CVE-2024-50085, CVE-2024-49891, CVE-2024-56614, CVE-2024-47713, CVE-2024-47703, CVE-2024-50191,…

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)

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;
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• ACPI drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• Network block device driver;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• TPM device driver;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• DAX dirext access to differentiated memory framework;
• ARM SCMI message protocol;
• EFI core;
• GPU drivers;
• HID subsystem;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Mailbox framework;
• Media drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• NTB driver;
• Virtio pmem driver;
• Parport drivers;
• PCI subsystem;
• Alibaba DDR Sub-System Driveway PMU driver;
• Pin controllers subsystem;
• x86 platform drivers;
• Powercap sysfs driver;
• Remote Processor subsystem;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• Direct Digital Synthesis drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB Device Class drivers;
• USB Gadget drivers;
• USB Host Controller drivers;
• TI TPS6598x USB Power Delivery controller driver;
• vDPA drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• AFS file system;
• BTRFS file system;
• File systems infrastructure;
• Ceph distributed file system;
• Ext4 file system;
• F2FS 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;
• SMB network file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Virtio network driver;
• Network namespace;
• Network traffic control;
• Network sockets;
• TCP network protocol;
• User-space API (UAPI);
• io_uring subsystem;
• Perf events;
• Kernel thread helper (kthread);
• Padata parallel execution mechanism;
• RCU subsystem;
• Arbitrary resource management;
• Static call mechanism;
• Timer subsystem;
• Tracing infrastructure;
• Maple Tree data structure library;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• CAN network layer;
• Networking core;
• Distributed Switch Architecture;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• NCSI (Network Controller Sideband Interface) driver;
• Netfilter;
• Netlink;
• RxRPC session sockets;
• SCTP protocol;
• TIPC protocol;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path;
• AudioScience HPI driver;
• KVM core; (CVE-2024-49950, CVE-2024-49955, CVE-2024-50077, CVE-2024-57798, CVE-2024-47671, CVE-2024-49987, CVE-2024-50078, CVE-2024-49985, CVE-2024-49981, CVE-2024-49852, CVE-2024-49882, CVE-2024-49925, CVE-2024-50047, CVE-2024-47752, CVE-2024-49851, CVE-2024-50229, CVE-2024-47675, CVE-2024-50017, CVE-2024-47726, CVE-2024-50008, CVE-2024-49889, CVE-2024-50059, CVE-2024-53144, CVE-2024-49959, CVE-2024-49886,…