CVE-2026-53027
Last modified
CVE-2026-53027 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked() When a compressed or sparse attribute has its clusters frame-aligned, vcn is rounded down to the frame start using cmask, which can result in vcn != vcn0. In this case, vcn and vcn0 may reside in different attribute segments. The code already handles the case where vcn is in a different segment by loading its runs before allocation. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked() When a compressed or sparse attribute has its clusters frame-aligned, vcn is rounded down to the frame start using cmask, which can result in vcn != vcn0. In this case, vcn and vcn0 may reside in different attribute segments. The code already handles the case where vcn is in a different segment by loading its runs before allocation. However, it fails to load runs for vcn0 when vcn0 resides in a different segment than vcn. This causes run_lookup_entry() to return SPARSE_LCN for vcn0 since its segment was never loaded into the in-memory run list, triggering the WARN_ON(1). Fix this by adding a missing check for vcn0 after the existing vcn segment check. If vcn0 falls outside the current segment range [svcn, evcn1), find and load the attribute segment containing vcn0 before performing the run lookup. The following scenario triggers the bug: attr_data_get_block_locked() vcn = vcn0 & cmask <- vcn != vcn0 after frame alignment load runs for vcn segment <- vcn0 segment not loaded! attr_allocate_clusters() <- allocation succeeds run_lookup_entry(vcn0) <- vcn0 not in run -> SPARSE_LCN WARN_ON(1) <- bug fires here!
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.1.132, < 6.2 |
| Linux | Linux Kernel | >= 6.2, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-53027?
How severe is CVE-2026-53027?
How do I fix CVE-2026-53027?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53021In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53022In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53023In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53024In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53025In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53026In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53028In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53029In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5303The ACAP framework contains a Time-of-Check to Time-of-Use (…5.7
- CVE-2026-53030In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53031In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53032In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53027?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
