Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 50 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23235, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < e85a99db9ab85dfc30d93b0ca0e9156f3127f55a
    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < 438a405fbad6882df0e34b3e1a16839a71f04240
    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < 6a6c07a9b49e43f0df42d7118fc76aa555c73d98
    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < eebd72cff518ac87e660aefb8a41224bd88c32ce
    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < 4ef30b9f1641c9e877792df6b049f1cf507d002d
    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < d4a594dd952df123cbdcdee9b9640d9d55e4a954
    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < 3a905e183c047577b154f08a78ac3039e9454703
    • affected b59d0bae6ca30c496f298881616258f9cde0d9c6 – < 98ea0039dbfdd00e5cc1b9a8afa40434476c0955
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 5.10.251 – ≤ 5.10.*
    • unaffected 5.15.201 – ≤ 5.15.*
    • unaffected 6.1.164 – ≤ 6.1.*
    • unaffected 6.6.127 – ≤ 6.6.*
    • unaffected 6.12.74 – ≤ 6.12.*
    • unaffected 6.18.13 – ≤ 6.18.*
    • unaffected 6.19.3 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23235 badge
[![CVE-2026-23235](https://cveledger.app/badge/CVE-2026-23235.svg)](https://cveledger.app/cve/CVE-2026-23235)

Record last updated .