Answer in brief
CVE-2026-98543 records a High severity (CVSS 7.3) vulnerability in bpf: fs/xattr: don't assume the inode is locked in path_unlink/path_rmdir. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.15 | Not reported |
| Linux/Linuxgeneric | >=56467292794b800164df20c076c409ac548e56ec <7504b677c4370c9e4b153c553ff8831c093b1ff6 || >=56467292794b800164df20c076c409ac548e56ec <640d37fbd34d03af727dbc567f48c0203d1de6b4 || >=56467292794b800164df20c076c409ac548e56ec <35d442ed1f86465e49df3119fb898f985186db13 | 7504b677c4370c9e4b153c553ff8831c093b1ff6, 640d37fbd34d03af727dbc567f48c0203d1de6b4, 35d442ed1f86465e49df3119fb898f985186db13 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.