PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-98090 Linux CVE debrief

A vulnerability in the Linux kernel's btrfs module has been resolved, which can cause a crash when a failed sprout operation occurs due to dereferencing a freed device pointer. This issue arises from the btrfs_init_new_device() function switching latest_dev and possibly s_bdev from the seed device to the new sprout device before creating the first writable chunks. If chunk creation or subsequent sprout setup fails, the error path releases the new device without switching those pointers back, leading to potential crashes when btrfs_show_devname() dereferences the freed latest_dev.

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

Who should care

Linux system administrators, kernel maintainers, and users of btrfs file systems should assess exposure and verify patches to prevent potential system crashes or errors in btrfs module usage. They should review Linux kernel versions and distributions for potential exposure, verify system configurations and applied patches, and monitor for potential crashes or errors in btrfs module usage.

Why it matters

A vulnerability in the Linux kernel's btrfs module can cause a crash when a failed sprout operation occurs. Linux system administrators and kernel maintainers should assess exposure and verify patches.

  • Potential system crashes or errors in btrfs module usage
  • Need for verification of Linux kernel versions and patches
  • Importance of monitoring system configurations and applied patches

Technical summary

The Linux kernel's btrfs module has a vulnerability that can cause a crash when a failed sprout operation occurs due to dereferencing a freed device pointer. This happens because btrfs_init_new_device() switches device pointers without properly restoring them if the operation fails. The vulnerability impacts Linux system administrators, kernel maintainers, and users of btrfs file systems, who should assess exposure and verify patches to prevent potential system crashes or errors in btrfs module usage. The issue requires verification of Linux kernel versions and patches, as well as monitoring of system configurations and applied patches.

Defensive priority

Medium

Recommended defensive actions

  • Review Linux kernel versions and distributions for potential exposure
  • Verify system configurations and applied patches
  • Monitor for potential crashes or errors in btrfs module usage
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • 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. The scope of affected systems and versions is not explicitly stated, but it is known that the Linux kernel's btrfs module is impacted. Defenders should verify Linux kernel versions and patches for potential exposure, focusing on btrfs module usage and system configurations.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-98090 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-98090 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/2ee5c4bc11007c51f63f0c1be5d3f07f2b404ff7

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

    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.