PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-98445 Linux CVE debrief

A memory allocation failure in the Linux kernel's xrep_newbt_add_blocks function can cause online repair to leak blocks previously allocated to write a new btree. The issue arises because callers cannot undo the transaction and return the error; they must either undo all changes and commit the transaction or error out and shut down the filesystem. However, the new btree space reservation object is relatively small (~48 bytes), and using a NOFAIL allocation resolves the problem.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-18
Original CVE updated
2026-10-18
Advisory published
2026-10-18
Advisory updated
2026-10-18

Who should care

Linux system administrators, security teams, and developers responsible for maintaining and securing Linux-based systems should assess exposure and prioritize patching or compensating controls.

Why it matters

CVE-2026-98445 is a Linux kernel vulnerability that can cause block leaks during online repair due to memory allocation failures. Defenders should verify Linux kernel versions, prioritize patching, and monitor system logs.

  • Verify Linux kernel versions to assess exposure
  • Prioritize patching or applying compensating controls for affected systems
  • Monitor system logs for indicators of potential block leaks

Technical summary

The Linux kernel vulnerability CVE-2026-98445 involves a memory allocation failure in the xrep_newbt_add_blocks function, potentially causing online repair to leak blocks. The issue is resolved by using a NOFAIL allocation due to the small size of the new btree space reservation object (~48 bytes). This vulnerability affects Linux kernel versions and can be mitigated by patching or applying compensating controls. Defenders should verify Linux kernel versions, prioritize patching, and monitor system logs to address potential block leaks.

Defensive priority

Verify Linux kernel versions and assess exposure; prioritize patching or applying compensating controls for affected systems.

Recommended defensive actions

  • Verify Linux kernel versions to assess exposure
  • Prioritize patching or applying compensating controls for affected systems
  • Monitor system logs for indicators of potential block leaks
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Kernel.org references are available for the commits addressing the issue. A memory allocation failure in the Linux kernel's xrep_newbt_add_blocks function can cause online repair to leak blocks previously allocated to write a new btree. The issue arises because callers cannot undo the transaction and return the error; they must either undo all changes and commit the transaction or error out and shut down the filesystem. However, the new btree space reservation object

Sources and references

Verified primary and authoritative sources

  • CVE-2026-98445 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-98445

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-98445 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-98445

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0e0d3372a84029da1768c7a4c4601484af5b58a2

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/3380151cf0ce8ad0c1d356fed51e4b69e1d28e50

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/ab1c416d2377cdc16123ef521aac4da1c468c3d4

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b15c79fca28060fd9c7e77f2c3ebc4ba023974e8

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.