CVE-2026-23235: f2fs: fix out-of-bounds access in sysfs attribute read/write
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix out-of-bounds access in sysfs attribute read/write
Some f2fs sysfs attributes suffer from out-of-bounds memory access and
incorrect handling of integer values whose size is not 4 bytes.
For example:
vm:~# echo 65537 > /sys/fs/f2fs/vde/carve_out
vm:~# cat /sys/fs/f2fs/vde/carve_out
65537
vm:~# echo 4294967297 > /sys/fs/f2fs/vde/atgc_age_threshold
vm:~# cat /sys/fs/f2fs/vde/atgc_age_threshold
1
carve_out maps to {struct f2fs_sb_info}->carve_out, which is a 8-bit
integer. However, the sysfs interface allows setting it to a value
larger than 255, resulting in an out-of-range update.
atgc_age_threshold maps to {struct atgc_management}->age_threshold,
which is a 64-bit integer, but its sysfs interface cannot correctly set
values larger than UINT_MAX.
The root causes are:
1. __sbi_store() treats all default values as unsigned int, which
prevents updating integers larger than 4 bytes and causes out-of-bounds
writes for integers smaller than 4 bytes.
2. f2fs_sbi_show() also assumes all default values are unsigned int,
leading to out-of-bounds reads and incorrect access to integers larger
than 4 bytes.
This patch introduces {struct f2fs_attr}->size to record the actual size
of the integer associated with each sysfs attribute. With this
information, sysfs read and write operations can correctly access and
update values according to their real data size, avoiding memory
corruption and truncation.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23235 is a Linux kernel f2fs bug where some filesystem tuning files can read or write memory using the wrong integer size. This can cause incorrect values, out-of-bounds access, and possible memory corruption. The available sources do not report active exploitation or a CVSS score.
Executive priority
Treat as a routine-to-priority kernel maintenance item for Linux systems using f2fs. It is not currently supported as internet-exploited or actively exploited, but kernel memory corruption bugs deserve timely patching during the next appropriate maintenance window.
Technical view
The flaw is in f2fs sysfs attribute show/store handling. Code treated default values as unsigned int, causing out-of-bounds reads/writes for smaller fields and truncation for larger fields. The kernel fix adds a size field to f2fs_attr so sysfs access matches each backing integer’s actual size.
Likely exposure
Systems using Linux kernels with affected f2fs code and exposed f2fs sysfs attributes may be exposed. Practical reach appears local and tied to permission to read or write /sys/fs/f2fs attributes. Distribution backports may change whether a nominal version is vulnerable.
Exploitation context
The source includes local examples of writing and reading f2fs sysfs attributes, but does not show weaponized exploitation. CISA KEV status is false in the provided data, and no cited source states active exploitation.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. No CVSS, CWE, public exploit status, or distro-specific package mapping is provided. Validate exposure through the exact kernel source or vendor backport status, not version strings alone.
Mitigation direction
Review your Linux vendor’s advisory or kernel changelog for CVE-2026-23235.
Update to a kernel containing the referenced stable f2fs fix commits.
Prioritize systems that mount or rely on f2fs filesystems.
Restrict administrative access to f2fs sysfs attributes as part of normal hardening.
Validation and detection
Inventory Linux hosts using f2fs or loading f2fs kernel support.
Compare running kernel builds against vendor-fixed packages or the referenced stable commits.
Confirm whether /sys/fs/f2fs exists on relevant systems.
Check configuration management for systems pinned to affected kernel builds.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23235 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 4, 2026, 14:36 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.