Filesystem shutdown via repair allocation failure
Published Oct 18, 2026 · Updated Oct 18, 2026
Allocation failure in Linux XFS online repair allows attackers to shut down the filesystem during replacement btree construction. In fs/xfs/scrub/newbt.c, xrep_newbt_add_blocks returns an allocation error after blocks have been allocated, leaving callers unable to both undo the transaction and propagate the error without shutting down the filesystem. The failure requires online repair and a failed reservation-object allocation; attacker control of that failure is not documented, and the reported consequences are leaked blocks and filesystem shutdown rather than a host reboot.
Summary
What happened
Allocation failure in Linux XFS online repair allows attackers to shut down the filesystem during replacement btree construction. In fs/xfs/scrub/newbt.c, xrep_newbt_add_blocks returns an allocation error after blocks have been allocated, leaving callers unable to both undo the transaction and propagate the error without shutting down the filesystem. The failure requires online repair and a failed reservation-object allocation; attacker control of that failure is not documented, and the reported consequences are leaked blocks and filesystem shutdown rather than a host reboot.
The record
- CVE
- CVE-2026-98445
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.8
- Affected versionversion=be408417630427984a1fddd069f30b245793234c <0e0d3372a84029da1768c7a4c4601484af5b58a2
- Affected versionversion=be408417630427984a1fddd069f30b245793234c <3380151cf0ce8ad0c1d356fed51e4b69e1d28e50
- Affected versionversion=be408417630427984a1fddd069f30b245793234c <ab1c416d2377cdc16123ef521aac4da1c468c3d4
- Affected versionversion=be408417630427984a1fddd069f30b245793234c <b15c79fca28060fd9c7e77f2c3ebc4ba023974e8
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started