kheaders: Use array declaration instead of char
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 43d8ce9d65a54846d378545770991e65838981e0 · < 82d2e01b95c439fe55fab5e04fc83387c42d3a48| No fix yet |
| Linux Linux |
|
|
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 ...
From the CVE record · Linux
The Linux kernel's kheaders code can trigger a buffer-overflow check under CONFIG_FORTIFY_SOURCE. A local user reading /sys/kernel/kheaders.tar.xz can trigger a kernel BUG; the input does not specify additional authorization requirements.
Anyone running a Linux kernel with kheaders and CONFIG_FORTIFY_SOURCE enabled should check whether their kernel includes the fix; affected versions are not specified.