CVE-2023-52436 json
f2fs: explicitly null-terminate the xattr list
published 2024-02-20 2 y ago modified 2026-08-15 2 mo ago also EUVD-2023-57061
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
f2fs: explicitly null-terminate the xattr list
When setting an xattr, explicitly null-terminate the xattr list. This eliminates the fragile assumption that the unused xattr space is always zeroed.
Patch / fix
- Linux Linux 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.74, 6.6.13, 6.7.1, 6.8
- linux Debian 12 6.1.76-1
- linux Debian 14, Debian 13 6.6.13-1
debian advisories DEBIAN-CVE-2023-52436
- linux Ubuntu 20.04 LTS 5.4.0-176.196
- linux Ubuntu 22.04 LTS 5.15.0-102.112
- linux-aws Ubuntu 20.04 LTS 5.4.0-1122.132
- linux-aws Ubuntu 22.04 LTS 5.15.0-1057.63
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1126.135
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1055.63
- linux-gke Ubuntu 22.04 LTS 5.15.0-1054.59
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1069.74
ubuntu advisories UBUNTU-CVE-2023-52436
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/16ae3132ff7746894894927c1892493693b89135 commit
- git.kernel.org/stable/c/12cf91e23b126718a96b914f949f2cdfeadc7b2a commit
- git.kernel.org/stable/c/3e47740091b05ac8d7836a33afd8646b6863ca52 commit
- git.kernel.org/stable/c/32a6cfc67675ee96fe107aeed5af9776fec63f11 commit
- git.kernel.org/stable/c/5de9e9dd1828db9b8b962f7ca42548bd596deb8a commit
- git.kernel.org/stable/c/2525d1ba225b5c167162fa344013c408e8b4de36 commit
- git.kernel.org/stable/c/f6c30bfe5a49bc38cae985083a11016800708fea commit
- git.kernel.org/stable/c/e26b6d39270f5eab0087453d9b544189a38c8564 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-52436 updated cvss 4.5
kernel: f2fs: explicitly null-terminate the xattr list
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/16ae3132ff7746894894927c1892493693b89135
patch
-
git.kernel.org
/stable/c/12cf91e23b126718a96b914f949f2cdfeadc7b2a
patch
-
git.kernel.org
/stable/c/3e47740091b05ac8d7836a33afd8646b6863ca52
patch
-
git.kernel.org
/stable/c/32a6cfc67675ee96fe107aeed5af9776fec63f11
patch
-
git.kernel.org
/stable/c/5de9e9dd1828db9b8b962f7ca42548bd596deb8a
patch
-
git.kernel.org
/stable/c/2525d1ba225b5c167162fa344013c408e8b4de36
patch
-
git.kernel.org
/stable/c/f6c30bfe5a49bc38cae985083a11016800708fea
patch
-
git.kernel.org
/stable/c/e26b6d39270f5eab0087453d9b544189a38c8564
patch
- lists.debian.org /debian-lts-announce/2024/06/msg00016.html
- lists.debian.org /debian-lts-announce/2024/06/msg00020.html
Sources
- CVE List CVE-2023-52436
- NVD CVE-2023-52436
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.