{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98688 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98688 is a vulnerability in Linux, published on 18 Oct 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-98688 and fix it if it is affected.\n\nWhat it is: CVE-2026-98688 is a vulnerability in Linux, published on 18 Oct 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-98688 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-98688/ (Markdown: https://insights.sbomify.com/CVE-2026-98688/index.md)","id":"CVE-2026-98688","markdown":"https://insights.sbomify.com/CVE-2026-98688/index.md","name":"CVE-2026-98688","record":{"aliases":["DEBIAN-CVE-2026-98688","GHSA-g38j-2fmx-j974","UBUNTU-CVE-2026-98688"],"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 race condition in the Linux kernel Thunderbolt driver causes a NULL pointer dereference, leading to a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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 NULL dereference in tb_remove_work()\n\nThere is a slight race between tb_remove_work() and tb_domain_remove()\nwhich leads to dereferencing a NULL tb-\u003eroot_switch pointer inside\ntb_free_unplugged_xdomains():\n\n        Thread A                            Thread B\n\n  tb_remove_work()\n                                    tb_domain_remove()\n                                      mutex_lock(\u0026tb-\u003elock)\n                                      tb_stop()\n                                        /* doesn't cancel a running callback */\n                                        cancel_delayed_work(\u0026tcm-\u003eremove_work)\n                                        ...\n                                        tb_switch_remove(tb-\u003eroot_switch)\n                                        tb-\u003eroot_switch = NULL\n                                      mutex_unlock(\u0026tb-\u003elock)\n    mutex_lock(\u0026tb-\u003elock)\n    ...\n    /* without checking -\u003eroot_switch */\n    tb_free_unplugged_xdomains(tb-\u003eroot_switch)\n    mutex_unlock(\u0026tb-\u003elock)\n\nCommit a8937f35cf39 (\"thunderbolt: Remove XDomain from the bus without\nholding tb-\u003elock\") doesn't seem right to move tb_free_unplugged_xdomains()\nout of the \u0026tb-\u003elock section and the check for tb-\u003eroot_switch, in\nparticular.  It states:\n\n  For this reason separate removing the XDomain from the topology data\n  structures (where we need the lock) from unregistering the device from\n  the bus (where remove callbacks of the drivers are being called).\n\ntb_free_unplugged_xdomains() belongs to the former group of functions\nrequiring the lock.  And it also calls tb_xdomain_remove() which should\nonly be called with \u0026tb-\u003elock held.\n\nFound by Linux Verification Center (linuxtesting.org) with Svace static\nanalysis tool.","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 NULL dereference in tb_remove_work()","id":"CVE-2026-98688","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"thunderbolt: Don't access a DP tunnel after its DPRX read was canceled","id":"CVE-2026-98689"},"packages":[],"prev":{"headline":"thunderbolt: Reject oversized XDomain properties responses","id":"CVE-2026-98687"},"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 race condition in the Linux kernel Thunderbolt driver causes a NULL pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2026-98688/"}