All reports
Low

kernel: kheaders: Use array declaration instead of char

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-54056

Probability of exploitation in the next 30 days: 0.23%

FIRST EPSS · 2026-11-19

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 ...

A false positive buffer overflow detection was found in the Linux kernel's kheaders module. When CONFIG_FORTIFY_SOURCE is enabled, memcpy() performs size checks on source and destination buffers. The kernel_headers_data symbol was declared as "char" rather than an array, causing FORTIFY_SOURCE to incorrectly detect a buffer overflow when reading /sys/kernel/kheaders.tar.xz. The fix changes the declaration to an array type to match actual usage.