CVE-2024-49859

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

f2fs: fix to check atomic_file in f2fs ioctl interfaces

Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check atomic_file in f2fs ioctl interfaces Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.

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…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)

In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc->ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It's not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev->descs variable.(CVE-2022-48975)

In the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table's kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)

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

memcg_write_event_control(): fix a user-triggerable oops

we are not guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).(CVE-2024-45021)

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

gtp: fix a potential NULL pointer dereference

When sockfd_lookup() fails, gtp_encap_enable_socket() returns a NULL pointer, but its callers only check for error pointers thus miss the NULL pointer case.

Fix it by returning an error pointer with the error code carried from sockfd_lookup().

(I found this bug during code inspection.)(CVE-2024-46677)

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

drm/amd/display: Check BIOS images before it is used

BIOS images may fail to load and null checks…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)

In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc->ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It's not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev->descs variable.(CVE-2022-48975)

In the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table's kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)

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

memcg_write_event_control(): fix a user-triggerable oops

we are not guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).(CVE-2024-45021)

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

gtp: fix a potential NULL pointer dereference

When sockfd_lookup() fails, gtp_encap_enable_socket() returns a NULL pointer, but its callers only check for error pointers thus miss the NULL pointer case.

Fix it by returning an error pointer with the error code carried from sockfd_lookup().

(I found this bug during code inspection.)(CVE-2024-46677)

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

drm/amd/display: Check BIOS images before it is used

BIOS images may fail to load and null checks…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

pinctrl: single: fix potential NULL dereference in pcs_get_function()

pinmux_generic_get_function() can return NULL and the pointer 'function' was dereferenced without checking against NULL. Add checking of pointer 'function' in pcs_get_function().

Found by code review.(CVE-2024-46685)

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

thunderbolt: Mark XDomain as unplugged when router is removed

I noticed that when we do discrete host router NVM upgrade and it gets hot-removed from the PCIe side as a result of NVM firmware authentication, if there is another host connected with enabled paths we hang in tearing them down. This is due to fact that the Thunderbolt networking driver also tries to cleanup the paths and ends up blocking in tb_disconnect_xdomain_paths() waiting for the domain lock.

However, at this point we already cleaned the paths in tb_stop() so there is really no need for tb_disconnect_xdomain_paths() to do that anymore. Furthermore it already checks if the XDomain is unplugged and bails out early so take advantage of that and mark the XDomain as unplugged when we remove the parent router.(CVE-2024-46702)

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

drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]

[WHY & HOW] num_valid_sets needs to be checked to avoid a negative index when accessing reader_wm_sets[num_valid_sets - 1].

This fixes an OVERRUN issue reported by Coverity.(CVE-2024-46815)

In the Linux kernel, the following vulnerability has been resolved: vfs: fix race between evice_inodes() and find_inode()&iput() Hi, all Recently I noticed a bug[1] in btrfs, after digged it into and I believe it'a race in vfs. Let's assume there's a inode (ie ino 261) with i_count 1 is called by iput(), and there's a concurrent thread calling generic_shutdown_super(). cpu0: cpu1: iput() // i_count is 1 ->spin_lock(inode) ->dec i_count to 0 ->iput_final() generic_shutdown_super() ->__inode_add_lru() ->evict_inodes() // cause some reason[2] ->if (atomic_read(inode->i_count)) continue; // return before // inode 261 passed the above check // list_lru_add_obj() // and then schedule out ->spin_unlock() // note here: the inode 261 // was still at sb list and hash list, // and I_FREEING|I_WILL_FREE was not been set btrfs_iget() // after some function calls ->find_inode() // found the above inode 261 ->spin_lock(inode) // check I_FREEING|I_WILL_FREE // and passed ->__iget() ->spin_unlock(inode) // schedule back ->spin_lock(inode) // check (I_NEW|I_FREEING|I_WILL_FREE) flags, // passed and set I_FREEING iput() ->spin_unlock(inode) ->spin_lock(inode) ->evict() // dec i_count to 0 ->iput_final() ->spin_unlock() ->evict() Now, we have two threads simultaneously evicting the same inode, which may trigger the BUG(inode->i_state & I_CLEAR) statement both within clear_inode() and iput(). To fix the bug, recheck the inode->i_count after holding i_lock. Because in the most scenarios, the first check is valid, and the overhead of spin_lock() can be reduced. If there is any misunderstanding, please let me know, thanks. [1]: https://lore.kernel.org/linux-btrfs/[email protected]/ [2]: The reason might be 1. SB_ACTIVE was removed or 2. mapping_shrinkable() return false when I reproduced the bug.(CVE-2024-47679)

In the Linux…

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

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

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check atomic_file in f2fs ioctl interfaces Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.

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

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