{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98690 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98690 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-98690 and fix it if it is affected.\n\nWhat it is: CVE-2026-98690 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-98690 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-98690/ (Markdown: https://insights.sbomify.com/CVE-2026-98690/index.md)","id":"CVE-2026-98690","markdown":"https://insights.sbomify.com/CVE-2026-98690/index.md","name":"CVE-2026-98690","record":{"aliases":["BELL-CVE-2026-98690","DEBIAN-CVE-2026-98690","GHSA-wqqh-3g59-38q4","UBUNTU-CVE-2026-98690"],"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":"none","summary":"A local attacker can cause a kernel hang and memory leak by unplugging a Thunderbolt device during a specific timing window, requiring physical access.","user_interaction":"required","vuln_class":"denial_of_service"},"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\nthunderbolt: Fix domain reference leak when DPRX read is canceled\n\ntb_tunnel_one_dp() takes a domain reference which is only dropped once\ntb_dp_tunnel_active() has run on the work queue. If that work is\ncancelled that reference is leaked. Since\ncommit f5cc545f5969 (\"thunderbolt: Wait for tb_domain_release() to\ncomplete when driver is removed\") instead of just leaking memory this\nnow also blocks in the completion wait forever when unbinding the\ndriver.\n\nThis can be triggered whenever a DP tunnel is torn down before the DPRX\nread has completed, e.g. by unplugging within the timeout, and then\nunbinding the driver.\n\nThat reference only exists to keep the domain around while the DPRX work\nis scheduled so let the work itself own it: take it in tb_dp_dprx_start()\nand drop it in both places that end the work. Get/put are then paired\ninside the same file and it doesn't matter anymore if the callback ever\nruns.","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":"thunderbolt: Fix domain reference leak when DPRX read is canceled","id":"CVE-2026-98690","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"thunderbolt: Tear down inactive DP tunnels when the domain is stopped","id":"CVE-2026-98691"},"packages":[],"prev":{"headline":"thunderbolt: Don't access a DP tunnel after its DPRX read was canceled","id":"CVE-2026-98689"},"products":["Linux"],"published":"2026-10-18","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-10-19","vendors":["Linux"]},"summary":"A local attacker can cause a kernel hang and memory leak by unplugging a Thunderbolt device during a specific timing window, requiring physical access.","url":"https://insights.sbomify.com/CVE-2026-98690/"}