cve.bz

CVE-2025-40245 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.15.196
  • Linux Linux: fixed in 6.1.158
  • Linux Linux: fixed in 6.6.115
  • Linux Linux: fixed in 6.12.56
  • Linux Linux: fixed in 6.17.6
  • Linux Linux: fixed in 6.18
  • Debian, Ubuntu, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-40245 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-40245?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-40245?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-40245 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.12 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.196
Linux6.16.1.158
Linux6.66.6.115
Linux6.126.12.56
Linux6.176.17.6
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.158-1DEBIAN-CVE-2025-40245
Debian13linux6.12.57-1DEBIAN-CVE-2025-40245
Debian14linux6.17.6-1DEBIAN-CVE-2025-40245
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-40245
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-40245
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-40245
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-170.180UBUNTU-CVE-2025-40245 USN-8033-1
Ubuntu22.04:LTSlinux-aws5.15.0-1100.107UBUNTU-CVE-2025-40245 USN-8033-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1050.53~22.04.1UBUNTU-CVE-2025-40245 USN-8095-4
Ubuntu22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-40245 USN-8163-2
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-40245 USN-8126-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-40245
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-40245
Ubuntu22.04:LTSlinux-gcp5.15.0-1100.109UBUNTU-CVE-2025-40245 USN-8033-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-40245 USN-8095-1
72 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-lts6.1.158-r0BELL-CVE-2025-40245
Alpaquita25linux-lts6.12.57-r0BELL-CVE-2025-40245
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-40245

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This vulnerability does not impact Red Hat Enterprise Linux because it is strictly confined to the Nios II (nios2) processor architecture. Red Hat does not build or distribute kernels for this hardware platform. Consequently, supported enterprise installations do not include the vulnerable architecture-specific setup code and are not at risk.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-40245.

References

Check your stackJSON