In the Linux kernel, the following vulnerability has been resolved: mm: memory-failure: update ttu flag inside unmap_poisoned_folio Patch series "mm: memory_failure: unmap poisoned folio during migrate properly", v3. Fix two bugs during folio migration if the folio is poisoned. This patch (of 3): Commit 6da6b1d4a7df ("mm/hwpoison: convert TTU_IGNORE_HWPOISON to TTU_HWPOISON") introduce TTU_HWPOISON to replace TTU_IGNORE_HWPOISON in order to stop send SIGBUS signal when accessing an error page after a memory error on a clean folio. However during page migration, anon folio must be set with TTU_HWPOISON during unmap_*(). For pagecache we need some policy just like the one in hwpoison_user_mappings to set this flag. So move this policy from hwpoison_user_mappings to unmap_poisoned_folio to handle this warning properly. Warning will be produced during unamp poison folio with the following log: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 365 at mm/rmap.c:1847 try_to_unmap_one+0x8fc/0xd3c Modules linked in: CPU: 1 UID: 0 PID: 365 Comm: bash Tainted: G W 6.13.0-rc1-00018-gacdb4bbda7ab #42 Tainted: [W]=WARN Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : try_to_unmap_one+0x8fc/0xd3c lr : try_to_unmap_one+0x3dc/0xd3c Call trace: try_to_unmap_one+0x8fc/0xd3c (P) try_to_unmap_one+0x3dc/0xd3c (L) rmap_walk_anon+0xdc/0x1f8 rmap_walk+0x3c/0x58 try_to_unmap+0x88/0x90 unmap_poisoned_folio+0x30/0xa8 do_migrate_range+0x4a0/0x568 offline_pages+0x5a4/0x670 memory_block_action+0x17c/0x374 memory_subsys_offline+0x3c/0x78 device_offline+0xa4/0xd0 state_store+0x8c/0xf0 dev_attr_store+0x18/0x2c sysfs_kf_write+0x44/0x54 kernfs_fop_write_iter+0x118/0x1a8 vfs_write+0x3a8/0x4bc ksys_write+0x6c/0xf8 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x44/0x100 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x30/0xd0 el0t_64_sync_handler+0xc8/0xcc el0t_64_sync+0x198/0x19c ---[ end trace 0000000000000000 ]--- [mawupeng1@huawei.com: unmap_poisoned_folio(): remove shadowed local `mapping', per Miaohe]
CVE-2025-21887 is a use-after-free vulnerability in the Linux kernel's overlay filesystem (ovl) component. The flaw occurs because a dput() call on an upper dentry was made before its last use, leading to a use-after-free condition. This issue was fixed by moving the dput() call to after the last access to prevent the vulnerability. The flaw was detected by KASAN and affects various Linux kernel versions prior to the fixed releases. The vulnerability has a high severity score and could allow an attacker with local privileges to compromise system confidentiality, integrity, and availability.
A vulnerability in the interprocess communication (IPC) channel of Cisco Secure Client for Windows could allow an authenticated, local attacker to perform a DLL hijacking attack on an affected device if the Secure Firewall Posture Engine, formerly HostScan, is installed on Cisco Secure Client.
This vulnerability is due to insufficient validation of resources that are loaded by the application at run time. An attacker could exploit this vulnerability by sending a crafted IPC message to a specific Cisco Secure Client process. A successful exploit could allow the attacker to execute arbitrary code on the affected machine with SYSTEM privileges. To exploit this vulnerability, the attacker must have valid user credentials on the Windows system.
A vulnerability in the Linux kernel's arm64 cacheinfo code could cause an out-of-bounds write to the cacheinfo array due to improper indexing when handling cache levels with separate data and instruction caches. This flaw has been fixed in multiple patched kernel versions. The vulnerability has a high severity score and could allow local attackers to compromise system confidentiality, integrity, and availability.
CVE-2025-21763 is a high-severity vulnerability in the Linux kernel's neighbour subsystem where the __neigh_notify() function can be called without proper RTNL or RCU protection. This lack of protection can lead to a use-after-free (UAF) condition. The issue affects multiple Linux kernel versions and has been fixed in several patched releases. The vulnerability could allow an attacker with local privileges to compromise system confidentiality, integrity, and availability. Ubuntu has released security updates addressing this and other kernel vulnerabilities, recommending users to update and reboot their systems.
A vulnerability in the Linux kernel's IPv6 multicast implementation (mld_newpack function) was identified where the function could be called without proper RTNL or RCU locking, potentially leading to race conditions. This flaw has been fixed by adding RCU protection and changing socket buffer allocation methods. The issue affects multiple Linux kernel versions prior to 5.15.0-1084.91 and several older versions. The vulnerability has a high severity score and could allow an attacker with local privileges to compromise system confidentiality, integrity, and availability. A patch is available and included in various updated Linux kernel releases.
CVE-2025-21738 is a high-severity vulnerability in the Linux kernel's libata-sff driver. It involves a buffer overflow condition where the ata_pio_sector() function can write outside the allocated buffer due to improper handling of certain SCSI ioctl commands. This flaw could allow an attacker with local privileges to overwrite random memory, potentially leading to system compromise. The issue has been fixed in Linux kernel versions 6.8.0 and later.
CVE-2025-21731 is a use-after-free vulnerability in the Linux kernel's network block device (nbd) driver. It occurs due to improper handling of references during reconnect attempts after a disconnect, leading to a potential use-after-free condition. This flaw has been fixed by clearing a specific internal flag to prevent reconnection after disconnection. The vulnerability affects multiple Linux kernel versions prior to fixed releases in the 5.4.x and 5.15.x series. The issue has a high severity score and could allow an attacker with local privileges to compromise system integrity and availability.
CVE-2025-21718 is a race condition vulnerability in the Linux kernel's Rose network layer timers. The flaw occurs because Rose timers only acquire the socket spinlock without verifying if the socket is owned by a user thread, leading to a use-after-free condition. This issue has been fixed in Linux kernel versions starting from 5.4.0-1146.156 and other specified patched versions. The vulnerability has a high severity score and could allow an attacker with local privileges to compromise system integrity and availability.
In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the first datagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to the address of the sender, in order to set up a directed flow. Now, if the client, running on a different CPU thread, happens to send a (subsequent) datagram while the server's socket changes its address, but is not rehashed yet, this will result in a failed lookup and a port unreachable error delivered to the client, as apparent from the following reproducer: LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4)) dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in while :; do taskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc & sleep 0.1 || sleep 1 taskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null wait done where the client will eventually get ECONNREFUSED on a write() (typically the second or third one of a given iteration): 2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused This issue was first observed as a seldom failure in Podman's tests checking UDP functionality while using pasta(1) to connect the container's network namespace, which leads us to a reproducer with the lookup error resulting in an ICMP packet on a tap device: LOCAL_ADDR="$(ip -j -4 addr show|jq -rM '.[] | .addr_info[0] | select(.scope == "global").local')" while :; do ./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc & sleep 0.2 || sleep 1 socat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null wait cmp tmp.in tmp.out done Once this fails: tmp.in tmp.out differ: char 8193, line 29 we can finally have a look at what's going on: $ tshark -r pasta.pcap 1 0.000000 :: ? ff02::16 ICMPv6 110 Multicast Listener Report Message v2 2 0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 3 0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 4 0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 5 0.168827 c6:47:05:8d:dc:04 ? Broadcast ARP 42 Who has 88.198.0.161? Tell 88.198.0.164 6 0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55 7 0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 8 0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable) 9 0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 10 0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 11 0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096 12 0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0 On the third datagram received, the network namespace of the container initiates an ARP lookup to deliver the ICMP message. In another variant of this reproducer, starting the client with: strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru ---truncated---
CVE-2025-21699 is a high-severity vulnerability in the Linux kernel's GFS2 file system. It involves improper handling of an inode's address space when flipping the GFS2_DIF_JDATA flag, which can cause mixing of incompatible page structures. This flaw has been fixed in multiple Linux kernel versions starting from 5.4.0-1090.95 and similar updates. The vulnerability could allow an attacker with local privileges to compromise system integrity and availability. Ubuntu has released security updates addressing this and other kernel issues.
CVE-2025-21631 is a use-after-free (UAF) vulnerability in the Linux kernel's block layer BFQ I/O scheduler subsystem. It occurs after the bfq_split_bfqq() function, leading to a kernel memory corruption detected by KASAN. This flaw affects multiple Linux kernel versions and has been fixed in several 5.15.x kernel releases. The vulnerability has a high severity score and could allow a local attacker with limited privileges to compromise system integrity and availability.
CVE-2024-57850 is a high-severity vulnerability in the Linux kernel's jffs2 filesystem. The rtime decompression routine lacks complete bounds checking during decompression, which can lead to memory corruption if the compressed data is corrupted. This flaw could allow an attacker with local privileges to cause memory corruption, potentially leading to system compromise.
A vulnerability in the Linux kernel's gpio-charger power supply subsystem allowed improper handling of charge current limits, leading to out-of-bounds memory access. This flaw was fixed in several Linux kernel versions starting with 5.15.0-1074.77~20.04.1 and later. The issue could allow a local attacker with limited privileges to cause memory corruption, potentially leading to system compromise. The vulnerability has a high severity score of 7.8 CVSS v3.1 and affects multiple Linux kernel versions prior to the fixed releases.
A use-after-free vulnerability in the Linux kernel's NFS server daemon (nfsd) was fixed by ensuring the export structure remains active before being accessed. The flaw involved improper reference counting that could lead to a refcount use-after-free warning. This issue affects multiple Linux kernel versions prior to specific fixed releases. The vulnerability has a high severity score and could allow local attackers to compromise system integrity and confidentiality.
CVE-2024-56551 is a use-after-free vulnerability in the drm/amdgpu component of the Linux kernel. It involves a slab-use-after-free error in the drm_sched_entity_flush function, which has been fixed in updated Linux kernel versions. This flaw could allow local attackers with limited privileges to cause memory corruption, potentially leading to system compromise. The vulnerability affects multiple Linux kernel versions, particularly those used in AWS and Ubuntu distributions. A patch is available and has been incorporated into several fixed kernel releases.
CVE-2024-56603 is a use-after-free vulnerability in the Linux kernel's CAN network layer. The flaw occurs in the can_create() function where, on error, an allocated socket object is freed but a dangling pointer remains attached to the sock object, potentially leading to memory corruption. This issue affects multiple Linux kernel versions and has been addressed in several patched releases. The vulnerability has a high severity score and could allow local attackers with limited privileges to compromise system integrity. Official patches are available and should be applied to mitigate the risk.
CVE-2024-56602 is a use-after-free vulnerability in the Linux kernel's IEEE 802.15.4 network subsystem. The flaw occurs when the ieee802154_create() function fails after allocating a socket (sk) object but does not clear the pointer in the associated sock object, leaving a dangling pointer. This can lead to memory corruption and potentially allow an attacker with local privileges to compromise system confidentiality, integrity, and availability. The issue affects multiple Linux kernel versions prior to fixed releases. A patch is available and has been incorporated into various Linux kernel updates.
CVE-2024-56604 is a high-severity vulnerability in the Linux kernel's Bluetooth RFCOMM subsystem. It involves a use-after-free condition caused by a dangling socket pointer left in rfcomm_sock_alloc() when rfcomm_dlc_alloc() fails. This flaw could allow local attackers with limited privileges to compromise system confidentiality, integrity, and availability. The issue has been fixed in Linux kernel versions 6.8.0 and later. Ubuntu has released security updates addressing this and other kernel vulnerabilities.