Answer in brief
CVE-2025-40245 records a High severity (CVSS 7.8) vulnerability in nios2: ensure that memblock.current_limit is set when setting pfn limits. 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.
CVSS is 7.8. 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 | >=7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae <25f09699edd360b534ccae16bc276c3b52c471f3 || >=7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae <5c3e38a367822f036227dd52bac82dc4a05157e2 || >=7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae <b1ec9faef7e36269ca3ec890972a78effbaeb975 || >=7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae <90f5f715550e07cd6a51f80fc3f062d832c8c997 || >=7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae <8912814f14e298b83df072fecc1f7ed1b63b1b2c || >=7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae <a20b83cf45be2057f3d073506779e52c7fa17f94 | 25f09699edd360b534ccae16bc276c3b52c471f3, 5c3e38a367822f036227dd52bac82dc4a05157e2, b1ec9faef7e36269ca3ec890972a78effbaeb975, 90f5f715550e07cd6a51f80fc3f062d832c8c997, 8912814f14e298b83df072fecc1f7ed1b63b1b2c, a20b83cf45be2057f3d073506779e52c7fa17f94 |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Dec 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 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: nios2: ensure that memblock.current_limit is set when setting pfn limits On nios2, with CONFIG_FLATMEM set, the kernel relies on memblock_get_current_limit() to determine the limits of mem_map, in particular for max_low_pfn. Unfortunately, memblock.current_limit is only default initialized to MEMBLOCK_ALLOC_ANYWHERE at this point of the bootup, potentially leading to situations where max_low_pfn can erroneously exceed the value of max_pfn and, thus, the valid range of available DRAM. This can in turn cause kernel-level paging failures, e.g.: [ 76.900000] Unable to handle kernel paging request at virtual address 20303000 [ 76.900000] ea = c0080890, ra = c000462c, cause = 14 [ 76.900000] Kernel panic - not syncing: Oops [ 76.900000] ---[ end Kernel panic - not syncing: Oops ]--- This patch fixes this by pre-calculating memblock.current_limit based on the upper limits of the available memory ranges via adjust_lowmem_bounds, a simplified version of the equivalent implementation within the arm architecture.
Quoted source text, attributed separately from HOL analysis.