{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40124 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40124 is a high-severity memory corruption vulnerability in Linux, published on 12 Nov 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-40124 and fix it if it is affected.\n\nWhat it is: CVE-2025-40124 is a high-severity memory corruption vulnerability in Linux, published on 12 Nov 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-40124 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-40124/ (Markdown: https://insights.sbomify.com/CVE-2025-40124/index.md)","id":"CVE-2025-40124","markdown":"https://insights.sbomify.com/CVE-2025-40124/index.md","name":"CVE-2025-40124","record":{"aliases":["BELL-CVE-2025-40124","DEBIAN-CVE-2025-40124","GHSA-v3c5-2xf8-7jwx","ROOT-OS-DEBIAN-11-CVE-2025-40124","ROOT-OS-DEBIAN-13-CVE-2025-40124","ROOT-OS-UBUNTU-2404-CVE-2025-40124","UBUNTU-CVE-2025-40124"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel SPARC","requires_auth":"low_privilege","summary":"A flaw in SPARC copy_from_user exception handling causes incorrect byte counts, leading to kernel BUG_ON crashes and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nsparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III\n\nAnthony Yznaga tracked down that a BUG_ON in ext4 code with large folios\nenabled resulted from copy_from_user() returning impossibly large values\ngreater than the size to be copied. This lead to __copy_from_iter()\nreturning impossible values instead of the actual number of bytes it was\nable to copy.\n\nThe BUG_ON has been reported in\nhttps://lore.kernel.org/r/b14f55642207e63e907965e209f6323a0df6dcee.camel@physik.fu-berlin.de\n\nThe referenced commit introduced exception handlers on user-space memory\nreferences in copy_from_user and copy_to_user. These handlers return from\nthe respective function and calculate the remaining bytes left to copy\nusing the current register contents. The exception handlers expect that\n%o2 has already been masked during the bulk copy loop, but the masking was\nperformed after that loop. This will fix the return value of copy_from_user\nand copy_to_user in the faulting case. The behaviour of memcpy stays\nunchanged.","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":"sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III","id":"CVE-2025-40124","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"blk-mq: check kobject state_in_sysfs before deleting in blk_mq_unregister_hctx","id":"CVE-2025-40125"},"packages":[],"prev":{"headline":"bpf: Enforce expected_attach_type for tailcall compatibility","id":"CVE-2025-40123"},"products":["Linux"],"published":"2025-11-12","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 flaw in SPARC copy_from_user exception handling causes incorrect byte counts, leading to kernel BUG_ON crashes and denial of service.","url":"https://insights.sbomify.com/CVE-2025-40124/"}