CVE-2025-40245nios2: ensure that memblock.current_limit is set when setting pfn limits
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 8 months later
· 8 months later
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae – < 25f09699edd360b534ccae16bc276c3b52c471f3
- affected 7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae – < 5c3e38a367822f036227dd52bac82dc4a05157e2
- affected 7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae – < b1ec9faef7e36269ca3ec890972a78effbaeb975
- affected 7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae – < 90f5f715550e07cd6a51f80fc3f062d832c8c997
- affected 7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae – < 8912814f14e298b83df072fecc1f7ed1b63b1b2c
- affected 7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae – < a20b83cf45be2057f3d073506779e52c7fa17f94
- affected 5.12
- unaffected < 5.12
- unaffected 5.15.196 – ≤ 5.15.*
- unaffected 6.1.158 – ≤ 6.1.*
- unaffected 6.6.115 – ≤ 6.6.*
- unaffected 6.12.56 – ≤ 6.12.*
- unaffected 6.17.6 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References6
- https://git.kernel.org/stable/c/25f09699edd360b534ccae16bc276c3b52c471f3 (opens in a new tab)
- https://git.kernel.org/stable/c/5c3e38a367822f036227dd52bac82dc4a05157e2 (opens in a new tab)
- https://git.kernel.org/stable/c/b1ec9faef7e36269ca3ec890972a78effbaeb975 (opens in a new tab)
- https://git.kernel.org/stable/c/90f5f715550e07cd6a51f80fc3f062d832c8c997 (opens in a new tab)
- https://git.kernel.org/stable/c/8912814f14e298b83df072fecc1f7ed1b63b1b2c (opens in a new tab)
- https://git.kernel.org/stable/c/a20b83cf45be2057f3d073506779e52c7fa17f94 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-201214 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40245)Record last updated .