CVE-2024-50066

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

mm/mremap: fix move_normal_pmd/retract_page_tables race

In mremap(), move_page_tables() looks at the type of the PMD entry and the specified address range to figure out by which method the next chunk of page table entries should be moved.

At that point, the mmap_lock is held in write mode, but no rmap locks are held yet. For PMD entries that point to page tables and are fully covered by the source address range, move_pgt_entry(NORMAL_PMD, ...) is called, which first takes rmap locks, then does move_normal_pmd(). move_normal_pmd() takes the necessary page table locks at source and destination, then moves an entire page table from the source to the destination.

The problem is: The rmap locks, which protect against concurrent page table removal by retract_page_tables() in the THP code, are only taken after the PMD entry has been read and it has been decided how to move it. So we can race as follows (with two processes that have mappings of the same tmpfs file that is stored on a tmpfs mount with huge=advise); note that process A accesses page tables through the MM while process B does it through the file rmap:

process A process B ========= ========= mremap mremap_to move_vma move_page_tables get_old_pmd alloc_new_pmd *** PREEMPT *** madvise(MADV_COLLAPSE) do_madvise madvise_walk_vmas madvise_vma_behavior madvise_collapse hpage_collapse_scan_file collapse_file retract_page_tables i_mmap_lock_read(mapping) pmdp_collapse_flush i_mmap_unlock_read(mapping) move_pgt_entry(NORMAL_PMD, ...) take_rmap_locks move_normal_pmd drop_rmap_locks

When this happens, move_normal_pmd() can end up creating bogus PMD entries in the line pmd_populate(mm, new_pmd, pmd_pgtable(pmd)). The effect depends on arch-specific and machine-specific details; on x86, you can end up with physical page 0 mapped as a page table, which is likely exploitable for user->kernel privilege escalation.

Fix the race by letting process B recheck that the PMD still points to a page table after the rmap locks have been taken. Otherwise, we bail and let the caller fall back to the PTE-level copying path, which will then bail immediately at the pmd_none() check.

Bug reachability: Reaching this bug requires that you can create shmem/file THP mappings - anonymous THP uses different code that doesn't zap stuff under rmap locks. File THP is gated on an experimental config flag (CONFIG_READ_ONLY_THP_FOR_FS), so on normal distro kernels you need shmem THP to hit this bug. As far as I know, getting shmem THP normally requires that you can mount your own tmpfs with the right mount flags, which would require creating your own user+mount namespace; though I don't know if some distros maybe enable shmem THP by default or something like that.

Bug impact: This issue can likely be used for user->kernel privilege escalation when it is reachable.

In the Linux kernel, the following vulnerability has been resolved: mm/mremap: fix move_normal_pmd/retract_page_tables race In mremap(), move_page_tables() looks at the type of the PMD entry and the specified address range to figure out by which method the next chunk of page table entries should be moved. At that point, the mmap_lock is held in write mode, but no rmap locks are held yet. For PMD entries that point to page tables and are fully covered by the source address range, move_pgt_entry(NORMAL_PMD, ...) is called, which first takes rmap locks, then does move_normal_pmd(). move_normal_pmd() takes the necessary page table locks at source and destination, then moves an entire page table from the source to the destination. The problem is: The rmap locks, which protect against concurrent page table removal by retract_page_tables() in the THP code, are only taken after the PMD entry has been read and it has been decided how to move it. So we can race as follows (with two processes that have mappings of the same tmpfs file that is stored on a tmpfs mount with huge=advise); note that process A accesses page tables through the MM while process B does it through the file rmap: process A process B ========= ========= mremap mremap_to move_vma move_page_tables get_old_pmd alloc_new_pmd *** PREEMPT *** madvise(MADV_COLLAPSE) do_madvise madvise_walk_vmas madvise_vma_behavior madvise_collapse hpage_collapse_scan_file collapse_file retract_page_tables i_mmap_lock_read(mapping) pmdp_collapse_flush i_mmap_unlock_read(mapping) move_pgt_entry(NORMAL_PMD, ...) take_rmap_locks move_normal_pmd drop_rmap_locks When this happens, move_normal_pmd() can end up creating bogus PMD entries in the line pmd_populate(mm, new_pmd, pmd_pgtable(pmd)). The effect depends on arch-specific and machine-specific details; on x86, you can end up with physical page 0 mapped as a page table, which is likely exploitable for user->kernel privilege escalation. Fix the race by letting process B recheck that the PMD still points to a page table after the rmap locks have been taken. Otherwise, we bail and let the caller fall back to the PTE-level copying path, which will then bail immediately at the pmd_none() check. Bug reachability: Reaching this bug requires that you can create shmem/file THP mappings - anonymous THP uses different code that doesn't zap stuff under rmap locks. File THP is gated on an experimental config flag (CONFIG_READ_ONLY_THP_FOR_FS), so on normal distro kernels you need shmem THP to hit this bug. As far as I know, getting shmem THP normally requires that you can mount your own tmpfs with the right mount flags, which would require creating your own user+mount namespace; though I don't know if some distros maybe enable shmem THP by default or something like that. Bug impact: This issue can likely be used for user->kernel privilege escalation when it is reachable.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

drm/amd/display: Add NULL pointer check for kzalloc

[Why & How] Check return pointer of kzalloc before using it.(CVE-2024-42122)

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

mm: gup: stop abusing try_grab_folio

A kernel warning was reported when pinning folio in CMA memory when launching SEV virtual machine. The splat looks like:

[ 464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520 [ 464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6 [ 464.325477] RIP: 0010:__get_user_pages+0x423/0x520 [ 464.325515] Call Trace: [ 464.325520] <TASK> [ 464.325523] ? __get_user_pages+0x423/0x520 [ 464.325528] ? __warn+0x81/0x130 [ 464.325536] ? __get_user_pages+0x423/0x520 [ 464.325541] ? report_bug+0x171/0x1a0 [ 464.325549] ? handle_bug+0x3c/0x70 [ 464.325554] ? exc_invalid_op+0x17/0x70 [ 464.325558] ? asm_exc_invalid_op+0x1a/0x20 [ 464.325567] ? __get_user_pages+0x423/0x520 [ 464.325575] __gup_longterm_locked+0x212/0x7a0 [ 464.325583] internal_get_user_pages_fast+0xfb/0x190 [ 464.325590] pin_user_pages_fast+0x47/0x60 [ 464.325598] sev_pin_memory+0xca/0x170 [kvm_amd] [ 464.325616] sev_mem_enc_register_region+0x81/0x130 [kvm_amd]

Per the analysis done by yangge, when starting the SEV virtual machine, it will call pin_user_pages_fast(..., FOLL_LONGTERM, ...) to pin the memory. But the page is in CMA area, so fast GUP will fail then fallback to the slow path due to the longterm pinnalbe check in try_grab_folio().

The slow path will try to pin the pages then migrate them out of CMA area. But the slow path also uses try_grab_folio() to pin the page, it will also fail due to the same check then the above warning is triggered.

In addition, the try_grab_folio() is supposed to be used in fast path and it elevates folio refcount by using add ref unless zero. We are guaranteed to have at least one stable reference in slow path, so the simple atomic add could be used. The performance difference should be trivial, but the misuse may be confusing and misleading.

Redefined try_grab_folio() to try_grab_folio_fast(), and try_grab_page() to try_grab_folio(), and use them in the proper paths. This solves both the abuse and the kernel warning.

The proper naming makes their usecase more clear and should prevent from abusing in the future.

peterx said:

: The user will see the pin fails, for gpu-slow it further triggers the WARN : right below that failure (as in the original report): : : folio = try_grab_folio(page, page_increm - 1, : foll_flags); : if (WARN_ON_ONCE(!folio)) { <------------------------ here : /* : * Release the 1st page ref if the : * folio is problematic, fail hard. : */ : gup_put_folio(page_folio(page), 1, : foll_flags); : ret = -EFAULT; : goto out; : }

[1] https://lore.kernel.org/linux-mm/[email protected]/

[[email protected]: fix implicit declaration of function try_grab_folio_fast] Link: https://lkml.kernel.org/r/CAHbLzkowMSso-4Nufc9hcMehQsK9PNz3OSu-+eniU-2Mm-xjhA@mail.gmail.com(CVE-2024-44943)

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

serial: sc16is7xx: fix TX fifo corruption

Sometimes, when a packet is received on channel A at almost the same time as a packet is about to be transmitted on channel B, we observe with a logic analyzer that the received packet on channel A is transmitted on channel B. In other words, the Tx buffer data on channel B is corrupted with data from channel A.

The problem appeared since commit…

In the Linux kernel, the following vulnerability has been resolved: mm/mremap: fix move_normal_pmd/retract_page_tables race In mremap(), move_page_tables() looks at the type of the PMD entry and the specified address range to figure out by which method the next chunk of page table entries should be moved. At that point, the mmap_lock is held in write mode, but no rmap locks are held yet. For PMD entries that point to page tables and are fully covered by the source address range, move_pgt_entry(NORMAL_PMD, ...) is called, which first takes rmap locks, then does move_normal_pmd(). move_normal_pmd() takes the necessary page table locks at source and destination, then moves an entire page table from the source to the destination. The problem is: The rmap locks, which protect against concurrent page table removal by retract_page_tables() in the THP code, are only taken after the PMD entry has been read and it has been decided how to move it. So we can race as follows (with two processes that have mappings of the same tmpfs file that is stored on a tmpfs mount with huge=advise); note that process A accesses page tables through the MM while process B does it through the file rmap: process A process B ========= ========= mremap mremap_to move_vma move_page_tables get_old_pmd alloc_new_pmd *** PREEMPT *** madvise(MADV_COLLAPSE) do_madvise madvise_walk_vmas madvise_vma_behavior madvise_collapse hpage_collapse_scan_file collapse_file retract_page_tables i_mmap_lock_read(mapping) pmdp_collapse_flush i_mmap_unlock_read(mapping) move_pgt_entry(NORMAL_PMD, ...) take_rmap_locks move_normal_pmd drop_rmap_locks When this happens, move_normal_pmd() can end up creating bogus PMD entries in the line pmd_populate(mm, new_pmd, pmd_pgtable(pmd)). The effect depends on arch-specific and machine-specific details; on x86, you can end up with physical page 0 mapped as a page table, which is likely exploitable for user->kernel privilege escalation. Fix the race by letting process B recheck that the PMD still points to a page table after the rmap locks have been taken. Otherwise, we bail and let the caller fall back to the PTE-level copying path, which will then bail immediately at the pmd_none() check. Bug reachability: Reaching this bug requires that you can create shmem/file THP mappings - anonymous THP uses different code that doesn't zap stuff under rmap locks. File THP is gated on an experimental config flag (CONFIG_READ_ONLY_THP_FOR_FS), so on normal distro kernels you need shmem THP to hit this bug. As far as I know, getting shmem THP normally requires that you can mount your own tmpfs with the right mount flags, which would require creating your own user+mount namespace; though I don't know if some distros maybe enable shmem THP by default or something like that. Bug impact: This issue can likely be used for user->kernel privilege escalation when it is reachable.

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

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

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;
• 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;
• x86 architecture;
• Block layer subsystem;
• Drivers core;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• CPU frequency scaling framework;
• DAX dirext access to differentiated memory framework;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Network drivers;
• NTB driver;
• Virtio pmem driver;
• Parport drivers;
• Pin controllers subsystem;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• Direct Digital Synthesis drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• TI TPS6598x USB Power Delivery controller driver;
• Framebuffer layer;
• BTRFS file system;
• Ext4 file system;
• F2FS file system;
• Network file system (NFS) client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Network traffic control;
• Network sockets;
• User-space API (UAPI);
• io_uring subsystem;
• Kernel thread helper (kthread);
• RCU subsystem;
• Timer subsystem;
• Maple Tree data structure library;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• Networking core;
• IPv4 networking;
• Multipath TCP;
• Netfilter;
• Netlink;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path; (CVE-2024-50182, CVE-2024-50020, CVE-2024-50060, CVE-2024-50074, CVE-2024-50193, CVE-2024-50117, CVE-2024-50201, CVE-2024-50033, CVE-2024-50056, CVE-2024-50026, CVE-2024-50059, CVE-2024-50041, CVE-2024-50083, CVE-2024-50038, CVE-2024-50229, CVE-2024-50028, CVE-2024-50183, CVE-2024-50196, CVE-2024-50029, CVE-2024-50093, CVE-2024-50188, CVE-2024-50025, CVE-2024-50200, CVE-2024-50068, CVE-2024-49920, CVE-2024-50198, CVE-2024-50035, CVE-2024-50042, CVE-2024-50023, CVE-2024-50047, CVE-2024-56582, CVE-2024-50090, CVE-2024-50062, CVE-2024-50073, CVE-2024-50063, CVE-2024-50098, CVE-2024-50197, CVE-2024-50040, CVE-2024-50180, CVE-2024-53170, CVE-2024-50087, CVE-2024-50031, CVE-2024-50202, CVE-2024-50058, CVE-2024-50186, CVE-2024-50134, CVE-2024-50194, CVE-2024-50075, CVE-2024-50046, CVE-2024-50078, CVE-2024-50066, CVE-2024-53156, CVE-2024-49893, CVE-2024-50021, CVE-2024-47711, CVE-2024-47726, CVE-2024-50024, CVE-2024-49865, CVE-2024-50064, CVE-2024-50049, CVE-2024-50171, CVE-2024-50019, CVE-2024-50077, CVE-2024-50199, CVE-2024-50072, CVE-2024-50069, CVE-2024-50048, CVE-2024-49972, CVE-2024-53165, CVE-2024-50022, CVE-2024-50084, CVE-2024-50185, CVE-2024-50055, CVE-2024-50187, CVE-2024-50009, CVE-2024-50082, CVE-2024-50085, CVE-2024-50095, CVE-2024-50195, CVE-2024-50080, CVE-2024-50076, CVE-2024-50088, CVE-2024-50039, CVE-2024-50044, CVE-2024-50030, CVE-2024-49968, CVE-2024-50148, CVE-2024-50192, CVE-2024-50032, CVE-2024-50061, CVE-2024-50233, CVE-2024-50099, CVE-2024-49921, CVE-2024-50184, CVE-2024-50065, CVE-2024-49914, CVE-2024-50027, CVE-2024-50070, CVE-2024-50086, CVE-2024-50189, CVE-2024-56614, CVE-2024-50057, CVE-2024-50096, CVE-2024-50045, CVE-2024-50036, CVE-2024-56663, CVE-2024-50191, CVE-2024-50101)

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;
• x86 architecture;
• Block layer subsystem;
• Drivers core;
• Ublk userspace block driver;
• Compressed RAM block device driver;
• CPU frequency scaling framework;
• DAX dirext access to differentiated memory framework;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Network drivers;
• NTB driver;
• Virtio pmem driver;
• Parport drivers;
• Pin controllers subsystem;
• SCSI subsystem;
• SuperH / SH-Mobile drivers;
• Direct Digital Synthesis drivers;
• Thermal drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• TI TPS6598x USB Power Delivery controller driver;
• Framebuffer layer;
• BTRFS file system;
• Ext4 file system;
• F2FS file system;
• Network file system (NFS) client;
• NILFS2 file system;
• NTFS3 file system;
• SMB network file system;
• BPF subsystem;
• Network file system (NFS) superblock;
• Network traffic control;
• Network sockets;
• User-space API (UAPI);
• io_uring subsystem;
• Kernel thread helper (kthread);
• RCU subsystem;
• Timer subsystem;
• Maple Tree data structure library;
• Memory management;
• Bluetooth subsystem;
• Ethernet bridge;
• Networking core;
• IPv4 networking;
• Multipath TCP;
• Netfilter;
• Netlink;
• Unix domain sockets;
• Wireless networking;
• eXpress Data Path; (CVE-2024-50182, CVE-2024-50020, CVE-2024-50060, CVE-2024-50074, CVE-2024-50193, CVE-2024-50117, CVE-2024-50201, CVE-2024-50033, CVE-2024-50056, CVE-2024-50026, CVE-2024-50059, CVE-2024-50041, CVE-2024-50083, CVE-2024-50038, CVE-2024-50229, CVE-2024-50028, CVE-2024-50183, CVE-2024-50196, CVE-2024-50029, CVE-2024-50093, CVE-2024-50188, CVE-2024-50025, CVE-2024-50200, CVE-2024-50068, CVE-2024-49920, CVE-2024-50198, CVE-2024-50035, CVE-2024-50042, CVE-2024-50023, CVE-2024-50047, CVE-2024-56582, CVE-2024-50090, CVE-2024-50062, CVE-2024-50073, CVE-2024-50063, CVE-2024-50098, CVE-2024-50197, CVE-2024-50040, CVE-2024-50180, CVE-2024-53170, CVE-2024-50087, CVE-2024-50031, CVE-2024-50202, CVE-2024-50058, CVE-2024-50186, CVE-2024-50134, CVE-2024-50194, CVE-2024-50075, CVE-2024-50046, CVE-2024-50078, CVE-2024-50066, CVE-2024-53156, CVE-2024-49893, CVE-2024-50021, CVE-2024-47711, CVE-2024-47726, CVE-2024-50024, CVE-2024-49865, CVE-2024-50064, CVE-2024-50049, CVE-2024-50171, CVE-2024-50019, CVE-2024-50077, CVE-2024-50199, CVE-2024-50072, CVE-2024-50069, CVE-2024-50048, CVE-2024-49972, CVE-2024-53165, CVE-2024-50022, CVE-2024-50084, CVE-2024-50185, CVE-2024-50055, CVE-2024-50187, CVE-2024-50009, CVE-2024-50082, CVE-2024-50085, CVE-2024-50095, CVE-2024-50195, CVE-2024-50080, CVE-2024-50076, CVE-2024-50088, CVE-2024-50039, CVE-2024-50044, CVE-2024-50030, CVE-2024-49968, CVE-2024-50148, CVE-2024-50192, CVE-2024-50032, CVE-2024-50061, CVE-2024-50233, CVE-2024-50099, CVE-2024-49921, CVE-2024-50184, CVE-2024-50065, CVE-2024-49914, CVE-2024-50027, CVE-2024-50070, CVE-2024-50086, CVE-2024-50189, CVE-2024-56614, CVE-2024-50057, CVE-2024-50096, CVE-2024-50045, CVE-2024-50036, CVE-2024-56663, CVE-2024-50191, CVE-2024-50101)

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

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

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