Buffer overflow in drivers/xen/sys-hypervisor.c
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 84b7625728ea311ea35bdaa0eded53c1c56baeaa · < d5f59216650c51e5e3fcb7517c825bc8047f60ef| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Buffer overflow in drivers/xen/sys-hypervisor.c
The build id returned by HYPERVISOR_xen_version(XENVER_build_id) is neither NUL terminated nor a string.
The first causes a buffer overflow as sprintf in buildid_show will read and copy till it finds a NUL.
00000000 f4 91 51 f4 dd 38 9e 9d 65 47 52 eb 10 71 db 50 |..Q..8..eGR..q.P| 00000010 b9 a8 01 42 6f 2e 32 |...Bo.2| 00000017
So use a memcpy instead of sprintf to have the correct value:
00000000 f4 91 51 f4 dd 00 9e 9d 65 47 52 eb 10 71 db 50 |..Q.....eGR..q.P| 00000010 b9 a8 01 42 |...B| 00000014
(the above have a hack to embed a zero inside and check it's returned correctly).
From the CVE record · Linux
The Linux kernel's Xen sys-hypervisor driver treats a build ID that is not NUL-terminated as a string, causing `buildid_show` to read and copy beyond its bounds. This can cause a buffer overflow. The input does not specify an attacker capability or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel with the Xen sys-hypervisor driver should check their exposure; affected versions were not provided.