CVE-2026-89839

f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set()

CVE-2026-89839 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-89839, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.1
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0020
9th percentile

In the Linux kernel, the following vulnerability has been resolved: f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set() f2fs_xattr_advise_set() calls inode_owner_or_capable() with &nop_mnt_idmap before allowing the "system.advise" xattr to be set, instead of the idmap that the VFS passes to the ->set() handler. f2fs supports idmapped mounts, so on such a mount this checks the caller's fsuid against the unmapped on-disk owner rather than the mapped owner: the actual owner can be wrongly denied with -EPERM and an unrelated caller wrongly allowed. Pass the handler's idmap instead.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 13.5 (trixie) 6.12.111-1 DEBIAN-CVE-2026-89839 Sep 23, 2026
linux · Debian 14 7.2.6-1 DEBIAN-CVE-2026-89839 Sep 23, 2026
linux-6.12 · Debian 12.15 (bookworm) 6.12.111-1~deb12u1 DEBIAN-CVE-2026-89839 Sep 23, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.