{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68245 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68245 is an use after free vulnerability in Linux, published on 16 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68245 and fix it if it is affected.\n\nWhat it is: CVE-2025-68245 is an use after free vulnerability in Linux, published on 16 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68245 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-68245/ (Markdown: https://insights.sbomify.com/CVE-2025-68245/index.md)","id":"CVE-2025-68245","markdown":"https://insights.sbomify.com/CVE-2025-68245/index.md","name":"CVE-2025-68245","record":{"aliases":["BELL-CVE-2025-68245","DEBIAN-CVE-2025-68245","GHSA-jr3x-g84v-9793","ROOT-OS-DEBIAN-12-CVE-2025-68245","ROOT-OS-DEBIAN-13-CVE-2025-68245","ROOT-OS-UBUNTU-2204-CVE-2025-68245","ROOT-OS-UBUNTU-2404-CVE-2025-68245","UBUNTU-CVE-2025-68245"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A refcount handling error in the Linux kernel netpoll subsystem causes memory leaks and improper cleanup, potentially leading to denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nnet: netpoll: fix incorrect refcount handling causing incorrect cleanup\n\ncommit efa95b01da18 (\"netpoll: fix use after free\") incorrectly\nignored the refcount and prematurely set dev-\u003enpinfo to NULL during\nnetpoll cleanup, leading to improper behavior and memory leaks.\n\nScenario causing lack of proper cleanup:\n\n1) A netpoll is associated with a NIC (e.g., eth0) and netdev-\u003enpinfo is\n   allocated, and refcnt = 1\n   - Keep in mind that npinfo is shared among all netpoll instances. In\n     this case, there is just one.\n\n2) Another netpoll is also associated with the same NIC and\n   npinfo-\u003erefcnt += 1.\n   - Now dev-\u003enpinfo-\u003erefcnt = 2;\n   - There is just one npinfo associated to the netdev.\n\n3) When the first netpolls goes to clean up:\n   - The first cleanup succeeds and clears np-\u003edev-\u003enpinfo, ignoring\n     refcnt.\n     - It basically calls `RCU_INIT_POINTER(np-\u003edev-\u003enpinfo, NULL);`\n   - Set dev-\u003enpinfo = NULL, without proper cleanup\n   - No -\u003endo_netpoll_cleanup() is either called\n\n4) Now the second target tries to clean up\n   - The second cleanup fails because np-\u003edev-\u003enpinfo is already NULL.\n     * In this case, ops-\u003endo_netpoll_cleanup() was never called, and\n       the skb pool is not cleaned as well (for the second netpoll\n       instance)\n  - This leaks npinfo and skbpool skbs, which is clearly reported by\n    kmemleak.\n\nRevert commit efa95b01da18 (\"netpoll: fix use after free\") and adds\nclarifying comments emphasizing that npinfo cleanup should only happen\nonce the refcount reaches zero, ensuring stable and correct netpoll\nbehavior.","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":"net: netpoll: fix incorrect refcount handling causing incorrect cleanup","id":"CVE-2025-68245","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"ksmbd: close accepted socket when per-IP limit rejects connection","id":"CVE-2025-68246"},"packages":[],"prev":{"headline":"drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD","id":"CVE-2025-68244"},"products":["Linux"],"published":"2025-12-16","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 refcount handling error in the Linux kernel netpoll subsystem causes memory leaks and improper cleanup, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-68245/"}