s390/mm: Do not map lowcore with identity mapping
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.11, 6.12.44, 6.16.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 32db401965f165f7c44447d0508097f070c8f576 · fixed in 30bf5728bb217a6d1ba73f44094c9b9c6bc9a567; From 32db401965f165f7c44447d0508097f070c8f576 · fixed in 1d7864acd497cb468a998d44631f84896f885e85; From 32db401965f165f7c44447d0508097f070c8f576 · fixed in 93f616ff870a1fb7e84d472cad0af651b18f9f87; From 6.10.11 · fixed in 6.11
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.44; From 6.13.0 · fixed in 6.16.4