CVE-2026-72379

published 15 Aug 2026 · updated 14 Nov 2026

fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid

5.0MediumEPSS 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 bac8fb0d60254846f3b56957435dcd870ae12948, Kernel 47e434da476b5a8bcd1e6e52ab03c5ee7764ee78, Kernel 503d0568a525b168d9aa5ca046ec72fc5477df84 and 8 more.

In the Linux kernel, the following vulnerability has been resolved: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid vfs_tmpfile() never checked that the caller's fsuid and fsgid map into the filesystem. On an idmapped mount whose idmapping does not cover the caller's fs{u,g}id, the ->tmpfile() instance initializes the new inode through inode_init_owner(), where mapped_fsuid()/mapped_fsgid() return INVALID_UID/INVALID_GID, and the tmpfile ends up owned by (uid_t)-1. Every other creation path already refuses this: may_o_create() (O_CREAT) and may_create_dentry() (mkdir, mknod, symlink, link) bail out with -EOVERFLOW via fsuidgid_has_mapping() precisely so that an object cannot be created with an owner the filesystem cannot represent. An O_TMPFILE is no exception: it is created I_LINKABLE and linkat(2) can splice it into the namespace afterwards, so the same guarantee must hold. Add the missing fsuidgid_has_mapping() check to vfs_tmpfile(). On a non-idmapped mount the caller's fs{u,g}id always map in the superblock's user namespace, so this is a no-op there and only takes effect on an idmapped mount that does not map the caller. It applies to every filesystem that sets FS_ALLOW_IDMAP and implements ->tmpfile() (tmpfs, ext4, btrfs, xfs, f2fs, ...), and to overlayfs, whose upper-layer tmpfile creation funnels through vfs_tmpfile() via backing_tmpfile_open().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=8e5389132ab429604c1a2459b52f0c849a71cc61 <bac8fb0d60254846f3b56957435dcd870ae12948, >=8e5389132ab429604c1a2459b52f0c849a71cc61 <47e434da476b5a8bcd1e6e52ab03c5ee7764ee78, >=8e5389132ab429604c1a2459b52f0c849a71cc61 <503d0568a525b168d9aa5ca046ec72fc5477df84, >=8e5389132ab429604c1a2459b52f0c849a71cc61 <539dce1144651f7976fa418e618b0b574bf15eeb, >=8e5389132ab429604c1a2459b52f0c849a71cc61 <74365c6e367725728d5ce36d38ca116c9f77a254, >=8e5389132ab429604c1a2459b52f0c849a71cc61 <a2038514e69371eb493083a6a897ed20fcbb8acb, =5.13bac8fb0d60254846f3b56957435dcd870ae12948, 47e434da476b5a8bcd1e6e52ab03c5ee7764ee78, 503d0568a525b168d9aa5ca046ec72fc5477df84, 539dce1144651f7976fa418e618b0b574bf15eeb, 74365c6e367725728d5ce36d38ca116c9f77a254, a2038514e69371eb493083a6a897ed20fcbb8acb
linux-kernel: Kernel>=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=5.13.0 <6.1.1916.18.40, 7.1.5, 6.6.145, 6.12.97, 6.1.191

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-72379 severity on Zeptric[![CVE-2026-72379](https://zeptric.io/badge/cve/CVE-2026-72379.svg)](https://zeptric.io/cve/CVE-2026-72379)