x86, relocs: Ignore relocations in .notes section
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045 · < af2a9f98d884205145fd155304a6955822ccca1c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86, relocs: Ignore relocations in .notes section
When building with CONFIG_XEN_PV=y, .text symbols are emitted into the .notes section so that Xen can find the "startup_xen" entry point. This information is used prior to booting the kernel, so relocations are not useful. In fact, performing relocations against the .notes section means that the KASLR base is exposed since /sys/kernel/notes is world-readable.
To avoid leaking the KASLR base without breaking unprivileged tools that are expecting to read /sys/kernel/notes, skip performing relocations in the .notes section. The values readable in .notes are then identical to those found in System.map.
From the CVE record · Linux
Linux kernels built with CONFIG_XEN_PV=y can expose the KASLR base through relocations in the world-readable /sys/kernel/notes file. A local unprivileged user can read the file to obtain that information; no user interaction is required.
Operators running Linux kernels built with CONFIG_XEN_PV=y should check their vendor advisory for affected versions.