Linux Kernel up to 7.2.3 ntfs parse_ntfs_boot_sector memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00+ |
Summary
A vulnerability marked as critical has been reported in Linux Kernel up to 7.2.3. This impacts the function parse_ntfs_boot_sector of the component ntfs. The manipulation leads to memory corruption.
This vulnerability is uniquely identified as CVE-2026-89612. Local access is required to approach this attack. No exploit exists.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 7.2.3 and classified as critical. This issue affects the function parse_ntfs_boot_sector of the component ntfs. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: ntfs: reject invalid MFT LCNs from boot sector The NTFS boot sector stores the MFT and MFTMirr locations as unsigned 64-bit LCNs, but parse_ntfs_boot_sector() decoded them into an s64. A crafted high-bit value could therefore become negative and pass the existing upper-bound check. The invalid value then propagated into the MFT zone allocator and could result in an out-of-bounds access to lcn_empty_bits_per_page.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-89612 since 09/11/2026. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are required for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/12/2026).
Upgrading to version 7.2.4 or 7.3-rc1 eliminates this vulnerability. Applying the patch 8f8420b68a6f05ca2b03779d8208814ec539b9e5/cc9d09fef78410bcd37ac05168cbd5f6dd75d3d2 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.7
VulDB Temp Score: 7.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 7.2.4/7.3-rc1
Patch: 8f8420b68a6f05ca2b03779d8208814ec539b9e5/cc9d09fef78410bcd37ac05168cbd5f6dd75d3d2
Timeline
09/11/2026 CVE reserved09/11/2026 VulDB entry created
09/12/2026 Advisory disclosed
09/12/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-89612 (🔒)
GCVE (CVE): GCVE-0-2026-89612
GCVE (VulDB): GCVE-100-402917
Entry
Created: 09/12/2026 01:47Changes: 09/12/2026 01:47 (59)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.