{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40245 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40245 is a high-severity denial of service vulnerability in Linux, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40245 and fix it if it is affected.\n\nWhat it is: CVE-2025-40245 is a high-severity denial of service vulnerability in Linux, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40245 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-40245/ (Markdown: https://insights.sbomify.com/CVE-2025-40245/index.md)","id":"CVE-2025-40245","markdown":"https://insights.sbomify.com/CVE-2025-40245/index.md","name":"CVE-2025-40245","record":{"aliases":["BELL-CVE-2025-40245","DEBIAN-CVE-2025-40245","GHSA-56rc-pfj3-9mx3","ROOT-OS-DEBIAN-11-CVE-2025-40245","ROOT-OS-UBUNTU-2404-CVE-2025-40245","UBUNTU-CVE-2025-40245"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A kernel panic occurs on nios2 systems with FLATMEM due to incorrect memory limit calculations, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nios2: ensure that memblock.current_limit is set when setting pfn limits","id":"CVE-2025-40245","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"xfs: fix out of bounds memory read error in symlink repair","id":"CVE-2025-40246"},"packages":[],"prev":{"headline":"hfsplus: fix KMSAN uninit-value issue in __hfsplus_ext_cache_extent()","id":"CVE-2025-40244"},"products":["Linux"],"published":"2025-12-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A kernel panic occurs on nios2 systems with FLATMEM due to incorrect memory limit calculations, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2025-40245/"}