Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 467/469 docs · 8/9 advisories · checked 21:57 UTC Customize Public modeDiscuss ChangeIntel on Discord

fs: Free any excess xarray nodes in clear_inode()

Exact source revision recorded 23 Oct 2026 16:01:20 UTC. It does not establish the source's current position. Latest evidence.

cve-program · CVE-2026-99080

Published

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.

Source published
23 Oct 2026 12:23:27 UTC
Source modified
23 Oct 2026 12:23:27 UTC
Observed here
23 Oct 2026 16:01:20 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 21:57 UTC · 272 of 272 readable · 270 fully read · documentation 467/469 current