{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98753 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98753 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-98753 and fix it if it is affected.\n\nWhat it is: CVE-2026-98753 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-98753 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-98753/ (Markdown: https://insights.sbomify.com/CVE-2026-98753/index.md)","id":"CVE-2026-98753","markdown":"https://insights.sbomify.com/CVE-2026-98753/index.md","name":"CVE-2026-98753","record":{"aliases":["AZL-109020","BELL-CVE-2026-98753","DEBIAN-CVE-2026-98753","GHSA-fxvh-5c26-7p3q","UBUNTU-CVE-2026-98753"],"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":"low_privilege","summary":"A race condition in the Linux kernel TTY subsystem can cause a kernel panic via NULL pointer dereference when accessing powered-down ports.","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\ntty: tty_port: restore TTY_IO_ERROR on activation failure\n\nMake sure to restore the TTY_IO_ERROR flag if activation fails to\nprevent I/O attempts on a port that is gone or powered down.\n\nThis specifically avoids issues like kernel panic due to unclocked\naccesses or NULL-pointer dereferences when accessing powered down or\nderegistered ports when a TTY ioctl races with hangup and open.\n\nNote that the flag is set again in tty_port_close() but not restoring it\non activation failure leaves a window where drivers fail to handle the\nioctl-hangup race.","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: tty_port: restore TTY_IO_ERROR on activation failure","id":"CVE-2026-98753","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup","id":"CVE-2026-98754"},"packages":[],"prev":{"headline":"tty: port: fix tty_port_tty_vhangup() race","id":"CVE-2026-98752"},"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 race condition in the Linux kernel TTY subsystem can cause a kernel panic via NULL pointer dereference when accessing powered-down ports.","url":"https://insights.sbomify.com/CVE-2026-98753/"}