CVE-2026-53015

Analyzed Analyzed - Analysis Complete

Integer Overflow in EROFS Linux Kernel Filesystem

Publication date: 2026-06-24

Last updated on: 2026-07-15

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: erofs: unify lcn as u64 for 32-bit platforms As sashiko reported [1], `lcn` was typed as `unsigned long` (or `unsigned int` sometimes), which is only 32 bits wide on 32-bit platforms, which causes `(lcn << lclusterbits)` to be truncated at 4 GiB. In order to consolidate the logic, just use `u64` consistently around the codebase. [1] https://sashiko.dev/r/20260420034612.1899973-1-hsiangkao%40linux.alibaba.com

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-24

Last Modified

2026-07-15

Generated

2026-08-04

AI Q&A

2026-06-24

EPSS Evaluated

2026-08-02

NVD

CVE-2026-53015

EUVD

EUVD-2026-38883

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.13 (inc) to 6.18.33 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.10 (exc)
linux	linux_kernel	From 5.3 (inc) to 6.12.91 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's erofs filesystem code where the variable 'lcn' was defined as 'unsigned long' or sometimes 'unsigned int'. On 32-bit platforms, these types are only 32 bits wide, which causes the calculation '(lcn << lclusterbits)' to be truncated at 4 GiB.

The issue was that the truncation could lead to incorrect behavior when handling large files or data beyond 4 GiB. The fix was to unify the 'lcn' type as a 64-bit unsigned integer (u64) consistently throughout the codebase to prevent this truncation.

Impact Analysis

Because the 'lcn' value was truncated on 32-bit platforms, this could cause incorrect file system behavior when dealing with files or data larger than 4 GiB. This might lead to data corruption, incorrect file access, or system instability when using the erofs filesystem on affected systems.

Hi! I’m here to help you understand CVE-2026-53015. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70