{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98600 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98600 is a denial of service 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-98600 and fix it if it is affected.\n\nWhat it is: CVE-2026-98600 is a denial of service 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-98600 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-98600/ (Markdown: https://insights.sbomify.com/CVE-2026-98600/index.md)","id":"CVE-2026-98600","markdown":"https://insights.sbomify.com/CVE-2026-98600/index.md","name":"CVE-2026-98600","record":{"aliases":["BELL-CVE-2026-98600","DEBIAN-CVE-2026-98600","GHSA-hpgr-cqmv-php2","UBUNTU-CVE-2026-98600"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"none","summary":"A flaw in the Linux kernel Bluetooth RFCOMM implementation allows attackers to cause a denial of service by sending malformed short frames.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: Reject short EA=0 frames in rfcomm_recv_frame()\n\nWhile rfcomm_recv_frame() verifies that skb-\u003elen is at least\nsizeof(*hdr) + 1 (4 bytes: 3-byte header + 1-byte FCS), an RFCOMM frame\nwith an extended 2-byte length field (!__test_ea(hdr-\u003elen)) has a 4-byte\nheader plus a 1-byte FCS (5 bytes minimum, sizeof(*hdr) + 2).\n\nWhen a 4-byte RFCOMM frame with EA == 0 arrives:\n1. The initial skb-\u003elen \u003c sizeof(*hdr) + 1 check passes (4 \u003c 4 is false).\n2. Trimming the FCS byte decrements skb-\u003elen to 3.\n3. If __check_fcs() succeeds, skb_pull(skb, 4) fails (4 \u003e 3) and returns\n   NULL without advancing skb-\u003edata.\n4. Because the return value of skb_pull() is ignored, the un-pulled\n   3-byte struct rfcomm_hdr remains at skb-\u003edata and is either queued as\n   application payload via rfcomm_recv_data() or parsed as a multiplexer\n   control command via rfcomm_recv_mcc() on DLCI 0.\n\nFix this by extending the length check in rfcomm_recv_frame() to also\nrequire skb-\u003elen \u003e= sizeof(*hdr) + 2 when !__test_ea(hdr-\u003elen).","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: Reject short EA=0 frames in rfcomm_recv_frame()","id":"CVE-2026-98600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Bluetooth: btintel_pcie: validate device-supplied DMA indices","id":"CVE-2026-98601"},"packages":[],"prev":{"headline":"bpf: Reject non-negative offsets in stack_slot_obj_get_spi()","id":"CVE-2026-98599"},"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-19","vendors":["Linux"]},"summary":"A flaw in the Linux kernel Bluetooth RFCOMM implementation allows attackers to cause a denial of service by sending malformed short frames.","url":"https://insights.sbomify.com/CVE-2026-98600/"}