CVE-2025-37899

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in session logoff The sess->user object can currently be in use by another thread, for example if another connection has sent a session setup request to bind to the session being free'd. The handler for that connection could be in the smb2_sess_setup function which makes use of sess->user.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

media: davinci: vpif: fix use-after-free on driver unbind

The driver allocates and registers two platform device structures during probe, but the devices were never deregistered on driver unbind.

This results in a use-after-free on driver unbind as the device structures were allocated using devres and would be freed by driver core when remove() returns.

Fix this by adding the missing deregistration calls to the remove() callback and failing probe on registration errors.

Note that the platform device structures must be freed using a proper release callback to avoid leaking associated resources like device names.(CVE-2021-47653)

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

mmc: core: use sysfs_emit() instead of sprintf()

sprintf() (still used in the MMC core for the sysfs output) is vulnerable to the buffer overflow. Use the new-fangled sysfs_emit() instead.

Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.(CVE-2022-49267)

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

Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event

We should not access skb buffer data anymore after hci_recv_frame was called.

[ 39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0 [ 39.634855] Read of size 1 at addr ffffff80cf28a60d by task kworker [ 39.634962] Call trace: [ 39.634974] dump_backtrace+0x0/0x3b8 [ 39.634999] show_stack+0x20/0x2c [ 39.635016] dump_stack_lvl+0x60/0x78 [ 39.635040] print_address_description+0x70/0x2f0 [ 39.635062] kasan_report+0x154/0x194 [ 39.635079] __asan_report_load1_noabort+0x44/0x50 [ 39.635099] btmtksdio_recv_event+0x1b0/0x1c4 [ 39.635129] btmtksdio_txrx_work+0x6cc/0xac4 [ 39.635157] process_one_work+0x560/0xc5c [ 39.635177] worker_thread+0x7ec/0xcc0 [ 39.635195] kthread+0x2d0/0x3d0 [ 39.635215] ret_from_fork+0x10/0x20 [ 39.635247] Allocated by task 0: [ 39.635260] (stack is not available) [ 39.635281] Freed by task 2392: [ 39.635295] kasan_save_stack+0x38/0x68 [ 39.635319] kasan_set_track+0x28/0x3c [ 39.635338] kasan_set_free_info+0x28/0x4c [ 39.635357] ____kasan_slab_free+0x104/0x150 [ 39.635374] __kasan_slab_free+0x18/0x28 [ 39.635391] slab_free_freelist_hook+0x114/0x248 [ 39.635410] kfree+0xf8/0x2b4 [ 39.635427] skb_free_head+0x58/0x98 [ 39.635447] skb_release_data+0x2f4/0x410 [ 39.635464] skb_release_all+0x50/0x60 [ 39.635481] kfree_skb+0xc8/0x25c [ 39.635498] hci_event_packet+0x894/0xca4 [bluetooth] [ 39.635721] hci_rx_work+0x1c8/0x68c [bluetooth] [ 39.635925] process_one_work+0x560/0xc5c [ 39.635951] worker_thread+0x7ec/0xcc0 [ 39.635970] kthread+0x2d0/0x3d0 [ 39.635990] ret_from_fork+0x10/0x20 [ 39.636021] The buggy address belongs to the object at ffffff80cf28a600 which belongs to the cache kmalloc-512 of size 512 [ 39.636039] The buggy address is located 13 bytes inside of 512-byte region [ffffff80cf28a600, ffffff80cf28a800)(CVE-2022-49470)

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

Bluetooth: L2CAP: Fix use-after-free

Fix potential use-after-free in l2cap_le_command_rej.(CVE-2023-53305)

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

ip6mr: Fix skb_under_panic in ip6mr_cache_report()

skbuff: skb_under_panic: text:ffffffff88771f69 len:56 put:-4 head:ffff88805f86a800 data:ffff887f5f86a850 tail:0x88 end:0x2c0 dev:pim6reg ------------[ cut here ]------------ kernel BUG at net/core/skbuff.c:192! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 2 PID: 22968 Comm: kworker/2:11 Not tainted 6.5.0-rc3-00044-g0a8db05b571a #236 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP:…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

media: davinci: vpif: fix use-after-free on driver unbind

The driver allocates and registers two platform device structures during probe, but the devices were never deregistered on driver unbind.

This results in a use-after-free on driver unbind as the device structures were allocated using devres and would be freed by driver core when remove() returns.

Fix this by adding the missing deregistration calls to the remove() callback and failing probe on registration errors.

Note that the platform device structures must be freed using a proper release callback to avoid leaking associated resources like device names.(CVE-2021-47653)

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

mmc: core: use sysfs_emit() instead of sprintf()

sprintf() (still used in the MMC core for the sysfs output) is vulnerable to the buffer overflow. Use the new-fangled sysfs_emit() instead.

Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.(CVE-2022-49267)

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

Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event

We should not access skb buffer data anymore after hci_recv_frame was called.

[ 39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0 [ 39.634855] Read of size 1 at addr ffffff80cf28a60d by task kworker [ 39.634962] Call trace: [ 39.634974] dump_backtrace+0x0/0x3b8 [ 39.634999] show_stack+0x20/0x2c [ 39.635016] dump_stack_lvl+0x60/0x78 [ 39.635040] print_address_description+0x70/0x2f0 [ 39.635062] kasan_report+0x154/0x194 [ 39.635079] __asan_report_load1_noabort+0x44/0x50 [ 39.635099] btmtksdio_recv_event+0x1b0/0x1c4 [ 39.635129] btmtksdio_txrx_work+0x6cc/0xac4 [ 39.635157] process_one_work+0x560/0xc5c [ 39.635177] worker_thread+0x7ec/0xcc0 [ 39.635195] kthread+0x2d0/0x3d0 [ 39.635215] ret_from_fork+0x10/0x20 [ 39.635247] Allocated by task 0: [ 39.635260] (stack is not available) [ 39.635281] Freed by task 2392: [ 39.635295] kasan_save_stack+0x38/0x68 [ 39.635319] kasan_set_track+0x28/0x3c [ 39.635338] kasan_set_free_info+0x28/0x4c [ 39.635357] ____kasan_slab_free+0x104/0x150 [ 39.635374] __kasan_slab_free+0x18/0x28 [ 39.635391] slab_free_freelist_hook+0x114/0x248 [ 39.635410] kfree+0xf8/0x2b4 [ 39.635427] skb_free_head+0x58/0x98 [ 39.635447] skb_release_data+0x2f4/0x410 [ 39.635464] skb_release_all+0x50/0x60 [ 39.635481] kfree_skb+0xc8/0x25c [ 39.635498] hci_event_packet+0x894/0xca4 [bluetooth] [ 39.635721] hci_rx_work+0x1c8/0x68c [bluetooth] [ 39.635925] process_one_work+0x560/0xc5c [ 39.635951] worker_thread+0x7ec/0xcc0 [ 39.635970] kthread+0x2d0/0x3d0 [ 39.635990] ret_from_fork+0x10/0x20 [ 39.636021] The buggy address belongs to the object at ffffff80cf28a600 which belongs to the cache kmalloc-512 of size 512 [ 39.636039] The buggy address is located 13 bytes inside of 512-byte region [ffffff80cf28a600, ffffff80cf28a800)(CVE-2022-49470)

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

scsi: ufs: core: Fix handling of lrbp->cmd

ufshcd_queuecommand() may be called two times in a row for a SCSI command before it is completed. Hence make the following changes:

• In the functions that submit a command, do not check the old value of lrbp->cmd nor clear lrbp->cmd in error paths.

• In ufshcd_release_scsi_cmd(), do not clear lrbp->cmd.

See also scsi_send_eh_cmnd().

This commit prevents that the following appears if a command times out:

WARNING: at drivers/ufs/core/ufshcd.c:2965 ufshcd_queuecommand+0x6f8/0x9a8 Call trace: ufshcd_queuecommand+0x6f8/0x9a8 scsi_send_eh_cmnd+0x2c0/0x960 scsi_eh_test_devices+0x100/0x314 scsi_eh_ready_devs+0xd90/0x114c …

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

jfs: add check read-only before txBeginAnon() call

Added a read-only check before calling txBeginAnon in extAlloc and extRecord. This prevents modification attempts on a read-only mounted filesystem, avoiding potential errors or crashes.

Call trace: txBeginAnon+0xac/0x154 extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78 jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248 __block_write_begin_int+0x580/0x166c fs/buffer.c:2128 __block_write_begin fs/buffer.c:2177 [inline] block_write_begin+0x98/0x11c fs/buffer.c:2236 jfs_write_begin+0x44/0x88 fs/jfs/inode.c:299(CVE-2024-58095)

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

mm: zswap: properly synchronize freeing resources during CPU hotunplug

In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.

If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).

The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.

Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.

The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.

Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].

Alternative fixes that were considered/attempted and could have worked:

• Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
• Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.

[1]https://lkml.kernel.org/(CVE-2025-21693)

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

memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove

This fixes the following crash:

================================================================== BUG: KASAN: slab-use-after-free in rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms] Read of size 8 at addr ffff888136335380 by task kworker/6:0/140241

CPU: 6 UID: 0 PID: 140241 Comm: kworker/6:0 Kdump: loaded Tainted: G E 6.14.0-rc6+ #1 Tainted: [E]=UNSIGNED_MODULE Hardware name: LENOVO 30FNA1V7CW/1057, BIOS S0EKT54A 07/01/2024 Workqueue: events…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

nfc: nci: Fix uninit-value in nci_rx_work

syzbot reported the following uninit-value access issue [1]

nci_rx_work() parses received packet from ndev->rx_q. It should be validated header size, payload size and total packet size before processing the packet. If an invalid packet is detected, it should be silently discarded.(CVE-2024-38381)

In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)

In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)

In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — rmmod — insmod cycle the kerneloopses: max3100 spi-PRP0001:01: max3100_probe: adding port 0 BUG: kernel NULL pointer dereference, address: 0000000000000408 ... RIP: 0010:serial_core_register_port+0xa0/0x840 ... max3100_probe+0x1b6/0x280 [max3100] spi_probe+0x8d/0xb0Update the actual state so next time UART driver will be registeredagain.Hugo also noticed, that the error path in the probe also affectedby having the variable set, and not cleared. Instead of clearing itmove the assignment after the successfull uart_register_driver() call.(CVE-2024-38633)

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

enic: Validate length of nl attributes in enic_set_vf_port

enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE is of length PORT_PROFILE_MAX and that the nl attributes IFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX. These attributes are validated (in the function do_setlink in rtnetlink.c) using the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE as NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and IFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation using the policy is for the max size of the attributes and not on exact size so the length of these attributes might be less than the sizes that enic_set_vf_port expects. This might cause an out of bands read access in the memcpys of the data of these attributes in enic_set_vf_port.(CVE-2024-38659)

In the Linux kernel, the following vulnerability has been resolved:riscv: prevent pt_regs corruption for secondary idle threadsTop of the kernel thread stack should be reserved for pt_regs. Howeverthis is not the case for the idle threads of the secondary boot harts.Their stacks overlap with their pt_regs, so both may get corrupted.Similar issue has been fixed for the primary hart, see c7cdd96eca28( riscv: prevent stack corruption by reserving task_pt_regs(p) early ).However that fix was not propagated to the secondary harts. The problemhas been noticed in some CPU hotplug tests with V enabled. The functionsmp_callin stored several registers on stack, corrupting top of pt_regsstructure including status field. As a result, kernel attempted to saveor restore inexistent V context.(CVE-2024-38667)

In the Linux kernel, the following vulnerability has been resolved:jfs: xattr: fix buffer overflow for invalid xattrWhen an xattr size is not what is expected, it is printed out to thekernel log in hex format as a…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint

Patch series "nilfs2: fix null-ptr-deref bugs on block tracepoints".

This series fixes null pointer dereference bugs that occur when using nilfs2 and two block-related tracepoints.

This patch (of 2):

It has been reported that when using "block:block_touch_buffer" tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a NULL pointer dereference, or a general protection fault when KASAN is enabled.

This happens because since the tracepoint was added in touch_buffer(), it references the dev_t member bh->b_bdev->bd_dev regardless of whether the buffer head has a pointer to a block_device structure. In the current implementation, the block_device structure is set after the function returns to the caller.

Here, touch_buffer() is used to mark the folio/page that owns the buffer head as accessed, but the common search helper for folio/page used by the caller function was optimized to mark the folio/page as accessed when it was reimplemented a long time ago, eliminating the need to call touch_buffer() here in the first place.

So this solves the issue by eliminating the touch_buffer() call itself.(CVE-2024-53131)

In the Linux kernel, the following vulnerability has been resolved:drm: adv7511: Fix use-after-free in adv7533_attach_dsi()The host_node pointer was assigned and freed in adv7533_parse_dt(), andlater, adv7533_attach_dsi() uses the same. Fix this use-after-free issueby dropping of_node_put() in adv7533_parse_dt() and calling of_node_put()in error path of probe() and also in the remove().(CVE-2024-57887)

In the Linux kernel, the following vulnerability has been resolved:ila: serialize calls to nf_register_net_hooks()syzbot found a race in ila_add_mapping() [1]commit 031ae72825ce ( ila: call nf_unregister_net_hooks() sooner )attempted to fix a similar issue.Looking at the syzbot repro, we have concurrent ILA_CMD_ADD commands.Add a mutex to make sure at most one thread is calling nf_register_net_hooks().[1] BUG: KASAN: slab-use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline] BUG: KASAN: slab-use-after-free in __rhashtable_lookup.constprop.0+0x426/0x550 include/linux/rhashtable.h:604Read of size 4 at addr ffff888028f40008 by task dhcpcd/5501CPU: 1 UID: 0 PID: 5501 Comm: dhcpcd Not tainted 6.13.0-rc4-syzkaller-00054-gd6ef8b40d075 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024Call Trace: <IRQ> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xc3/0x620 mm/kasan/report.c:489 kasan_report+0xd9/0x110 mm/kasan/report.c:602 rht_key_hashfn include/linux/rhashtable.h:159 [inline] __rhashtable_lookup.constprop.0+0x426/0x550 include/linux/rhashtable.h:604 rhashtable_lookup include/linux/rhashtable.h:646 [inline] rhashtable_lookup_fast include/linux/rhashtable.h:672 [inline] ila_lookup_wildcards net/ipv6/ila/ila_xlat.c:127 [inline] ila_xlat_addr net/ipv6/ila/ila_xlat.c:652 [inline] ila_nf_input+0x1ee/0x620 net/ipv6/ila/ila_xlat.c:185 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xbb/0x200 net/netfilter/core.c:626 nf_hook.constprop.0+0x42e/0x750 include/linux/netfilter.h:269 NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0xa4/0x680 net/ipv6/ip6_input.c:309 __netif_receive_skb_one_core+0x12e/0x1e0 net/core/dev.c:5672 __netif_receive_skb+0x1d/0x160 net/core/dev.c:5785 process_backlog+0x443/0x15f0 net/core/dev.c:6117 __napi_poll.constprop.0+0xb7/0x550 net/core/dev.c:6883 napi_poll net/core/dev.c:6952 [inline] net_rx_action+0xa94/0x1010 net/core/dev.c:7074 handle_softirqs+0x213/0x8f0 kernel/softirq.c:561 __do_softirq kernel/softirq.c:595 [inline] …

Root has patched CVE-2025-37899 in the linux package for Root:Debian:12. Multiple fixed versions available.

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

Root has patched CVE-2025-37899 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in session logoff The sess->user object can currently be in use by another thread, for example if another connection has sent a session setup request to bind to the session being free'd. The handler for that connection could be in the smb2_sess_setup function which makes use of sess->user.

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;
• PA-RISC architecture;
• PowerPC architecture;
• S390 architecture;
• x86 architecture;
• Compute Acceleration Framework;
• Ublk userspace block driver;
• Bluetooth drivers;
• ARM SCMI message protocol;
• GPU drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Network drivers;
• PCI subsystem;
• PTP clock framework;
• SPI subsystem;
• BTRFS file system;
• SMB network file system;
• eXpress Data Path;
• Universal MIDI packet (UMP) support module;
• Tracing infrastructure;
• Memory management;
• IPv4 networking;
• IPv6 networking;
• Network traffic control;
• AMD SoC Alsa drivers;
• SoC Audio generic drivers; (CVE-2025-37898, CVE-2025-37990, CVE-2025-37974, CVE-2025-37991, CVE-2025-37894, CVE-2025-37906, CVE-2025-37896, CVE-2025-37909, CVE-2025-37923, CVE-2025-37899, CVE-2025-37901, CVE-2025-37914, CVE-2025-38216, CVE-2025-37931, CVE-2025-37928, CVE-2025-37916, CVE-2025-37908, CVE-2025-37915, CVE-2025-37917, CVE-2025-37921, CVE-2025-37903, CVE-2025-37922, CVE-2025-37895, CVE-2025-37936, CVE-2025-37933, CVE-2025-37891, CVE-2025-37926, CVE-2025-37912, CVE-2025-37920, CVE-2025-37924, CVE-2025-37927, CVE-2025-37946, CVE-2025-37907, CVE-2025-37930, CVE-2025-37911, CVE-2025-37905, CVE-2025-37900, CVE-2025-37929, CVE-2025-37910, CVE-2025-37913, CVE-2025-37935, CVE-2025-37919, CVE-2025-37918, CVE-2025-37897, CVE-2025-37904, CVE-2025-37934)

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;
• PA-RISC architecture;
• PowerPC architecture;
• S390 architecture;
• x86 architecture;
• Compute Acceleration Framework;
• Ublk userspace block driver;
• Bluetooth drivers;
• ARM SCMI message protocol;
• GPU drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Network drivers;
• PCI subsystem;
• PTP clock framework;
• SPI subsystem;
• BTRFS file system;
• SMB network file system;
• eXpress Data Path;
• Universal MIDI packet (UMP) support module;
• Tracing infrastructure;
• Memory management;
• IPv4 networking;
• IPv6 networking;
• Network traffic control;
• AMD SoC Alsa drivers;
• SoC Audio generic drivers; (CVE-2025-37974, CVE-2025-37931, CVE-2025-37990, CVE-2025-37921, CVE-2025-37917, CVE-2025-37908, CVE-2025-37906, CVE-2025-37896, CVE-2025-37919, CVE-2025-37909, CVE-2025-37934, CVE-2025-37897, CVE-2025-37912, CVE-2025-37923, CVE-2025-37904, CVE-2025-37894, CVE-2025-38216, CVE-2025-37930, CVE-2025-37935, CVE-2025-37910, CVE-2025-37933, CVE-2025-37916, CVE-2025-37907, CVE-2025-37913, CVE-2025-37905, CVE-2025-37918, CVE-2025-37915, CVE-2025-37927, CVE-2025-37991, CVE-2025-37929, CVE-2025-37924, CVE-2025-37920, CVE-2025-37901, CVE-2025-37900, CVE-2025-37922, CVE-2025-37898, CVE-2025-37946, CVE-2025-37914, CVE-2025-37936, CVE-2025-37926, CVE-2025-37899, CVE-2025-37895, CVE-2025-37903, CVE-2025-37911, CVE-2025-37891, CVE-2025-37928)

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;
• PA-RISC architecture;
• PowerPC architecture;
• S390 architecture;
• x86 architecture;
• Compute Acceleration Framework;
• Ublk userspace block driver;
• ARM SCMI message protocol;
• GPU drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Network drivers;
• PCI subsystem;
• PTP clock framework;
• SPI subsystem;
• BTRFS file system;
• SMB network file system;
• eXpress Data Path;
• Universal MIDI packet (UMP) support module;
• Tracing infrastructure;
• Memory management;
• IPv4 networking;
• IPv6 networking;
• Network traffic control;
• AMD SoC Alsa drivers;
• SoC Audio generic drivers; (CVE-2025-37899, CVE-2025-37905, CVE-2025-37916, CVE-2025-37935, CVE-2025-37923, CVE-2025-37906, CVE-2025-37929, CVE-2025-37907, CVE-2025-37909, CVE-2025-37910, CVE-2025-37921, CVE-2025-37927, CVE-2025-38216, CVE-2025-37914, CVE-2025-37928, CVE-2025-37915, CVE-2025-37990, CVE-2025-37917, CVE-2025-37936, CVE-2025-37946, CVE-2025-37934, CVE-2025-37894, CVE-2025-37898, CVE-2025-37911, CVE-2025-37912, CVE-2025-37920, CVE-2025-37926, CVE-2025-37919, CVE-2025-37900, CVE-2025-37908, CVE-2025-37924, CVE-2025-37974, CVE-2025-37901, CVE-2025-37903, CVE-2025-37891, CVE-2025-37922, CVE-2025-37991, CVE-2025-37930, CVE-2025-37896, CVE-2025-37897, CVE-2025-37913, CVE-2025-37895, CVE-2025-37933, CVE-2025-37904, CVE-2025-37931)

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;
• PA-RISC architecture;
• PowerPC architecture;
• S390 architecture;
• x86 architecture;
• Compute Acceleration Framework;
• Ublk userspace block driver;
• Bluetooth drivers;
• ARM SCMI message protocol;
• GPU drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Network drivers;
• PCI subsystem;
• PTP clock framework;
• SPI subsystem;
• BTRFS file system;
• SMB network file system;
• eXpress Data Path;
• Universal MIDI packet (UMP) support module;
• Tracing infrastructure;
• Memory management;
• IPv4 networking;
• IPv6 networking;
• Network traffic control;
• AMD SoC Alsa drivers;
• SoC Audio generic drivers; (CVE-2025-37901, CVE-2025-37990, CVE-2025-37891, CVE-2025-37918, CVE-2025-37930, CVE-2025-37909, CVE-2025-37906, CVE-2025-37913, CVE-2025-37927, CVE-2025-37922, CVE-2025-37899, CVE-2025-37894, CVE-2025-37934, CVE-2025-37911, CVE-2025-37912, CVE-2025-37933, CVE-2025-37924, CVE-2025-37900, CVE-2025-37907, CVE-2025-37974, CVE-2025-37928, CVE-2025-37914, CVE-2025-37905, CVE-2025-37921, CVE-2025-37919, CVE-2025-37915, CVE-2025-37910, CVE-2025-37903, CVE-2025-37936, CVE-2025-37904, CVE-2025-38216, CVE-2025-37923, CVE-2025-37931, CVE-2025-37895, CVE-2025-37917, CVE-2025-37926, CVE-2025-37916, CVE-2025-37935, CVE-2025-37898, CVE-2025-37897, CVE-2025-37929, CVE-2025-37908, CVE-2025-37946, CVE-2025-37896, CVE-2025-37920, CVE-2025-37991)

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;
• PA-RISC architecture;
• PowerPC architecture;
• S390 architecture;
• x86 architecture;
• Compute Acceleration Framework;
• Ublk userspace block driver;
• Bluetooth drivers;
• ARM SCMI message protocol;
• GPU drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Network drivers;
• PCI subsystem;
• PTP clock framework;
• SPI subsystem;
• BTRFS file system;
• SMB network file system;
• eXpress Data Path;
• Universal MIDI packet (UMP) support module;
• Tracing infrastructure;
• Memory management;
• IPv4 networking;
• IPv6 networking;
• Netfilter;
• Network traffic control;
• AMD SoC Alsa drivers;
• SoC Audio generic drivers; (CVE-2025-37900, CVE-2025-37912, CVE-2025-37904, CVE-2025-37924, CVE-2025-37907, CVE-2025-37894, CVE-2025-37909, CVE-2025-37891, CVE-2025-37990, CVE-2025-37991, CVE-2025-37910, CVE-2025-37930, CVE-2025-37895, CVE-2025-37898, CVE-2025-37935, CVE-2025-37931, CVE-2025-37906, CVE-2025-37997, CVE-2025-37946, CVE-2025-37896, CVE-2025-37933, CVE-2025-37920, CVE-2025-37890, CVE-2025-37899, CVE-2025-37974, CVE-2025-37919, CVE-2025-37916, CVE-2025-38177, CVE-2025-37908, CVE-2025-37913, CVE-2025-37911, CVE-2025-37901, CVE-2025-37927, CVE-2025-38000, CVE-2025-38001, CVE-2025-37897, CVE-2025-37918, CVE-2025-37923, CVE-2025-37914, CVE-2025-37929, CVE-2025-37903, CVE-2025-37932, CVE-2025-37926, CVE-2025-37905, CVE-2025-37928, CVE-2025-37915, CVE-2025-38216, CVE-2025-37917, CVE-2025-37936, CVE-2025-37934, CVE-2025-37921, CVE-2025-37922)

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;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• x86 architecture;
• Compute Acceleration Framework;
• Ublk userspace block driver;
• Bluetooth drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• ARM SCMI message protocol;
• GPU drivers;
• HID subsystem;
• IIO ADC drivers;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Multiple devices driver;
• Network drivers;
• Mellanox network drivers;
• PCI subsystem;
• PHY drivers;
• PTP clock framework;
• Voltage and Current Regulator drivers;
• SPI subsystem;
• VideoCore services drivers;
• USB Type-C Connector System Software Interface driver;
• Xen hypervisor drivers;
• BTRFS file system;
• EROFS file system;
• Network file system (NFS) client;
• File systems infrastructure;
• SMB network file system;
• Network traffic control;
• eXpress Data Path;
• Universal MIDI packet (UMP) support module;
• io_uring subsystem;
• Kernel command line parsing driver;
• Scheduler infrastructure;
• Tracing infrastructure;
• Memory management;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• Management Component Transport Protocol (MCTP);
• Netfilter;
• Open vSwitch;
• TLS protocol;
• Wireless networking;
• AMD SoC Alsa drivers;
• SoC Audio generic drivers;
• SOF drivers; (CVE-2025-37959, CVE-2025-37927, CVE-2025-37891, CVE-2025-37906, CVE-2025-37962, CVE-2025-37972, CVE-2025-37919, CVE-2025-37958, CVE-2025-37929, CVE-2025-37969, CVE-2025-37949, CVE-2025-37916, CVE-2025-38027, CVE-2025-37968, CVE-2025-37931, CVE-2025-37923, CVE-2025-37918, CVE-2025-37998, CVE-2025-37907, CVE-2025-37894, CVE-2025-38028, CVE-2025-37915, CVE-2025-38008, CVE-2025-37946, CVE-2025-38020, CVE-2025-37926, CVE-2025-37950, CVE-2025-38216, CVE-2025-37973, CVE-2025-38014, CVE-2025-37963, CVE-2025-38009, CVE-2025-38010, CVE-2025-37971, CVE-2025-38012, CVE-2025-38094, CVE-2025-37955, CVE-2025-37904, CVE-2025-38095, CVE-2025-37951, CVE-2025-37964, CVE-2025-37901, CVE-2025-37956, CVE-2025-38016, CVE-2025-37960, CVE-2025-37898, CVE-2025-37992, CVE-2025-38006, CVE-2025-37993, CVE-2025-37921, CVE-2025-38007, CVE-2025-37930, CVE-2025-37895, CVE-2025-37897, CVE-2025-37933, CVE-2025-37899, CVE-2025-37967, CVE-2025-38019, CVE-2025-37966, CVE-2025-37961, CVE-2025-37934, CVE-2025-37952, CVE-2025-37994, CVE-2025-37914, CVE-2025-38083, CVE-2025-37970, CVE-2025-37965, CVE-2025-38025, CVE-2025-38023, CVE-2025-38015, CVE-2025-37911, CVE-2025-38056, CVE-2025-37995, CVE-2025-37991, CVE-2025-37920, CVE-2025-38011, CVE-2025-37910, CVE-2025-37924, CVE-2025-37996, CVE-2025-37948, CVE-2025-37922, CVE-2025-37947, CVE-2025-37912, CVE-2025-37990, CVE-2025-37909, CVE-2025-38021, CVE-2025-38022, CVE-2025-37908, CVE-2025-37900, CVE-2025-37999, CVE-2025-37905, CVE-2025-37954, CVE-2025-37974, CVE-2025-38005, CVE-2025-37913, CVE-2025-37903, CVE-2025-37896, CVE-2025-38002, CVE-2025-37935, CVE-2025-38018, CVE-2025-37936, CVE-2025-38013, CVE-2025-37957, CVE-2025-37928, CVE-2025-37917, CVE-2025-38024)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

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:

• SMB network file system; (CVE-2025-22037, CVE-2025-37899)

Qualys discovered that several vulnerabilities existed in the AppArmor Linux kernel Security Module (LSM). An unprivileged local attacker could use these issues to load, replace, and remove arbitrary AppArmor profiles causing denial of service, exposure of sensitive information (kernel memory), local privilege escalation, or possibly escape a container. (LP: #2143853)

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;
• Nios II architecture;
• PA-RISC architecture;
• RISC-V architecture;
• S390 architecture;
• Sun Sparc architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Xtensa architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• ATM drivers;
• Drivers core;
• Block device driver;
• Network block device driver;
• Bluetooth drivers;
• Bus devices;
• Hardware random number generator core;
• Character device driver;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• DMA engine subsystem;
• ARM SCMI message protocol;
• EFI core;
• Intel Stratix 10 firmware drivers;
• GPU drivers;
• HID subsystem;
• CoreSight HW tracing drivers;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• Input Device (Tablet) drivers;
• IOMMU subsystem;
• ISDN/mISDN subsystem;
• Mailbox framework;
• Multiple devices driver;
• Media drivers;
• Fastrpc Driver;
• MOST (Media Oriented Systems Transport) drivers;
• MTD block device drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• Texas Instruments network drivers;
• Ethernet team driver;
• NVME drivers;
• PCI subsystem;
• PCCARD (PCMCIA/CardBus) bus subsystem;
• Performance monitor drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• ARM PM domains;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• PWM drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• Texas Instruments SoC drivers;
• TCM subsystem;
• Trusted Execution Environment drivers;
• TTY drivers;
• Userspace I/O drivers;
• Cadence USB3 driver;
• DesignWare USB3 driver;
• USB Gadget drivers;
• USB Host Controller drivers;
• Renesas USBHS Controller drivers;
• USB Mass Storage drivers;
• Virtio Host (VHOST) subsystem;
• Framebuffer layer;
• Xen hypervisor drivers;
• AFS file system;
• BTRFS file system;
• Ceph distributed file system;
• File systems infrastructure;
• EFI Variable file system;
• exFAT file system;
• Ext4 file system;
• F2FS file system;
• FUSE (File system in Userspace);
• GFS2 file system;
• HFS file system;
• HFS+ file system;
• HugeTLB file system;
• JFS file system;
• KERNFS file system;
• Network file system (NFS) client;
• Network file system (NFS) server daemon;
• File system notification infrastructure;
• NTFS3 file system;
• OCFS2 file system;
• OrangeFS file system;
• Proc file system;
• Diskquota system;
• SMB network file system;
• SquashFS file system;
• UDF file system;
• XFS file system;
• Asynchronous Transfer Mode (ATM) subsystem;
• BPF subsystem;
• Mellanox drivers;
• NFS page cache wrapper;
• Memory management;
• Memory Management;
• Media input infrastructure;
• Bluetooth subsystem;
• IP tunnels definitions;
• Network traffic control;
• Rose network layer;
• Network sockets;
• io_uring subsystem;
• Control group (cgroup);
• Kernel crash support code;
• Kernel futex primitives;
• PID allocator;
• Scheduler infrastructure;
• Syscalls implementation;
• Timer…

Qualys discovered that several vulnerabilities existed in the AppArmor Linux kernel Security Module (LSM). An unprivileged local attacker could use these issues to load, replace, and remove arbitrary AppArmor profiles causing denial of service, exposure of sensitive information (kernel memory), local privilege escalation, or possibly escape a container. (LP: #2143853)

It was discovered that improper initialization of CPU cache memory could allow a local attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity. (CVE-2024-36331)

Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos, and Flavien Solt discovered that some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information. A local attacker could possibly use this to expose sensitive information. (CVE-2024-36350, CVE-2024-36357)

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;
• MIPS architecture;
• Nios II architecture;
• PA-RISC architecture;
• PowerPC architecture;
• RISC-V architecture;
• S390 architecture;
• Sun Sparc architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Xtensa architecture;
• Block layer subsystem;
• Cryptographic API;
• Compute Acceleration Framework;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• ATM drivers;
• Drivers core;
• ATA over ethernet (AOE) driver;
• DRBD Distributed Replicated Block Device drivers;
• Block device driver;
• Network block device driver;
• Ublk userspace block driver;
• Bluetooth drivers;
• Bus devices;
• Hardware random number generator core;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Device frequency scaling framework;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• EDAC drivers;
• Arm Firmware Framework for ARMv8-A(FFA);
• ARM SCMI message protocol;
• EFI core;
• Intel Stratix 10 firmware drivers;
• FPGA Framework;
• GPU drivers;
• HID subsystem;
• Hardware monitoring drivers;
• CoreSight HW tracing drivers;
• I2C subsystem;
• I3C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device core drivers;
• Input Device (Miscellaneous) drivers;
• Input Device (Tablet) drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• ISDN/mISDN subsystem;
• Mailbox framework;
• MCB driver;
• Multiple devices driver;
• Media drivers;
• Multifunction device drivers;
• Fastrpc Driver;
• Microchip PCI driver;
• Intel Management Engine Interface driver;
• PCI Endpoint Test driver;
• TI TPS6594 PFSM driver;
• VMware VMCI Driver;
• MMC subsystem;
• MOST (Media Oriented Systems Transport) drivers;
• MTD block device drivers;
• Ethernet bonding driver;
• Network drivers;
• Mellanox network drivers;
• STMicroelectronics network drivers;
• Texas Instruments network drivers;
• Ethernet team driver;
• MediaTek network drivers;
• NVDIMM (Non-Volatile Memory Device) drivers;
• NVME drivers;
• PCI subsystem;
• PCCARD (PCMCIA/CardBus) bus subsystem;
• Amlogic Meson DDR PMU;
• Performance monitor drivers;
• PHY drivers;
• Pin controllers subsystem;
• x86 platform drivers;
• ARM PM domains;
• Power supply drivers;
• Powercap sysfs driver;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• PWM drivers;
• RapidIO drivers;
• Voltage and Current Regulator drivers;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI subsystem;
• ASPEED SoC drivers;
• QCOM SoC drivers;
• Samsung SoC drivers;
• Texas Instruments SoC drivers;
• SPI subsystem; -…