Linux
bpf: fs/xattr: don't assume the inode is locked in path_unlink/path_rmdir
In the Linux kernel, the following vulnerability has been resolved: bpf: fs/xattr: don't assume the inode is locked in path_unlink/path_rmdir bpf_lsm_has_d_inode_locked() makes the verifier rewrite bpf_[set|remove]_dentry_xattr() to the _locked variants, which assume that the caller already holds the inode's i_rwsem. The path_unlink and path_rmdir hooks are listed, but security_path_unlink() and security_path_rmdir() run before vfs_unlink()/vfs_rmdir() take the victim inode's i_rwsem, so a sleepable BPF LSM program attached to either hook mutates the victim's xattrs without the lock held. Drop the two path hooks from d_inode_locked_hooks so that the verifier keeps the locking bpf_[set|remove]_dentry_xattr() variants, which take the lock themselves.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 56467292794b800164df20c076c409ac548e56ec, < 7504b677c4370c9e4b153c553ff8831c093b1ff6
- >= 56467292794b800164df20c076c409ac548e56ec, < 640d37fbd34d03af727dbc567f48c0203d1de6b4
- >= 56467292794b800164df20c076c409ac548e56ec, < 35d442ed1f86465e49df3119fb898f985186db13
Fixed in 7504b677c4370c9e4b153c553ff8831c093b1ff6, 640d37fbd34d03af727dbc567f48c0203d1de6b4, 35d442ed1f86465e49df3119fb898f985186db13
- 6.15
Fixed in 0, 6.18.55, 7.2.9, 7.3
Mitigation
Upgrade Linux to 7504b677c4370c9e4b153c553ff8831c093b1ff6 or 640d37fbd34d03af727dbc567f48c0203d1de6b4 or 35d442ed1f86465e49df3119fb898f985186db13 or later.
Upgrade Linux to 0 or 6.18.55 or 7.2.9 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.