In the Linux kernel, the following vulnerability has been resolved: ntfs: serialize resident iomap reads with mrec_lock… (CVE-2026-90131)
A race condition vulnerability in the Linux kernel's NTFS driver was resolved by serializing resident iomap reads with the mrec_lock. The flaw allowed concurrent reads and writes to the MFT record without proper locking, potentially causing torn reads of attribute length and offset fields. This was detected by KCSAN during concurrent mmap read faults and link/unlink operations. The fix involves holding the mrec_lock during resident read iomap lookups to prevent data races. Testing showed the fix eliminated KCSAN reports of the race condition.
AI Analysis
Technical Summary
The Linux kernel NTFS driver had a race condition where ntfs_read_iomap_begin_resident() accessed the MFT record without holding the ni->mrec_lock, while other functions like ntfs_attr_record_resize() modified the same buffer under that lock. This caused torn reads of attribute fields during concurrent access. KCSAN detected data races between mmap read faults and link()/unlink() operations. The fix serializes resident iomap reads by holding mrec_lock from the resident read iomap lookup through iomap_end(), protecting both attribute walking and copying from iomap->inline_data. The non-resident path was not changed due to potential deadlocks. Testing with a reproducer showed the fix eliminated KCSAN race reports.
Potential Impact
The vulnerability could cause torn or inconsistent reads of NTFS MFT record attributes during concurrent file operations, potentially leading to data corruption or kernel instability. The CVSS score of 7.1 indicates high severity with high confidentiality impact and high availability impact, but no integrity impact. There are no known exploits in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel NTFS driver that serializes resident iomap reads with the mrec_lock. Users should update to a kernel version that includes this fix. No additional mitigations are indicated.
In the Linux kernel, the following vulnerability has been resolved: ntfs: serialize resident iomap reads with mrec_lock… (CVE-2026-90131)
Description
A race condition vulnerability in the Linux kernel's NTFS driver was resolved by serializing resident iomap reads with the mrec_lock. The flaw allowed concurrent reads and writes to the MFT record without proper locking, potentially causing torn reads of attribute length and offset fields. This was detected by KCSAN during concurrent mmap read faults and link/unlink operations. The fix involves holding the mrec_lock during resident read iomap lookups to prevent data races. Testing showed the fix eliminated KCSAN reports of the race condition.
CVSS v3.1
Score 7.1high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel NTFS driver had a race condition where ntfs_read_iomap_begin_resident() accessed the MFT record without holding the ni->mrec_lock, while other functions like ntfs_attr_record_resize() modified the same buffer under that lock. This caused torn reads of attribute fields during concurrent access. KCSAN detected data races between mmap read faults and link()/unlink() operations. The fix serializes resident iomap reads by holding mrec_lock from the resident read iomap lookup through iomap_end(), protecting both attribute walking and copying from iomap->inline_data. The non-resident path was not changed due to potential deadlocks. Testing with a reproducer showed the fix eliminated KCSAN race reports.
Potential Impact
The vulnerability could cause torn or inconsistent reads of NTFS MFT record attributes during concurrent file operations, potentially leading to data corruption or kernel instability. The CVSS score of 7.1 indicates high severity with high confidentiality impact and high availability impact, but no integrity impact. There are no known exploits in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel NTFS driver that serializes resident iomap reads with the mrec_lock. Users should update to a kernel version that includes this fix. No additional mitigations are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p65r-ghh2-3f2q
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-90131"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aade52455bf5e2cf5edc1a0
Added to database: 09/19/2026, 01:28:04 UTC
Last enriched: 09/19/2026, 01:52:13 UTC
Last updated: 09/19/2026, 02:41:40 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.