s390/mm: Do not map lowcore with identity mapping
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
6.11
|
In the Linux kernel, the following vulnerability has been resolved:
s390/mm: Do not map lowcore with identity mapping
Since the identity mapping is pinned to address zero the lowcore is always also mapped to address zero, this happens regardless of the relocate_lowcore command line option. If the option is specified the lowcore is mapped twice, instead of only once.
This means that NULL pointer accesses will succeed instead of causing an exception (low address protection still applies, but covers only parts). To fix this never map the first two pages of physical memory with the identity mapping.
From the CVE record · Linux
On s390 systems, the Linux kernel identity mapping also maps the lowcore at address zero, regardless of the relocate_lowcore option. As a result, some NULL pointer accesses succeed instead of causing an exception. The input does not specify whether exploiting this requires local access, authentication, or user interaction.
Engineers running the Linux kernel on s390 systems should check their installed kernel; affected versions are not specified.