CVE-2026-63815
Received Received - Intake

Integer Underflow in F2FS Leading to Out-of-Bounds Read

Vulnerability report for CVE-2026-63815, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-19

Last updated on: 2026-07-19

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: bound i_inline_xattr_size for non-inline-xattr inodes When the flexible_inline_xattr feature is enabled, do_read_inode() loads the on-disk i_inline_xattr_size unconditionally: if (f2fs_sb_has_flexible_inline_xattr(sbi)) fi->i_inline_xattr_size = le16_to_cpu(ri->i_inline_xattr_size); but sanity_check_inode() only range-checks it when the inode also has the FI_INLINE_XATTR flag set. An inode that carries an inline dentry or inline data but not FI_INLINE_XATTR -- the normal layout for an inline directory -- therefore keeps a fully attacker-controlled i_inline_xattr_size from a crafted image. get_inline_xattr_addrs() returns that value with no flag gating, so it feeds the inode geometry: MAX_INLINE_DATA() = 4 * (CUR_ADDRS_PER_INODE - i_inline_xattr_size - 1) NR_INLINE_DENTRY() = MAX_INLINE_DATA() * BITS_PER_BYTE / (...) addrs_per_page() = CUR_ADDRS_PER_INODE - i_inline_xattr_size A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY() negative, so make_dentry_ptr_inline() sets d->max (int) to a negative value. The inline directory walk then compares an unsigned long bit_pos against that negative d->max, which is promoted to a huge unsigned bound, and reads far past the inline area: while (bit_pos < d->max) /* fs/f2fs/dir.c */ ... test_bit_le(bit_pos, d->bitmap) / d->dentry[bit_pos] ... Mounting a crafted image and reading such a directory triggers an out-of-bounds read in f2fs_fill_dentries(); the same underflow also corrupts ADDRS_PER_INODE for regular files. Validate i_inline_xattr_size against MAX_INLINE_XATTR_SIZE whenever the flexible_inline_xattr feature is enabled -- i.e. whenever the value is loaded from disk and consumed -- and keep the lower MIN_INLINE_XATTR_SIZE bound gated on inodes that actually carry an inline xattr, so legitimate inodes with i_inline_xattr_size == 0 are still accepted.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-19
Last Modified
2026-07-19
Generated
2026-07-20
AI Q&A
2026-07-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
linux_kernel f2fs *
linux kernel *
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel's F2FS filesystem allows an attacker to trigger an out-of-bounds read by manipulating the i_inline_xattr_size value in a crafted filesystem image. When the flexible_inline_xattr feature is enabled, the kernel loads this size without proper validation for non-inline-xattr inodes. A large or negative value causes the inline directory walk to read far beyond allocated memory, potentially exposing sensitive data or causing crashes.

Detection Guidance

This vulnerability is specific to the Linux kernel's F2FS filesystem and requires a crafted filesystem image to trigger. Detection involves checking kernel logs for filesystem errors or crashes during mount operations. Monitor for kernel oops messages or filesystem corruption errors when mounting F2FS volumes. No direct network detection commands are applicable.

Impact Analysis

If exploited, this vulnerability could allow an attacker to read sensitive kernel memory or cause a denial-of-service by crashing the system. It requires a crafted filesystem image, so users are impacted only if they mount untrusted images. Systems using F2FS with the flexible_inline_xattr feature enabled are at risk.

Compliance Impact

This vulnerability is specific to the Linux kernel's F2FS file system and involves an out-of-bounds read due to improper validation of inline xattr size. It does not directly impact compliance with standards like GDPR or HIPAA, as those focus on data protection, privacy, and security controls rather than file system vulnerabilities.

Mitigation Strategies

Apply the latest kernel patches that fix the i_inline_xattr_size validation issue in F2FS. Disable the flexible_inline_xattr feature if not required. Avoid mounting untrusted F2FS filesystem images. Monitor kernel security advisories for updates related to this CVE.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63815. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart