{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89548 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89548 is a high-severity use after free vulnerability in Linux, published on 11 Sep 2026. 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-2026-89548 and fix it if it is affected.\n\nWhat it is: CVE-2026-89548 is a high-severity use after free vulnerability in Linux, published on 11 Sep 2026. 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-2026-89548 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-2026-89548/ (Markdown: https://insights.sbomify.com/CVE-2026-89548/index.md)","id":"CVE-2026-89548","markdown":"https://insights.sbomify.com/CVE-2026-89548/index.md","name":"CVE-2026-89548","record":{"aliases":["AZL-100743","BELL-CVE-2026-89548","DEBIAN-CVE-2026-89548","GHSA-3g7j-4hj7-8rgc","UBUNTU-CVE-2026-89548"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel SUNRPC","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel SUNRPC subsystem allows attackers to execute arbitrary code or escalate privileges during network namespace teardown.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nSUNRPC: always drain cache_cleaner before destroying a cache_detail\n\nsunrpc_destroy_cache_detail() only cancels the global cache_cleaner\ndelayed_work when cache_list is empty.  During per-netns teardown\ncache_list is never empty because init_net's caches remain registered,\nso the cancel never fires.  After unlink, the caller proceeds to\ncache_destroy_net() which kfrees the cache_detail while cache_clean()\nmay still hold a dangling pointer to it.  The result is a\nuse-after-free: cache_dequeue() takes cd-\u003equeue_lock on freed memory,\nand cache_put() dereferences cd-\u003ecache_put as a function pointer from\nfreed slab.\n\nDrop the list_empty guard so that cancel_delayed_work_sync() always\nruns, ensuring any in-flight cache_clean() completes before the\ncache_detail is freed.  Re-arm the cleaner afterwards if other caches\nare still registered.","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":"SUNRPC: always drain cache_cleaner before destroying a cache_detail","id":"CVE-2026-89548","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"sunrpc: route to a populated pool in svc_pool_for_cpu()","id":"CVE-2026-89549"},"packages":[],"prev":{"headline":"SUNRPC: Check svc pool percpu counter allocation","id":"CVE-2026-89547"},"products":["Linux"],"published":"2026-09-11","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel SUNRPC subsystem allows attackers to execute arbitrary code or escalate privileges during network namespace teardown.","url":"https://insights.sbomify.com/CVE-2026-89548/"}