{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68191 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68191 is a vulnerability in Linux, published on 10 Aug 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-68191 and fix it if it is affected.\n\nWhat it is: CVE-2026-68191 is a vulnerability in Linux, published on 10 Aug 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-68191 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-68191/ (Markdown: https://insights.sbomify.com/CVE-2026-68191/index.md)","id":"CVE-2026-68191","markdown":"https://insights.sbomify.com/CVE-2026-68191/index.md","name":"CVE-2026-68191","record":{"aliases":["DEBIAN-CVE-2026-68191","GHSA-fcf7-j5wv-2rxv","UBUNTU-CVE-2026-68191"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A NULL pointer dereference in the ath12k Wi-Fi driver during device unbinding can cause a kernel crash, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nwifi: ath12k: fix NULL pointer dereference in rhash table destroy\n\nWhen unbinding the ath12k driver, kernel NULL pointer dereferences\noccur in irq_work_sync() called from rhashtable_destroy().\n\nTwo hash tables are affected:\n1. ath12k_link_sta hash table in ath12k_base\n2. ath12k_dp_link_peer hash table in ath12k_dp\n\nThe issue happens because the destroy functions are called unconditionally\nin cleanup paths, but the hash tables are only initialized late in their\nrespective init functions. If the device was never fully started or if the\ninit functions failed before initializing the hash tables, the pointers\nwill be NULL. The issues are always reproducible from a VM because the MSI\naddressing initialization is failing.\n\nCall trace for ath12k_link_sta_rhash_tbl_destroy:\n RIP: irq_work_sync+0x1e/0x70\n rhashtable_destroy+0x12/0x60\n ath12k_link_sta_rhash_tbl_destroy+0x19/0x40 [ath12k]\n ath12k_core_stop+0xe/0x80 [ath12k]\n ath12k_core_hw_group_cleanup+0x6b/0xb0 [ath12k]\n ath12k_pci_remove+0x60/0x110 [ath12k]\n\nCall trace for ath12k_dp_link_peer_rhash_tbl_destroy:\n RIP: irq_work_sync+0x1e/0x70\n rhashtable_destroy+0x12/0x60\n ath12k_dp_link_peer_rhash_tbl_destroy+0x29/0x50 [ath12k]\n ath12k_dp_cmn_device_deinit+0x21/0x140 [ath12k]\n ath12k_core_hw_group_cleanup+0x6b/0xb0 [ath12k]\n ath12k_pci_remove+0x60/0x110 [ath12k]\n\nFix this by adding NULL checks before calling rhashtable_destroy() in\nboth destroy functions.\n\nThe NULL check approach was chosen because the rhashtable pointer\nserves as the initialization state indicator. The init can fail at\nvarious points, leaving some components uninitialized. Checking the\npointer directly is simpler than adding separate state flags that\nwould need synchronization.","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":"wifi: ath12k: fix NULL pointer dereference in rhash table destroy","id":"CVE-2026-68191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"wifi: brcmfmac: make release_scratchbuffers idempotent","id":"CVE-2026-68192"},"packages":[],"prev":{"headline":"staging: rtl8723bs: fix OOB reads in rtw_get_wps_ie()","id":"CVE-2026-68190"},"products":["Linux"],"published":"2026-08-10","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-08-17","vendors":["Linux"]},"summary":"A NULL pointer dereference in the ath12k Wi-Fi driver during device unbinding can cause a kernel crash, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-68191/"}