CVE-2023-54056

kheaders: Use array declaration instead of char

N/A

Published: December 24, 2025 at 12:23 PM UTC

Updated: June 17, 2026 at 06:46 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

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: <TASK> ikheaders_read+0x45/0x50 [kheaders] kernfs_fop_read_iter+0x1a4/0x2f0 ...

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.2 ≤ v < 5.10.1805.2 ≤ v < 5.15.1115.2 ≤ v < 5.4.2435.2 ≤ v < 6.1.285.2 ≤ v < 6.2.155.2 ≤ v < 6.3.25.2 ≤ v < 6.443d8ce9d65a54846d378545770991e65838981e05.2

Vendor states this is fixed in 4a07d2d511e2703efd4387891d49e0326f1157f3 (fixed)

Vendor states this is fixed in 719459877d58c8aced5845c1e5b98d8d87d09197 (fixed)

Vendor states this is fixed in 82d2e01b95c439fe55fab5e04fc83387c42d3a48 (fixed)

Vendor states this is fixed in b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb (fixed)

Vendor states this is fixed in b9f6845a492de20679b84bda6b08be347c5819da (fixed)

Vendor states this is fixed in d6d1af6b8611801b585c53c0cc63626c8d339e96 (fixed)

Vendor states this is fixed in fcd2da2e6bf2640a31a2a5b118b50dc3635c707b (fixed)

Vendor states this is fixed in 5.10.180 (unaffected)

Vendor states this is fixed in 5.15.111 (unaffected)

Vendor states this is fixed in 5.2 (unaffected)

Vendor states this is fixed in 5.4.243 (unaffected)

Vendor states this is fixed in 6.1.28 (unaffected)