CVE-2026-23235

f2fs: fix out-of-bounds access in sysfs attribute read/write

State
Published
Severity
Not scored
Published
Mar 4, 2026
Updated
May 11, 2026
Reserved
Jan 13, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before e85a99db9ab85dfc30d93b0ca0e9156f3127f55aAffected
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before 438a405fbad6882df0e34b3e1a16839a71f04240Affected
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before 6a6c07a9b49e43f0df42d7118fc76aa555c73d98Affected
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before eebd72cff518ac87e660aefb8a41224bd88c32ceAffected
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before 4ef30b9f1641c9e877792df6b049f1cf507d002dAffected
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before d4a594dd952df123cbdcdee9b9640d9d55e4a954Affected
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before 3a905e183c047577b154f08a78ac3039e9454703Affected
  • b59d0bae6ca30c496f298881616258f9cde0d9c6 to before 98ea0039dbfdd00e5cc1b9a8afa40434476c0955Affected
LinuxLinux
  • 3.12Affected
  • before 3.12Not affected
  • 5.10.251 through 5.10.*Not affected
  • 5.15.201 through 5.15.*Not affected
  • 6.1.164 through 6.1.*Not affected
  • 6.6.127 through 6.6.*Not affected
  • 6.12.74 through 6.12.*Not affected
  • 6.18.13 through 6.18.*Not affected
  • 6.19.3 through 6.19.*Not affected
  • 7.0 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.