{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98738 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98738 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-98738 and fix it if it is affected.\n\nWhat it is: CVE-2026-98738 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-98738 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-98738/ (Markdown: https://insights.sbomify.com/CVE-2026-98738/index.md)","id":"CVE-2026-98738","markdown":"https://insights.sbomify.com/CVE-2026-98738/index.md","name":"CVE-2026-98738","record":{"aliases":["AZL-108674","BELL-CVE-2026-98738","DEBIAN-CVE-2026-98738","GHSA-pp83-8gx8-qvjg","UBUNTU-CVE-2026-98738"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"none","summary":"A race condition in the Linux kernel Bluetooth SMP implementation allows attackers to trigger a use-after-free, potentially leading to code execution or system crashes.","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: Serialize SMP remote OOB data access\n\nbuild_pairing_cmd() looks up remote OOB data and copies its contents\nwithout holding hdev-\u003elock, which serializes the list's writers. After\nSMP finds an entry, a concurrent management Remove Remote OOB Data\ncommand can unlink and free it before SMP reads its present flag or\ncopies its random and confirmation values. Removal can also invalidate\nan entry while the lookup is still traversing the list.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in build_pairing_cmd+0x948/0x9b0\n  Call Trace:\n   build_pairing_cmd+0x948/0x9b0\n   smp_recv_cb+0x459f/0x8110\n   l2cap_recv_frame+0xf14/0x9190\n   l2cap_recv_acldata+0xa64/0xd40\n   hci_rx_work+0x4ca/0x730\n\n  Allocated by task 87:\n   hci_add_remote_oob_data+0x11d/0x530\n   add_remote_oob_data+0x282/0x400\n   hci_sock_sendmsg+0x1033/0x1ea0\n\n  Freed by task 93:\n   hci_remote_oob_data_clear+0x108/0x1c0\n   remove_remote_oob_data+0x198/0x220\n   hci_sock_sendmsg+0x1033/0x1ea0\n\nTaking hdev-\u003elock in build_pairing_cmd() would recurse for callers that\nalready hold it and invert the device-to-L2CAP lock order on the receive\npath. Add a per-device remote_oob_lock instead, held across the SMP\nlookup and copies and by the add, remove and clear helpers. Cover\ninitialization and in-place updates as well, so SMP cannot read partially\ninitialized or updated OOB values. Release the mutex on allocation\nfailure, preserving the existing error return.\n\nThe new critical sections acquire no device, connection or channel locks.\nWriters retain their existing hdev-\u003elock protection, which continues to\nserialize the other readers without changing their locking or behavior.","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: Serialize SMP remote OOB data access","id":"CVE-2026-98738","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":"Bluetooth: RFCOMM: Fix initial port reference race","id":"CVE-2026-98739"},"packages":[],"prev":{"headline":"Bluetooth: hci_sync: Fix inquiry cache use-after-free","id":"CVE-2026-98737"},"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 SMP implementation allows attackers to trigger a use-after-free, potentially leading to code execution or system crashes.","url":"https://insights.sbomify.com/CVE-2026-98738/"}