{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40191 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40191 is a 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-40191 and fix it if it is affected.\n\nWhat it is: CVE-2025-40191 is a 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-40191 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-40191/ (Markdown: https://insights.sbomify.com/CVE-2025-40191/index.md)","id":"CVE-2025-40191","markdown":"https://insights.sbomify.com/CVE-2025-40191/index.md","name":"CVE-2025-40191","record":{"aliases":["BELL-CVE-2025-40191","DEBIAN-CVE-2025-40191","GHSA-6p7f-xr2h-v9qh","UBUNTU-CVE-2025-40191"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A reference counting bug in the Linux kernel's AMD KFD driver can lead to resource leaks and potential denial of service when unmapping user pointers.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: Fix kfd process ref leaking when userptr unmapping\n\nkfd_lookup_process_by_pid hold the kfd process reference to ensure it\ndoesn't get destroyed while sending the segfault event to user space.\n\nCalling kfd_lookup_process_by_pid as function parameter leaks the kfd\nprocess refcount and miss the NULL pointer check if app process is\nalready destroyed.","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":"drm/amdkfd: Fix kfd process ref leaking when userptr unmapping","id":"CVE-2025-40191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Revert \"ipmi: fix msg stack when IPMI is disconnected\"","id":"CVE-2025-40192"},"packages":[],"prev":{"headline":"ext4: guard against EA inode refcount underflow in xattr update","id":"CVE-2025-40190"},"products":["Linux"],"published":"2025-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A reference counting bug in the Linux kernel's AMD KFD driver can lead to resource leaks and potential denial of service when unmapping user pointers.","url":"https://insights.sbomify.com/CVE-2025-40191/"}