CVE-2026-23235

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-03-04. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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:

  • __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.
  • 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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

March 4, 2026

Last Modified

June 17, 2026

Advisory Details (8)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eebd72cff518ac87e660aefb8a41224bd88c32ce
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e85a99db9ab85dfc30d93b0ca0e9156f3127f55a
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d4a594dd952df123cbdcdee9b9640d9d55e4a954
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98ea0039dbfdd00e5cc1b9a8afa40434476c0955
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a6c07a9b49e43f0df42d7118fc76aa555c73d98
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ef30b9f1641c9e877792df6b049f1cf507d002d
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/438a405fbad6882df0e34b3e1a16839a71f04240
generic

f2fs: fix out-of-bounds access in sysfs attribute read/write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a905e183c047577b154f08a78ac3039e9454703

Vendor Advisories for CVE-2026-23235(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)5.10.251-1
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)6.1.164-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.74-2~bpo12+1 (15 versions)6.12.74-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (102 versions)6.18.13-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(23)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 12:30 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 16:04 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 61 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 20:57 UTCVendor advisory
  8. 2026-08-14 20:57 UTCGHSA enrichment
  9. 2026-08-14 08:37 UTCEG score recompute
  10. 2026-08-14 08:37 UTCVendor advisory
  11. 2026-08-14 08:37 UTCGHSA enrichment
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 00:22 UTCEG score recompute
  14. 2026-08-13 00:22 UTCVendor advisory
  15. 2026-08-13 00:22 UTCGHSA enrichment
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 23:18 UTCEG score recompute
  18. 2026-08-11 23:18 UTCVendor advisory
  19. 2026-08-11 23:18 UTCGHSA enrichment
  20. 2026-08-11 13:42 UTCEPSS rescore
  21. 2026-08-11 05:52 UTCEG score recompute
  22. 2026-08-11 05:52 UTCVendor advisory
  23. 2026-08-11 05:52 UTCGHSA enrichment
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 08:09 UTCVendor advisory
  26. 2026-08-10 08:09 UTCGHSA enrichment
  27. 2026-08-09 20:09 UTCEG score recompute
  28. 2026-08-09 20:09 UTCVendor advisory
  29. 2026-08-09 20:09 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 08:14 UTCEG score recompute
  32. 2026-08-09 08:14 UTCVendor advisory
  33. 2026-08-09 08:14 UTCGHSA enrichment
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 08:03 UTCVendor advisory
  36. 2026-08-08 08:03 UTCGHSA enrichment
  37. 2026-08-07 20:07 UTCEG score recompute
  38. 2026-08-07 20:07 UTCVendor advisory
  39. 2026-08-07 20:07 UTCGHSA enrichment
  40. 2026-08-06 13:46 UTCEPSS rescore
  41. 2026-08-06 02:42 UTCEG score recompute
  42. 2026-08-06 02:42 UTCVendor advisory
  43. 2026-08-06 02:42 UTCGHSA enrichment
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-04 15:10 UTCEPSS rescore
  46. 2026-08-04 10:38 UTCEPSS rescore
  47. 2026-08-04 04:11 UTCEG score recompute
  48. 2026-08-04 04:11 UTCVendor advisory
  49. 2026-08-04 04:11 UTCGHSA enrichment
  50. 2026-08-03 10:35 UTCEPSS rescore
  51. 2026-08-02 19:01 UTCEG score recompute
  52. 2026-08-02 19:01 UTCVendor advisory
  53. 2026-08-02 19:01 UTCGHSA enrichment
  54. 2026-08-02 02:26 UTCEPSS rescore
  55. 2026-08-01 04:15 UTCEPSS rescore
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-27 14:13 UTCEPSS rescore
  58. 2026-07-27 12:56 UTCEG score recompute
  59. 2026-07-27 12:56 UTCVendor advisory
  60. 2026-07-27 12:56 UTCGHSA enrichment
  61. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-23235?
CVE-2026-23235 is a high vulnerability published on March 4, 2026. 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 >…
When was CVE-2026-23235 disclosed?
CVE-2026-23235 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23235 actively exploited?
CVE-2026-23235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.8% of all scored CVEs.
What is the CVSS score of CVE-2026-23235?
CVE-2026-23235 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-23235?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23235, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23235

Explore →

Is Your Infrastructure Affected by CVE-2026-23235?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.