Skip to main content
VulnerabilityPublished

CVE-2026-99412: Linux kernel · xfs: avoid cross-rtgroup reaping after a repair

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99412

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

Data as of 19 Nov 2026, 16:21 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d46e7803780d5f1a7bbb889f54ab400c30508f09, d7c204d4ea7ef0cf0dac908388984c2936f1f94e, 84c0abd7e70fde9f2f61f06287dbee82734e664a

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 d46e7803780d5f1a7bbb889f54ab400c30508f09, d7c204d4ea7ef0cf0dac908388984c2936f1f94e or 84c0abd7e70fde9f2f61f06287dbee82734e664a.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ fd97fe1112088c16594dcd45e809f1643e623309, < d46e7803780d5f1a7bbb889f54ab400c30508f09
Fixed in
  • d46e7803780d5f1a7bbb889f54ab400c30508f09
LinuxLinuxAffected
  • ≥ fd97fe1112088c16594dcd45e809f1643e623309, < d7c204d4ea7ef0cf0dac908388984c2936f1f94e
Fixed in
  • d7c204d4ea7ef0cf0dac908388984c2936f1f94e
LinuxLinuxAffected
  • ≥ fd97fe1112088c16594dcd45e809f1643e623309, < 84c0abd7e70fde9f2f61f06287dbee82734e664a
Fixed in
  • 84c0abd7e70fde9f2f61f06287dbee82734e664a
LinuxLinuxAffected
  • =6.14
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: xfs: avoid cross-rtgroup reaping after a repair LOLLM notices that the extents stored in a xrtb_bitmap (aka xfs_rtblock bitmap) can span multiple rtgroups due to two circumstances. The first is that the size of an rtgroup is an exact power of two, which means that rtgroups are adjacent in the segmented xfs_rtblock_t address space. This is fairly common to reduce the amount of multiplication and division needed to handle space on the rt volume. The second is that (unlike in the original rtgroups design), rtgroups do not have fixed-location metadata like AGs do, which means that there's nothing to force a break between rtgroups. Therefore, we must loop through the rtgroups in xreap_rtmeta_extent to avoid running off the end of an rtgroup while reaping.

References

Community reviews

Loading reviews…