boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, August 20, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-53027

Linux Linux — fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked()
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   L   L   N  U  N  N  H    5.5   .0012    2.4     —
AFFECTED
  Product  Versions                                    Fixed
  Linux    c380b52f6c5702cc4bdda5e6d456d6c19a201a0b –  —
  Linux    6.2 –                                       6.6.145
TIMELINE
  Jun 9   Reserved by Linux
  Jun 24  Published (CNA: Linux)
  Jul 24  ENRICHED — CVE-2026-53027 (Linux). Received CVSS 5.5 and CPE data from NVD.
CNA: Linux · CVSS v3.1 · 5 references · NVD status: Modified

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!

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
June 9, 2026ReservedReserved by Linux
June 24, 2026PublishedPublished (CNA: Linux)
July 24, 2026ENRICHEDENRICHED — CVE-2026-53027 (Linux). Received CVSS 5.5 and CPE data from NVD.

Affected

Affected products and packages — 2 rows
VendorProduct / PackageEcosystemVersion introducedFixed
LinuxLinuxc380b52f6c5702cc4bdda5e6d456d6c19a201a0b
LinuxLinux6.26.6.145

References (5)

Related

Authoritative record: CVE-2026-53027 at cve.org

Vendors: linux

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-53027 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, August 20, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.