Skip to main content
VulnerabilityPublished

CVE-2026-99396: Linux kernel · xfs: bound da-node entry count against the correct geometry

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in aaeb3e51052c94959bbc286ccda0c6f2feb3cd69 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 14:34 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 7ab610f9e0f1701b7b319bdc946b9804fb79e780, < aaeb3e51052c94959bbc286ccda0c6f2feb3cd69
Fixed in
  • aaeb3e51052c94959bbc286ccda0c6f2feb3cd69
LinuxLinuxAffected
  • ≥ 7ab610f9e0f1701b7b319bdc946b9804fb79e780, < 5909f2935ca2897b51800d00f58a48605253ef4b
Fixed in
  • 5909f2935ca2897b51800d00f58a48605253ef4b
LinuxLinuxAffected
  • ≥ 7ab610f9e0f1701b7b319bdc946b9804fb79e780, < 229c4478a35663582893916250ebcdfc7b845b85
Fixed in
  • 229c4478a35663582893916250ebcdfc7b845b85
LinuxLinuxAffected
  • ≥ 7ab610f9e0f1701b7b319bdc946b9804fb79e780, < 3df5e5aaa3bc0913236c48ab29b7df3a785aa29f
Fixed in
  • 3df5e5aaa3bc0913236c48ab29b7df3a785aa29f
LinuxLinuxAffected
  • =3.16
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

Community reviews

Loading reviews…