{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50833 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50833 is a vulnerability in Linux, published on 30 Dec 2025. 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-2022-50833 and fix it if it is affected.\n\nWhat it is: CVE-2022-50833 is a vulnerability in Linux, published on 30 Dec 2025. 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-2022-50833 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-2022-50833/ (Markdown: https://insights.sbomify.com/CVE-2022-50833/index.md)","id":"CVE-2022-50833","markdown":"https://insights.sbomify.com/CVE-2022-50833/index.md","name":"CVE-2022-50833","record":{"aliases":["DEBIAN-CVE-2022-50833","GHSA-rxjc-h4m5-gvq8","UBUNTU-CVE-2022-50833"],"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 race condition in the Linux kernel Bluetooth subsystem allows attackers to cause a denial of service via improper workqueue scheduling.","user_interaction":"not_required","vuln_class":"race_condition"},"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: use hdev-\u003eworkqueue when queuing hdev-\u003e{cmd,ncmd}_timer works\n\nsyzbot is reporting attempt to schedule hdev-\u003ecmd_work work from system_wq\nWQ into hdev-\u003eworkqueue WQ which is under draining operation [1], for\ncommit c8efcc2589464ac7 (\"workqueue: allow chained queueing during\ndestruction\") does not allow such operation.\n\nThe check introduced by commit 877afadad2dce8aa (\"Bluetooth: When HCI work\nqueue is drained, only queue chained work\") was incomplete.\n\nUse hdev-\u003eworkqueue WQ when queuing hdev-\u003e{cmd,ncmd}_timer works because\nhci_{cmd,ncmd}_timeout() calls queue_work(hdev-\u003eworkqueue). Also, protect\nthe queuing operation with RCU read lock in order to avoid calling\nqueue_delayed_work() after cancel_delayed_work() completed.","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: use hdev-\u003eworkqueue when queuing hdev-\u003e{cmd,ncmd}_timer works","id":"CVE-2022-50833","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"nfc: Fix potential resource leaks","id":"CVE-2022-50834"},"packages":[],"prev":{"headline":"wifi: wilc1000: fix potential memory leak in wilc_mac_xmit()","id":"CVE-2022-50832"},"products":["Linux"],"published":"2025-12-30","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-05-23","vendors":["Linux"]},"summary":"A race condition in the Linux kernel Bluetooth subsystem allows attackers to cause a denial of service via improper workqueue scheduling.","url":"https://insights.sbomify.com/CVE-2022-50833/"}