CVE-2026-99180

published 28 Oct 2026 · updated 2 Nov 2026

unicode: free the map after a grace period

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f96c2731a105d6663c606388f5dc21781e00ade5, Kernel 092e14e1479a39157ca01668d43e4649793f39ed, Kernel 2b54d3c971a1e5df3c9b0bcc10311ae6c29e79d8 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: unicode: free the map after a grace period generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still inside such a filesystem at that point reads a freed map. With a pathwalk held up in utf8_casefold_hash() while the last reference to a casefolded tmpfs goes away: BUG: KASAN: slab-use-after-free in utf8nlookup+0x74c/0x950 Read of size 8 at addr ff110001030fe658 by task walker/98 Call Trace: <TASK> utf8nlookup+0x74c/0x950 utf8byte+0x160/0x1560 utf8_casefold_hash+0x167/0x230 generic_ci_d_hash+0xdd/0x1c0 link_path_walk+0x11ad/0x1d30 path_lookupat+0x63/0xb00 filename_lookup+0x1f1/0x5b0 vfs_statx+0xd7/0x3b0 [...] Allocated by task 94: __kmalloc_cache_noprof+0x249/0x560 utf8_load+0x4e/0x570 shmem_parse_opt_casefold.isra.0+0x92/0x270 [...] Freed by task 97: kfree+0x1db/0x5b0 shmem_put_super+0x72/0x170 generic_shutdown_super+0x14c/0x530 kill_anon_super+0x3a/0x60 deactivate_locked_super+0x9c/0xf0 cleanup_mnt+0x9f/0x130 So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker. So it is reachable. Delay the free until a grace period has passed. The map and the data table it holds a reference to then outlive any pathwalk that found the superblock before the mount went away. The reference on the data table module is dropped from the rcu callback as well. utf8-core is built in whenever CONFIG_UNICODE is set, so there is no module exit that would have to wait for the callbacks. Overlayfs points the s_encoding of an overlay at the map of its first layer without taking a reference of its own. That stays correct. The layer is held by the overlay, so its map is dropped only after the overlay is gone.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <f96c2731a105d6663c606388f5dc21781e00ade5, >=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <092e14e1479a39157ca01668d43e4649793f39ed, >=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <2b54d3c971a1e5df3c9b0bcc10311ae6c29e79d8, >=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <5d7687b0b71601cc32f1bfd62f56cf5eea3e5a07, >=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <6472455f2b015cad43adb790cb63fe1d3cff2f57, >=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <6560c3d9a6925e3747d9ad8463e16010c31ba715, >=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <69a0d6b31d05e856c7335509222f25321e3c69ca, >=b886ee3e778ec2ad43e276fd378ab492cf6819b7 <a96c5299bd7305eb984377681eb3222a57376405, =5.2f96c2731a105d6663c606388f5dc21781e00ade5, 092e14e1479a39157ca01668d43e4649793f39ed, 2b54d3c971a1e5df3c9b0bcc10311ae6c29e79d8, 5d7687b0b71601cc32f1bfd62f56cf5eea3e5a07, 6472455f2b015cad43adb790cb63fe1d3cff2f57, 6560c3d9a6925e3747d9ad8463e16010c31ba715, 69a0d6b31d05e856c7335509222f25321e3c69ca, a96c5299bd7305eb984377681eb3222a57376405
linux-kernel: Kernel>=5.16.0 <6.1.191, >=5.2.0 <5.10.273, >=6.13.0 <6.18.59, >=6.19.0 <7.2.13, >=6.2.0 <6.6.161, >=6.7.0 <6.12.115, >=5.11.0 <5.15.2246.1.191, 5.10.273, 6.18.59, 7.2.13, 6.6.161, 6.12.115, 5.15.224

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99180 severity on Zeptric[![CVE-2026-99180](https://zeptric.io/badge/cve/CVE-2026-99180.svg)](https://zeptric.io/cve/CVE-2026-99180)