CVE-2026-23235
Vulnérabilité non évaluée dans Linux (Linux)
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.
Gravité et risque d'exploitation
CVE-2026-23235 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.16 %, ce qui la place devant 4.6 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions <e85a99db9ab85dfc30d93b0ca0e9156f3127f55a, 6.19.3, <=6.1.*, <=6.12.*, 5.15.201, 6.12.74, b59d0bae6ca30c496f298881616258f9cde0d9c6, <4ef30b9f1641c9e877792df6b049f1cf507d002d, 6.1.164, 6.18.13, 0, 3.12, 7.0, <=5.10.*, <=6.6.*, <=6.19.*, <d4a594dd952df123cbdcdee9b9640d9d55e4a954, <98ea0039dbfdd00e5cc1b9a8afa40434476c0955, <3a905e183c047577b154f08a78ac3039e9454703, <=6.18.*, <6a6c07a9b49e43f0df42d7118fc76aa555c73d98, <eebd72cff518ac87e660aefb8a41224bd88c32ce, <3.12, <=*, <=5.15.*, 6.6.127, <438a405fbad6882df0e34b3e1a16839a71f04240, 5.10.251) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- 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
