Answer in brief
CVE-2024-35987 records a Unknown severity vulnerability in riscv: Fix loading 64-bit NOMMU kernels past the start of RAM. 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 | >=3335068f87217ea59d08f462187dc856652eea15 <b008e327fa570aca210f98c817757649bae56694 || >=3335068f87217ea59d08f462187dc856652eea15 <ea6628e4e2353978af7e3b4ad4fdaab6149acf3d || >=3335068f87217ea59d08f462187dc856652eea15 <aea702dde7e9876fb00571a2602f25130847bf0f | b008e327fa570aca210f98c817757649bae56694, ea6628e4e2353978af7e3b4ad4fdaab6149acf3d, aea702dde7e9876fb00571a2602f25130847bf0f |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 20, 2024
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: riscv: Fix loading 64-bit NOMMU kernels past the start of RAM commit 3335068f8721 ("riscv: Use PUD/P4D/PGD pages for the linear mapping") added logic to allow using RAM below the kernel load address. However, this does not work for NOMMU, where PAGE_OFFSET is fixed to the kernel load address. Since that range of memory corresponds to PFNs below ARCH_PFN_OFFSET, mm initialization runs off the beginning of mem_map and corrupts adjacent kernel memory. Fix this by restoring the previous behavior for NOMMU kernels.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-35987 records a Unknown severity vulnerability in riscv: Fix loading 64-bit NOMMU kernels past the start of RAM. 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 | >=3335068f87217ea59d08f462187dc856652eea15 <b008e327fa570aca210f98c817757649bae56694 || >=3335068f87217ea59d08f462187dc856652eea15 <ea6628e4e2353978af7e3b4ad4fdaab6149acf3d || >=3335068f87217ea59d08f462187dc856652eea15 <aea702dde7e9876fb00571a2602f25130847bf0f | b008e327fa570aca210f98c817757649bae56694, ea6628e4e2353978af7e3b4ad4fdaab6149acf3d, aea702dde7e9876fb00571a2602f25130847bf0f |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 20, 2024
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: riscv: Fix loading 64-bit NOMMU kernels past the start of RAM commit 3335068f8721 ("riscv: Use PUD/P4D/PGD pages for the linear mapping") added logic to allow using RAM below the kernel load address. However, this does not work for NOMMU, where PAGE_OFFSET is fixed to the kernel load address. Since that range of memory corresponds to PFNs below ARCH_PFN_OFFSET, mm initialization runs off the beginning of mem_map and corrupts adjacent kernel memory. Fix this by restoring the previous behavior for NOMMU kernels.
Quoted source text, attributed separately from HOL analysis.