Skip to main content
VulnerabilityPublished

CVE-2026-99080: Linux kernel · fs: Free any excess xarray nodes in clear_inode()

Source GCVE Database

0
Authoritative record:CVE-2026-99080· Low

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

Data as of 26 Oct 2026, 14:05 UTC

Severity
Low

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f1c966eb6ed5e190c90a56c5bdaa69967de39f21, ee3f011250104129893d8e9599147e457d4d7280, 50cff3f112d64db6e5f57355f79bc837db8fe132 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 77da9389b9d5f07d54fda092d1ab56002ec0019a, < f1c966eb6ed5e190c90a56c5bdaa69967de39f21
Fixed in
  • f1c966eb6ed5e190c90a56c5bdaa69967de39f21
LinuxLinuxAffected
  • ≥ 77da9389b9d5f07d54fda092d1ab56002ec0019a, < ee3f011250104129893d8e9599147e457d4d7280
Fixed in
  • ee3f011250104129893d8e9599147e457d4d7280
LinuxLinuxAffected
  • ≥ 77da9389b9d5f07d54fda092d1ab56002ec0019a, < 50cff3f112d64db6e5f57355f79bc837db8fe132
Fixed in
  • 50cff3f112d64db6e5f57355f79bc837db8fe132
LinuxLinuxAffected
  • ≥ 77da9389b9d5f07d54fda092d1ab56002ec0019a, < 43f830e2bb84b22ca824b20bb861d823ecb520bd
Fixed in
  • 43f830e2bb84b22ca824b20bb861d823ecb520bd
LinuxLinuxAffected
  • ≥ 77da9389b9d5f07d54fda092d1ab56002ec0019a, < 21f51434c47d8628b62275ae6c6ad6b573abcd02
Fixed in
  • 21f51434c47d8628b62275ae6c6ad6b573abcd02
LinuxLinuxAffected
  • =4.20
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: fs: Free any excess xarray nodes in clear_inode() For many years we've had a hard to hit leak of xarray nodes. Hugh documented it well in commit 786b31121a2c. Recently people and syzbot have found ways to force it to happen with madvise. Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock.

References

Community reviews

Loading reviews…