Answer in brief
CVE-2025-38733 records a Unknown severity vulnerability in s390/mm: Do not map lowcore with identity mapping. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=32db401965f165f7c44447d0508097f070c8f576 <30bf5728bb217a6d1ba73f44094c9b9c6bc9a567 || >=32db401965f165f7c44447d0508097f070c8f576 <1d7864acd497cb468a998d44631f84896f885e85 || >=32db401965f165f7c44447d0508097f070c8f576 <93f616ff870a1fb7e84d472cad0af651b18f9f87 || 0b99d0e17d6a73a0526f92bc6b54b2b95e67a31d || >=6.10.11 <6.11 | 30bf5728bb217a6d1ba73f44094c9b9c6bc9a567, 1d7864acd497cb468a998d44631f84896f885e85, 93f616ff870a1fb7e84d472cad0af651b18f9f87, 6.11 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38733 records a Unknown severity vulnerability in s390/mm: Do not map lowcore with identity mapping. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=32db401965f165f7c44447d0508097f070c8f576 <30bf5728bb217a6d1ba73f44094c9b9c6bc9a567 || >=32db401965f165f7c44447d0508097f070c8f576 <1d7864acd497cb468a998d44631f84896f885e85 || >=32db401965f165f7c44447d0508097f070c8f576 <93f616ff870a1fb7e84d472cad0af651b18f9f87 || 0b99d0e17d6a73a0526f92bc6b54b2b95e67a31d || >=6.10.11 <6.11 | 30bf5728bb217a6d1ba73f44094c9b9c6bc9a567, 1d7864acd497cb468a998d44631f84896f885e85, 93f616ff870a1fb7e84d472cad0af651b18f9f87, 6.11 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.