CVE-2023-54056 json
kheaders: Use array declaration instead of char
published 2025-12-24 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2023-60270
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
kheaders: Use array declaration instead of char
Under CONFIG_FORTIFY_SOURCE, memcpy() will check the size of destination and source buffers. Defining kernel_headers_data as "char" would trip this check. Since these addresses are treated as byte arrays, define them as arrays (as done everywhere else).
This was seen with:
$ cat /sys/kernel/kheaders.tar.xz >> /dev/null
detected buffer overflow in memcpy kernel BUG at lib/string_helpers.c:1027! ... RIP: 0010:fortify_panic+0xf/0x20 [...] Call Trace: <TASK> ikheaders_read+0x45/0x50 [kheaders] kernfs_fop_read_iter+0x1a4/0x2f0 ...
Patch / fix
- Linux Linux 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4
- linux Debian 12 6.1.37-1
- linux Debian 14, Debian 13 6.3.7-1
debian advisories DEBIAN-CVE-2023-54056
- linux Ubuntu 20.04 LTS 5.4.0-162.179
- linux Ubuntu 22.04 LTS 5.15.0-79.86
- linux-aws Ubuntu 20.04 LTS 5.4.0-1109.118
- linux-aws Ubuntu 22.04 LTS 5.15.0-1042.47
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1112.121
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1039.47
- linux-gke Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1056.61
ubuntu advisories UBUNTU-CVE-2023-54056
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/719459877d58c8aced5845c1e5b98d8d87d09197 commit
- git.kernel.org/stable/c/fcd2da2e6bf2640a31a2a5b118b50dc3635c707b commit
- git.kernel.org/stable/c/4a07d2d511e2703efd4387891d49e0326f1157f3 commit
- git.kernel.org/stable/c/b9f6845a492de20679b84bda6b08be347c5819da commit
- git.kernel.org/stable/c/d6d1af6b8611801b585c53c0cc63626c8d339e96 commit
- git.kernel.org/stable/c/82d2e01b95c439fe55fab5e04fc83387c42d3a48 commit
- git.kernel.org/stable/c/b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb 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-54056 updated cvss 5.5
kernel: kheaders: Use array declaration instead of char
-
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 moreaffected: workaround, no fix available “To mitigate this issue, prevent the kheaders module from being loaded. See https://access.redhat.com/solutions/41278 for instructions.”
-
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 10 kernelnot 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
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/719459877d58c8aced5845c1e5b98d8d87d09197
- git.kernel.org /stable/c/fcd2da2e6bf2640a31a2a5b118b50dc3635c707b
- git.kernel.org /stable/c/4a07d2d511e2703efd4387891d49e0326f1157f3
- git.kernel.org /stable/c/b9f6845a492de20679b84bda6b08be347c5819da
- git.kernel.org /stable/c/d6d1af6b8611801b585c53c0cc63626c8d339e96
- git.kernel.org /stable/c/82d2e01b95c439fe55fab5e04fc83387c42d3a48
- git.kernel.org /stable/c/b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb
Sources
- CVE List CVE-2023-54056
- NVD CVE-2023-54056
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.