CVE-2023-54056
Description
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:
ikheaders_read+0x45/0x50 [kheaders] kernfs_fop_read_iter+0x1a4/0x2f0 ...
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A Linux kernel buffer overflow (CVE-2023-54056) occurs when reading kernel headers because the kheaders data variable is declared as a single char, causing FORTIFY_SOURCE to trigger a false BUG.
The vulnerability lies in the Linux kernel's kheaders module, which exposes kernel headers as a compressed tar archive via /sys/kernel/kheaders.tar.xz. The global variable kernel_headers_data was declared as a single char instead of a proper byte array, causing the FORTIFY_SOURCE protection mechanism to misinterpret the intended array size when memcpy() operations are performed on it.
To exploit this, a user with local access can simply read the sysfs file /sys/kernel/kheaders.tar.xz. When the kernel's ikheaders_read function copies the kernel headers data, the FORTIFY_SOURCE check sees the destination as a one-byte buffer and triggers a false positive buffer overflow detection, leading to a kernel panic.
The impact is a local denial of service. An unprivileged local user can trigger a kernel BUG (machine check exception) and crash the system by issuing a simple cat command on the exposed sysfs file. This does not require any special capabilities beyond the ability to read the sysfs node.
The fix changes the declaration of kernel_headers_data to an array (e.g., extern char kernel_headers_data[]), which correctly conveys the object's length to FORTIFY_SOURCE checks. Patched versions are available in the stable kernel trees; users should apply the corresponding commit for their kernel version [1][2][3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
7719459877d58fcd2da2e6bf24a07d2d511e2b9f6845a492dd6d1af6b861182d2e01b95c4b69edab47f1dVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- git.kernel.org/stable/c/4a07d2d511e2703efd4387891d49e0326f1157f3nvd
- git.kernel.org/stable/c/719459877d58c8aced5845c1e5b98d8d87d09197nvd
- git.kernel.org/stable/c/82d2e01b95c439fe55fab5e04fc83387c42d3a48nvd
- git.kernel.org/stable/c/b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fbnvd
- git.kernel.org/stable/c/b9f6845a492de20679b84bda6b08be347c5819danvd
- git.kernel.org/stable/c/d6d1af6b8611801b585c53c0cc63626c8d339e96nvd
- git.kernel.org/stable/c/fcd2da2e6bf2640a31a2a5b118b50dc3635c707bnvd
News mentions
0No linked articles in our index yet.