f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.157, 6.12.110, 6.18.51, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 01beba7957a26f9b7179127e8ad56bb5a0f56138 · fixed in 4c0c610b480cfbc57528aa1acbd6be12ed2a6fb1; From 01beba7957a26f9b7179127e8ad56bb5a0f56138 · fixed in c3e2692c7a58e0bdb84bd658d827e89dcecea3ad; From 01beba7957a26f9b7179127e8ad56bb5a0f56138 · fixed in 3b681229e9f8fb1dd29bc65983bf3c87779e4ca3; From 01beba7957a26f9b7179127e8ad56bb5a0f56138 · fixed in ab31e3b774f5d06b4489cef6c297b48c47c9dcbd; From 01beba7957a26f9b7179127e8ad56bb5a0f56138 · fixed in a54ffce4637acb0db8e695188a6c7f99f14c3576
- Linux Linux
6.3
- KernelLinux
From 6.3.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5