{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98687 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98687 is a memory corruption 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-98687 and fix it if it is affected.\n\nWhat it is: CVE-2026-98687 is a memory corruption 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-98687 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-98687/ (Markdown: https://insights.sbomify.com/CVE-2026-98687/index.md)","id":"CVE-2026-98687","markdown":"https://insights.sbomify.com/CVE-2026-98687/index.md","name":"CVE-2026-98687","record":{"aliases":["AZL-108953","BELL-CVE-2026-98687","DEBIAN-CVE-2026-98687","GHSA-rq3j-rw4p-w59w","UBUNTU-CVE-2026-98687"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Thunderbolt","requires_auth":"none","summary":"A malicious Thunderbolt peer can trigger a heap out-of-bounds read in the Linux kernel, potentially leaking memory or causing a crash.","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\nthunderbolt: Reject oversized XDomain properties responses\n\ntb_xdp_properties_request() allocates room for 45 data dwords in its\n252-byte response buffer.  The XDomain length field is six bits wide,\nhowever, and a malicious peer can set it to 63.  After the fixed response\nfields are subtracted, the driver treats this as 48 data dwords.\n\nCommit 322e93448d90 (\"thunderbolt: Clamp XDomain response data copy to\nallocation size\") only bounds the copy against data_len.  If data_len is\nat least 48, memcpy() reads 192 bytes from the 180-byte res-\u003edata array,\ncausing a 12-byte heap out-of-bounds read.  Commit 4db2bd2ed478\n(\"thunderbolt: Limit XDomain response copy to actual frame size\") limits\nthe earlier copy but does not constrain this header-derived length.\n\nReject response data lengths that exceed the allocated source buffer\nbefore copying them into the assembled property block.","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: Reject oversized XDomain properties responses","id":"CVE-2026-98687","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"thunderbolt: Fix NULL dereference in tb_remove_work()","id":"CVE-2026-98688"},"packages":[],"prev":{"headline":"smb: client: discard post-EOF pagecache when extending a file via zero range","id":"CVE-2026-98686"},"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-21","vendors":["Linux"]},"summary":"A malicious Thunderbolt peer can trigger a heap out-of-bounds read in the Linux kernel, potentially leaking memory or causing a crash.","url":"https://insights.sbomify.com/CVE-2026-98687/"}