PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-90131 Linux CVE debrief

A race condition vulnerability in the Linux kernel's NTFS implementation can lead to data corruption or crashes when handling resident I/O operations. The vulnerability arises from the lack of proper synchronization between the `ntfs_read_iomap_begin_resident` function and the `ntfs_attr_record_resize` function, allowing a writer to modify the MFT record while a reader is accessing it. This issue has been resolved by serializing resident I/O operations with the `mrec_lock`.

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

Who should care

Linux kernel developers and maintainers, as well as users of Linux systems that utilize NTFS filesystems, should be aware of this vulnerability and take steps to ensure their systems are patched.

Why it matters

The Linux kernel's NTFS implementation is vulnerable to a race condition that can cause data corruption or crashes when handling resident I/O operations. Linux kernel developers and maintainers, as well as users of Linux systems that utilize NTFS filesystems, should be aware of this vulnerability and take steps to ensure their systems are patched.

  • Data corruption or crashes may occur when handling resident I/O operations on NTFS filesystems.
  • The vulnerability can be exploited to cause denial-of-service conditions.
  • Exploitation may allow for potential data tampering.

Technical summary

The Linux kernel's NTFS implementation is vulnerable to a race condition that can cause data corruption or crashes. The issue arises from the lack of proper synchronization between the `ntfs_read_iomap_begin_resident` function and the `ntfs_attr_record_resize` function. This allows a writer to modify the MFT record while a reader is accessing it, resulting in torn reads of attribute length and offset fields.

Defensive priority

Medium

Recommended defensive actions

  • Review and apply the provided kernel patches to ensure the NTFS implementation is properly synchronized.
  • Monitor Linux kernel updates for any related security patches.
  • Consider implementing additional monitoring and logging to detect potential exploitation attempts.
  • Perform a thorough review of system configurations and NTFS filesystem usage.
  • Implement compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability was reported by KCSAN and involves a data race between `ntfs_attr_find` and `ntfs_attr_record_resize`. The issue allows for torn reads of attribute length and offset fields during MFT record relocation.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-90131 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-90131 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/0400e0d50eb3be19c98323faa322b652e4ae3f99

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

  • Source reference

    Unverified legacy reference

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

    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.