{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93783 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93783 is a memory corruption vulnerability in Linux, published on 24 Sep 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-93783 and fix it if it is affected.\n\nWhat it is: CVE-2026-93783 is a memory corruption vulnerability in Linux, published on 24 Sep 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-93783 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-93783/ (Markdown: https://insights.sbomify.com/CVE-2026-93783/index.md)","id":"CVE-2026-93783","markdown":"https://insights.sbomify.com/CVE-2026-93783/index.md","name":"CVE-2026-93783","record":{"aliases":["AZL-103928","BELL-CVE-2026-93783","DEBIAN-CVE-2026-93783","GHSA-xv96-c36m-qhm7","UBUNTU-CVE-2026-93783"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"none","summary":"A missing length check in the Linux kernel Bluetooth RFCOMM handler allows attackers to trigger out-of-bounds reads and potential crashes via malformed frames.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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: validate skb length in rfcomm_recv_frame\n\nrfcomm_recv_frame() casts skb-\u003edata to struct rfcomm_hdr and dereferences\nhdr-\u003eaddr and hdr-\u003ectrl without validating skb-\u003elen first. A truncated\nframe with skb-\u003elen less than the minimum header size causes an\nout-of-bounds read of uninitialized memory. Additionally, a zero-length\nframe causes skb-\u003elen-- to underflow to UINT_MAX, making\nskb_tail_pointer() read far past the buffer.\n\nCommit 23882b828c3c (\"Bluetooth: RFCOMM: validate skb length in MCC\nhandlers\") fixed the same class of missing-length-check bugs in the MCC\nsub-handlers, but the top-level rfcomm_recv_frame() was left unfixed.\nKMSAN reports:\n\n  BUG: KMSAN: uninit-value in rfcomm_run\n  ...\n  Uninit was created at:\n    __alloc_skb+0x474/0xb60\n    vhci_write+0xe9/0x870\n\nFix this by rejecting frames smaller than sizeof(struct rfcomm_hdr) + 1\n(the minimum frame must have a 3-byte header and a 1-byte FCS).","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: validate skb length in rfcomm_recv_frame","id":"CVE-2026-93783","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie()","id":"CVE-2026-93784"},"packages":[],"prev":{"headline":"vhost-scsi: flush backend after device ioctls","id":"CVE-2026-93782"},"products":["Linux"],"published":"2026-09-24","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-03","vendors":["Linux"]},"summary":"A missing length check in the Linux kernel Bluetooth RFCOMM handler allows attackers to trigger out-of-bounds reads and potential crashes via malformed frames.","url":"https://insights.sbomify.com/CVE-2026-93783/"}