---
id: "CVE-2026-99080"
kind: "vulnerability"
aliases: ["CVE-2026-99080"]
title: "Linux kernel: leaked xarray nodes in filesystem inodes can be forced by madvise"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "kernel", "linux"]
not_affected_if: []
published_at: "2026-10-23T13:17:32+00:00"
first_seen_at: "2026-10-23T21:57:34+00:00"
updated_at: "2026-10-25T04:53:37+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99080", "first_seen_at": "2026-10-23T21:57:34+00:00"}]
---

# Linux kernel: leaked xarray nodes in filesystem inodes can be forced by madvise

The Linux kernel's inode clearing path leaked xarray tree nodes in rare cases, and recent reports show that madvise calls can trigger the leak on demand. The fix frees any leftover nodes when an inode is cleared, which stops the memory from accumulating.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-10-23T21:57:34+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99080

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_