CVE-2026-90131

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

ntfs: serialize resident iomap reads with mrec_lock

ntfs_read_iomap_begin_resident() walks the MFT record through ntfs_attr_lookup() -> ntfs_attr_find() without taking ni->mrec_lock, while ntfs_attr_record_resize(), ntfs_make_room_for_attr() and ntfs_resident_attr_record_add() memmove() the same base_ni->mrec buffer under that lock. map_mft_record() only takes a reference and does not serialize, so the reader can observe torn attribute length and offset fields while a writer is relocating the records.

KCSAN reports the race between the mmap read fault path and both link() and unlink():

BUG: KCSAN: data-race in ntfs_attr_find / ntfs_attr_record_resize

write to 0xffff888100af1018 of 4 bytes by task 96 on cpu 1: ntfs_attr_record_resize+0xd2/0x130 ntfs_attr_record_rm+0xad/0x530 ntfs_delete+0x224/0x640 ntfs_unlink+0x14d/0x280 vfs_unlink+0x157/0x520

read to 0xffff888100af1018 of 4 bytes by task 95 on cpu 0: ntfs_attr_find+0x104/0x5b0 ntfs_attr_lookup+0x39c/0x10c0 ntfs_read_iomap_begin_resident+0xc6/0x230 ntfs_read_iomap_begin+0x5d/0xa0 iomap_iter+0x2e2/0x6e0 iomap_read_folio+0x147/0x2a0 ntfs_read_folio+0x108/0x170 filemap_read_folio+0x35/0x100 filemap_fault+0x993/0x1000

value changed: 0x00000250 -> 0x000001f0

The address is mrec + 0x18, i.e. mft_record.bytes_in_use, and the change is the 96 bytes of one $FILE_NAME attribute being removed.

Keep base_ni->mrec_lock from the resident read iomap lookup through iomap_end(). This protects both the attribute walk and the subsequent copy from iomap->inline_data, which points into the MFT record. The non-resident path is left alone: ntfs_lookup() already holds the directory inode's mrec_lock when it reads an index folio through read_mapping_folio(), and taking the lock in the shared wrapper deadlocks there with recursive locking on mrec_lock. The comment above the read_mapping_folio() call in fs/ntfs/dir.c notes the same hazard.

The seek path uses the same lookup helper but does not dereference iomap->inline_data. Release the lock before returning from that path, whereas the regular read path records base_ni in iomap->private and releases the lock from its iomap_end() callback.

Tested with a reproducer that faults in a 16-byte resident file while another thread runs link()/unlink() on it. Before: 40 KCSAN reports in about one second. After: no reports in 180 seconds over 206,090 read iterations and 423,540 link/unlink cycles. A PROVE_LOCKING build shows no lockdep splat with the same reproducer running for 60 seconds.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

ntfs: serialize resident iomap reads with mrec_lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: serialize resident iomap reads with mrec_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0400e0d50eb3be19c98323faa322b652e4ae3f99

Vendor Advisories for CVE-2026-90131(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 03:07 UTCEG score recompute
  2. 2026-10-05 03:07 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 14:00 UTCGHSA enrichment
  5. 2026-10-04 00:56 UTCEG score recompute
  6. 2026-10-04 00:56 UTCGHSA enrichment
  7. 2026-10-03 11:52 UTCGHSA enrichment
  8. 2026-10-02 22:42 UTCEG score recompute
  9. 2026-10-02 22:42 UTCGHSA enrichment
  10. 2026-10-02 09:36 UTCGHSA enrichment
  11. 2026-10-01 20:32 UTCEG score recompute
  12. 2026-10-01 20:32 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 07:19 UTCGHSA enrichment
  15. 2026-09-30 18:15 UTCEG score recompute
  16. 2026-09-30 18:15 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 05:07 UTCGHSA enrichment
  19. 2026-09-29 16:02 UTCEG score recompute
  20. 2026-09-29 16:02 UTCGHSA enrichment
  21. 2026-09-29 02:58 UTCEG score recompute
  22. 2026-09-29 02:58 UTCGHSA enrichment
  23. 2026-09-28 13:54 UTCEG score recompute
  24. 2026-09-28 13:54 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 42 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 00:50 UTCGHSA enrichment
  3. 2026-09-27 11:45 UTCGHSA enrichment
  4. 2026-09-26 22:41 UTCEG score recompute
  5. 2026-09-26 22:41 UTCGHSA enrichment
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-26 09:36 UTCEG score recompute
  8. 2026-09-26 09:36 UTCGHSA enrichment
  9. 2026-09-25 20:28 UTCGHSA enrichment
  10. 2026-09-25 07:24 UTCGHSA enrichment
  11. 2026-09-24 18:20 UTCEG score recompute
  12. 2026-09-24 18:20 UTCGHSA enrichment
  13. 2026-09-24 14:04 UTCEPSS rescore
  14. 2026-09-24 05:16 UTCEG score recompute
  15. 2026-09-24 05:16 UTCGHSA enrichment
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 16:11 UTCGHSA enrichment
  18. 2026-09-23 03:07 UTCEG score recompute
  19. 2026-09-23 03:07 UTCGHSA enrichment
  20. 2026-09-22 16:01 UTCEPSS rescore
  21. 2026-09-22 14:03 UTCGHSA enrichment
  22. 2026-09-22 00:59 UTCEG score recompute
  23. 2026-09-22 00:59 UTCGHSA enrichment
  24. 2026-09-21 21:09 UTCEPSS rescore
  25. 2026-09-21 11:55 UTCGHSA enrichment
  26. 2026-09-20 22:50 UTCEG score recompute
  27. 2026-09-20 22:50 UTCGHSA enrichment
  28. 2026-09-20 20:16 UTCEPSS rescore
  29. 2026-09-20 09:46 UTCGHSA enrichment
  30. 2026-09-19 20:41 UTCEG score recompute
  31. 2026-09-19 20:41 UTCGHSA enrichment
  32. 2026-09-19 07:37 UTCEG score recompute
  33. 2026-09-19 07:37 UTCGHSA enrichment
  34. 2026-09-18 19:28 UTCEPSS rescore
  35. 2026-09-18 18:31 UTCEG score recompute
  36. 2026-09-18 18:31 UTCGHSA enrichment
  37. 2026-09-18 18:05 UTCEG score recompute▲ 7.10
  38. 2026-09-18 18:05 UTCGHSA enrichment
  39. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  40. 2026-09-17 17:23 UTCNVD update
  41. 2026-09-17 16:47 UTCEG score recompute
  42. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90131?
CVE-2026-90131 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: serialize resident iomap reads with mrec_lock ntfsreadiomapbeginresident() walks the MFT record through ntfsattrlookup() -> ntfsattrfind() without taking ni->mrec_lock, while ntfsattrrecordresize(), ntfsmakeroomfor_attr() and…
When was CVE-2026-90131 disclosed?
CVE-2026-90131 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90131 actively exploited?
CVE-2026-90131 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90131?
CVE-2026-90131 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90131?
No fix for CVE-2026-90131 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90131 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90131

Explore →

Is Your Infrastructure Affected by CVE-2026-90131?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs