CVE-2023-54056
published 2025-12-24CVE-2023-54056: In the Linux kernel, the following vulnerability has been resolved: kheaders: Use array declaration instead of char Under CONFIG_FORTIFY_SOURCE, memcpy() will…
PriorityP423low5.5
EPSS
0.20%
9.8th percentile
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
...
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.37-1 (bookworm) | linux 6.1.37-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 43d8ce9d65a54846d378545770991e65838981e0 < 719459877d58c8aced5845c1e5b98d8d87d09197 | 719459877d58c8aced5845c1e5b98d8d87d09197 |
| linux | linux | >= 43d8ce9d65a54846d378545770991e65838981e0 < fcd2da2e6bf2640a31a2a5b118b50dc3635c707b | fcd2da2e6bf2640a31a2a5b118b50dc3635c707b |
| linux | linux | >= 43d8ce9d65a54846d378545770991e65838981e0 < 4a07d2d511e2703efd4387891d49e0326f1157f3 | 4a07d2d511e2703efd4387891d49e0326f1157f3 |
| linux | linux | >= 43d8ce9d65a54846d378545770991e65838981e0 < b9f6845a492de20679b84bda6b08be347c5819da | b9f6845a492de20679b84bda6b08be347c5819da |
| linux | linux | >= 43d8ce9d65a54846d378545770991e65838981e0 < d6d1af6b8611801b585c53c0cc63626c8d339e96 | d6d1af6b8611801b585c53c0cc63626c8d339e96 |
| linux | linux | >= 43d8ce9d65a54846d378545770991e65838981e0 < 82d2e01b95c439fe55fab5e04fc83387c42d3a48 | 82d2e01b95c439fe55fab5e04fc83387c42d3a48 |
| linux | linux | >= 43d8ce9d65a54846d378545770991e65838981e0 < b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb | b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.37-1 | 6.1.37-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 5.11.0 < 5.15.111 | 5.15.111 |
| linux | linux_kernel | >= 5.16.0 < 6.1.28 | 6.1.28 |
| linux | linux_kernel | >= 5.2.0 < 5.4.243 | 5.4.243 |
| linux | linux_kernel | >= 5.5.0 < 5.10.180 | 5.10.180 |
| linux | linux_kernel | >= 6.2.0 < 6.2.15 | 6.2.15 |
| linux | linux_kernel | >= 6.3.0 < 6.3.2 | 6.3.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: kheaders: Use array declaration instead of char
vendor_redhat·2025-12-24·CVSS 5.5
CVE-2023-54056 [LOW] CWE-843 kernel: kheaders: Use array declaration instead of char
kernel: kheaders: Use array declaration instead of char
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
...
A false positive buffer overflow detection was found in the Linux kernel's kheaders module. When CON
Debian
CVE-2023-54056: linux - In the Linux kernel, the following vulnerability has been resolved: kheaders: U...
vendor_debian·2023
CVE-2023-54056 CVE-2023-54056: linux - In the Linux kernel, the following vulnerability has been resolved: kheaders: U...
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 ...
Scope: local
bookworm: resolved (fixed in 6.1.37-1)
bullseye: resolved (fixed in 5.10.191-1)
forky: resolved (fixed in 6.3.7-1)
sid: resolved (fixed in 6.3.7-1
OSV
kheaders: Use array declaration instead of char
osv·2025-12-24
CVE-2023-54056 kheaders: Use array declaration instead of char
kheaders: Use array declaration instead of char
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
...
OSV
CVE-2023-54056: In the Linux kernel, the following vulnerability has been resolved: kheaders: Use array declaration instead of char Under CONFIG_FORTIFY_SOURCE, memcp
osv·2025-12-24
CVE-2023-54056 CVE-2023-54056: In the Linux kernel, the following vulnerability has been resolved: kheaders: Use array declaration instead of char Under CONFIG_FORTIFY_SOURCE, memcp
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 ...
GHSA
GHSA-w8p6-7x4v-892g: In the Linux kernel, the following vulnerability has been resolved:
kheaders: Use array declaration instead of char
Under CONFIG_FORTIFY_SOURCE, mem
ghsa_unreviewed·2025-12-24
CVE-2023-54056 GHSA-w8p6-7x4v-892g: In the Linux kernel, the following vulnerability has been resolved:
kheaders: Use array declaration instead of char
Under CONFIG_FORTIFY_SOURCE, mem
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
...
No detection rules found.
No public exploits indexed.
Wiz
CVE-2023-54056 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-54056 CVE-2023-54056 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-54056 :
Linux Kernel vulnerability analysis and mitigation
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
...
Source : NVD
Published December 24, 2025
CNA Score N/A
Affected Technologies
Bugzilla
CVE-2023-54056 kernel: kheaders: Use array declaration instead of char
bugzilla·2025-12-24
CVE-2023-54056 [LOW] CVE-2023-54056 kernel: kheaders: Use array declaration instead of char
CVE-2023-54056 kernel: kheaders: Use array declaration instead of char
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
...
Discussion:
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/20251
https://git.kernel.org/stable/c/4a07d2d511e2703efd4387891d49e0326f1157f3https://git.kernel.org/stable/c/719459877d58c8aced5845c1e5b98d8d87d09197https://git.kernel.org/stable/c/82d2e01b95c439fe55fab5e04fc83387c42d3a48https://git.kernel.org/stable/c/b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fbhttps://git.kernel.org/stable/c/b9f6845a492de20679b84bda6b08be347c5819dahttps://git.kernel.org/stable/c/d6d1af6b8611801b585c53c0cc63626c8d339e96https://git.kernel.org/stable/c/fcd2da2e6bf2640a31a2a5b118b50dc3635c707b
2025-12-24
Published