{"id":"CVE-2025-40245","summary":"nios2: ensure that memblock.current_limit is set when setting pfn limits","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nnios2: ensure that memblock.current_limit is set when setting pfn limits\n\nOn nios2, with CONFIG_FLATMEM set, the kernel relies on\nmemblock_get_current_limit() to determine the limits of mem_map, in\nparticular for max_low_pfn.\nUnfortunately, memblock.current_limit is only default initialized to\nMEMBLOCK_ALLOC_ANYWHERE at this point of the bootup, potentially leading\nto situations where max_low_pfn can erroneously exceed the value of\nmax_pfn and, thus, the valid range of available DRAM.\n\nThis can in turn cause kernel-level paging failures, e.g.:\n\n[   76.900000] Unable to handle kernel paging request at virtual address 20303000\n[   76.900000] ea = c0080890, ra = c000462c, cause = 14\n[   76.900000] Kernel panic - not syncing: Oops\n[   76.900000] ---[ end Kernel panic - not syncing: Oops ]---\n\nThis patch fixes this by pre-calculating memblock.current_limit\nbased on the upper limits of the available memory ranges via\nadjust_lowmem_bounds, a simplified version of the equivalent\nimplementation within the arm architecture.","modified":"2026-03-20T12:43:14.378340Z","published":"2025-12-04T15:31:34.142Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40245.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/25f09699edd360b534ccae16bc276c3b52c471f3"},{"type":"WEB","url":"https://git.kernel.org/stable/c/5c3e38a367822f036227dd52bac82dc4a05157e2"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8912814f14e298b83df072fecc1f7ed1b63b1b2c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/90f5f715550e07cd6a51f80fc3f062d832c8c997"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a20b83cf45be2057f3d073506779e52c7fa17f94"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b1ec9faef7e36269ca3ec890972a78effbaeb975"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40245.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40245"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"7f7bc20bc41a4fbcd2db75b375ac95e5faf958ae"},{"fixed":"25f09699edd360b534ccae16bc276c3b52c471f3"},{"fixed":"5c3e38a367822f036227dd52bac82dc4a05157e2"},{"fixed":"b1ec9faef7e36269ca3ec890972a78effbaeb975"},{"fixed":"90f5f715550e07cd6a51f80fc3f062d832c8c997"},{"fixed":"8912814f14e298b83df072fecc1f7ed1b63b1b2c"},{"fixed":"a20b83cf45be2057f3d073506779e52c7fa17f94"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-40245.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.12.0"},{"fixed":"5.15.196"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.158"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.115"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.56"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.17.6"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-40245.json"}}],"schema_version":"1.7.5"}