CVE-2026-53303

Analyzed Analyzed - Analysis Complete

Race Condition in F2FS Filesystem Extension List Handling

Publication date: 2026-06-26

Last updated on: 2026-07-06

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: protect extension_list reading with sb_lock in f2fs_sbi_show() In f2fs_sbi_show(), the extension_list, extension_count and hot_ext_count are read without holding sbi->sb_lock. If a concurrent sysfs store modifies the extension list via f2fs_update_extension_list(), the show path may read inconsistent count and array contents, potentially leading to out-of-bounds access or displaying stale data. Fix this by holding sb_lock around the entire extension list read and format operation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-26

Last Modified

2026-07-06

Generated

2026-07-17

AI Q&A

2026-06-26

EPSS Evaluated

2026-07-15

NVD

CVE-2026-53303

EUVD

EUVD-2026-39838

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.2 (inc) to 6.6.141 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.91 (exc)
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 4.17 (inc) to 6.1.175 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-125	The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's f2fs file system code, specifically in the function f2fs_sbi_show(). The issue is that the extension_list, extension_count, and hot_ext_count are read without holding the sb_lock. If another process concurrently modifies the extension list via f2fs_update_extension_list(), the reading process may access inconsistent or stale data. This can lead to out-of-bounds memory access or incorrect information being displayed.

The fix involves holding the sb_lock during the entire read and format operation of the extension list to ensure data consistency and prevent race conditions.

Impact Analysis

This vulnerability can cause the Linux kernel to read inconsistent or stale data from the f2fs extension list, potentially leading to out-of-bounds memory access. Such behavior may result in system instability, crashes, or unexpected behavior when interacting with the file system.

Mitigation Strategies

To mitigate this vulnerability, update the Linux kernel to a version where the fix has been applied. The fix involves holding the sb_lock around the entire extension list read and format operation in f2fs_sbi_show(), preventing out-of-bounds access or stale data display.

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

0/70