CVE Tools

CVE-2026-99080

fs: Free any excess xarray nodes in clear_inode()

No known exploitation. No EPSS score yet. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < f1c966eb6ed5e190c90a56c5bdaa69967de39f21Upgrade to: f1c966eb6ed5e190c90a56c5bdaa69967de39f21Affected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 21f51434c47d8628b62275ae6c6ad6b573abcd02Upgrade to: 21f51434c47d8628b62275ae6c6ad6b573abcd02Affected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 50cff3f112d64db6e5f57355f79bc837db8fe132Upgrade to: 50cff3f112d64db6e5f57355f79bc837db8fe132Affected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 43f830e2bb84b22ca824b20bb861d823ecb520bdUpgrade to: 43f830e2bb84b22ca824b20bb861d823ecb520bd + 5 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

No EPSS score yet. New CVEs are usually scored within a few days.

Lifecycle

2 events over 0 days, from the signal feeds we watch.

  1. Publishedrecord updated

Affected products

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.