CVE-2026-99396: Linux kernel · xfs: bound da-node entry count against the correct geometry
Source GCVE Database
Not known to be exploited · fixed in aaeb3e51052c94959bbc286ccda0c6f2feb3cd69 : update Linux kernel when convenient.
Data as of 19 Nov 2026, 16:21 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in aaeb3e51052c94959bbc286ccda0c6f2feb3cd69, 5909f2935ca2897b51800d00f58a48605253ef4b, 229c4478a35663582893916250ebcdfc7b845b85 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to aaeb3e51052c94959bbc286ccda0c6f2feb3cd69, 5909f2935ca2897b51800d00f58a48605253ef4b, 229c4478a35663582893916250ebcdfc7b845b85 or 3df5e5aaa3bc0913236c48ab29b7df3a785aa29f.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: xfs: bound da-node entry count against the correct geometry xfs_da3_node_verify() bounds the node entry count against the larger of the directory and attribute geometries because, as a buffer verifier, it cannot tell whether the block belongs to the directory or the attribute tree. When the directory block size exceeds the fs block size (e.g. mkfs.xfs -n size=64k -b size=4k), an attribute node buffer is a single fs block that holds only m_attr_geo->node_ents entries, yet a crafted attr node may claim a count up to m_dir_geo->node_ents and still pass the verifier. xfs_da3_node_lookup_int() then indexes btree[] up to that count during its binary search -- an out-of-bounds read via getxattr/listxattr on a mounted crafted image. The buffer verifier is the wrong place to tighten this: it has no fork context, and the transaction-less read path used by getxattr does not run xfs_da3_node_set_type() either. xfs_da3_node_lookup_int(), on the other hand, always runs on that path and holds args->geo, the geometry of the fork actually being searched. Bound the entry count against args->geo->node_ents there, before walking the entries.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99396 (opens in a new tab)
- git.kernel.org/stable/c/229c4478a35663582893916250ebcdfc7b845b85 (opens in a new tab)
- git.kernel.org/stable/c/3df5e5aaa3bc0913236c48ab29b7df3a785aa29f (opens in a new tab)
- git.kernel.org/stable/c/5909f2935ca2897b51800d00f58a48605253ef4b (opens in a new tab)
- git.kernel.org/stable/c/aaeb3e51052c94959bbc286ccda0c6f2feb3cd69 (opens in a new tab)