{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98739 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98739 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-98739 and fix it if it is affected.\n\nWhat it is: CVE-2026-98739 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-98739 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-98739/ (Markdown: https://insights.sbomify.com/CVE-2026-98739/index.md)","id":"CVE-2026-98739","markdown":"https://insights.sbomify.com/CVE-2026-98739/index.md","name":"CVE-2026-98739","record":{"aliases":["AZL-108653","BELL-CVE-2026-98739","DEBIAN-CVE-2026-98739","GHSA-jg2j-fxrh-w676","UBUNTU-CVE-2026-98739"],"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 Bluetooth","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel Bluetooth RFCOMM driver allows local attackers to trigger a use-after-free, potentially leading to privilege escalation or code execution.","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\nBluetooth: RFCOMM: Fix initial port reference race\n\nFor RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and\n__rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the\ninitial tty_port reference. The release path tests the bit separately\nfrom the install path setting it, so both can drop that reference.\n\nThe synchronous hangup does not prevent this race: port-\u003etty is not\nassigned until tty_port_open(), after installation. The following\ninterleaving is possible:\n\n  1. Install and release each obtain a reference with rfcomm_dev_get().\n  2. Release observes RFCOMM_TTY_OWNED clear.\n  3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.\n  4. Release drops the same initial reference again.\n  5. TTY cleanup drops its reference and frees the device.\n  6. Release performs its final tty_port_put() on the freed port.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190\n  Write of size 4 at addr ffff8881001d3d5c by task poc/92\n\n  Call Trace:\n   tty_port_put+0x22/0x190\n   rfcomm_dev_ioctl+0x1d4/0x1930\n   sock_do_ioctl+0x110/0x260\n   sock_ioctl+0x380/0x590\n   __x64_sys_ioctl+0x134/0x1c0\n\n  Allocated by task 88:\n   rfcomm_dev_ioctl+0x8f6/0x1930\n   sock_do_ioctl+0x110/0x260\n   sock_ioctl+0x380/0x590\n   __x64_sys_ioctl+0x134/0x1c0\n\n  Freed by task 65:\n   kfree+0x131/0x3c0\n   rfcomm_dev_destruct+0x23b/0x2f0\n   release_one_tty+0xc1/0x370\n   process_one_work+0x661/0x1090\n\nUse test_and_set_bit() in both paths so that only the caller that changes\nRFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path\nkeeps its own lookup reference until release or TTY cleanup, preserving\nthe existing callback ordering and error handling.","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":"Bluetooth: RFCOMM: Fix initial port reference race","id":"CVE-2026-98739","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":"EDAC/altera: Drop __init from ECC setup paths for re-probe safety","id":"CVE-2026-98740"},"packages":[],"prev":{"headline":"Bluetooth: Serialize SMP remote OOB data access","id":"CVE-2026-98738"},"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 Bluetooth RFCOMM driver allows local attackers to trigger a use-after-free, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2026-98739/"}