Skip to main content
VulnerabilityPublished Updated

CVE-2026-53027: Linux kernel · fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked()

Source GCVE Database

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Since this is a Linux kernel vulnerability, monitor official Linux kernel releases and apply updates when available to ensure the fix is applied. No other mitigations are specified.

Description

A vulnerability in the Linux kernel's NTFS3 filesystem driver was fixed involving improper handling of run loading for vcn0 in the attr_data_get_block_locked() function. The bug occurs when compressed or sparse attributes have clusters aligned to frame boundaries, causing a mismatch between vcn and vcn0. This leads to missing run loading for vcn0 when it resides in a different attribute segment, triggering a kernel warning and potentially causing allocation inconsistencies. The issue has been resolved by adding a check to load the attribute segment containing vcn0 before run lookup.

References

Community reviews

Loading reviews…