{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98754 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98754 is an use after free 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-98754 and fix it if it is affected.\n\nWhat it is: CVE-2026-98754 is an use after free 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-98754 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-98754/ (Markdown: https://insights.sbomify.com/CVE-2026-98754/index.md)","id":"CVE-2026-98754","markdown":"https://insights.sbomify.com/CVE-2026-98754/index.md","name":"CVE-2026-98754","record":{"aliases":["AZL-109044","BELL-CVE-2026-98754","DEBIAN-CVE-2026-98754","GHSA-phxc-9rqx-x894","UBUNTU-CVE-2026-98754"],"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","requires_auth":"none","summary":"A race condition in the Linux kernel's vcc driver allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.","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\ntty: vcc: hold port lock when clearing tty pointer in vcc_cleanup\n\nvcc_cleanup() sets port-\u003etty to NULL without holding port-\u003elock, racing\nwith vcc_event() LDC callbacks that read port-\u003etty under port-\u003elock and\nthen use tty-\u003eport. This can cause a use-after-free when the callback\ndereferences tty-\u003eport after cleanup has already destroyed and freed it.","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":"tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup","id":"CVE-2026-98754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"tty: vcc: zero-initialize control packet in vcc_send_ctl()","id":"CVE-2026-98755"},"packages":[],"prev":{"headline":"tty: tty_port: restore TTY_IO_ERROR on activation failure","id":"CVE-2026-98753"},"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-26","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's vcc driver allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-98754/"}