5.5

CVE-2026-53027: linux

CVSS: 5.5v3.1MediumModified
AliasesUBUNTU-CVE-2026-53027DEBIAN-CVE-2026-53027CGA-28fh-q4qp-p736
Published 24-06-2026Last modified 24-07-2026

Vulnerability summary

CVE-2026-53027 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.12% chance of exploitation in the next 30 days, higher than 1.8% of scored vulnerabilities.

Overall risk
22/100
0100
Low · default modelHow is this calculated?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.12%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 13 · Related 14

Timeline

  1. 24-06-2026
    PublishedVulnerability first disclosed.
  2. 24-07-2026
    Last modifiedVulnerability information updated.

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!

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.12%

Chance of exploitation in the next 30 days

Percentile

2%

Versus all other CVEs

30-day change

0.00 pp

From 0.12% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.12%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Ubuntu141 products
  • linuxAll versions (No fix recorded) | < 6.8.0-147.147 | < 7.0.0-28.28
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1067.70 | < 7.0.0-1009.9
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard38 products
  • hyperv-daemons-6.18All versions (No fix recorded)
  • linux-aws-6.12All versions (No fix recorded)
  • linux-aws-6.18All versions (No fix recorded) | < 6.18.39-r0
  • linux-aws-6.18-boot-installed< 6.18.39-r0
  • linux-aws-6.18-bootcAll versions (No fix recorded) | < 6.18.39-r0
Debian2 products
  • linuxAll versions (No fix recorded) | < 6.12.96-1 | < 7.0.10-1
  • linux-6.12< 6.12.100-1~deb12u1
Linux2 products
  • linux≥ c380b52f6c5702cc4bdda5e6d456d6c19a201a0b, < ea59d9dbc5504e29d420ac4aab774cbce39b0e69 | ≥ c380b52f6c5702cc4bdda5e6d456d6c19a201a0b, < d68a14450783ecc5fddae957ac4e1c546dfcfb73 | ≥ c380b52f6c5702cc4bdda5e6d456d6c19a201a0b, < 08fad5d5a26cc55c0ecb68ac59ba3be5e31f4147 | ≥ c380b52f6c5702cc4bdda5e6d456d6c19a201a0b, < 2b4ae1ce613ade8a7e118fba4a5a77cd23e97e54 | ≥ c380b52f6c5702cc4bdda5e6d456d6c19a201a0b, < d7ea8495fd307b58f8867acd81a1b40075b1d3ba | 406a037d93b769bca248476bd14bbe548dc1ec35 | ≥ 6.1.132, < 6.2 | 6.2
  • linux_kernel≥ 6.1.132, < 6.2 | ≥ 6.2, < 7.0.10

4 vendors · 183 products

References

22 links
Show all 22 references