Vulnerability-Lookup

GHSA-FCF7-J5WV-2RXV

Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-10 15:33

Details

In the Linux kernel, the following vulnerability has been resolved:

wifi: ath12k: fix NULL pointer dereference in rhash table destroy

When unbinding the ath12k driver, kernel NULL pointer dereferences occur in irq_work_sync() called from rhashtable_destroy().

Two hash tables are affected: 1. ath12k_link_sta hash table in ath12k_base 2. ath12k_dp_link_peer hash table in ath12k_dp

The issue happens because the destroy functions are called unconditionally in cleanup paths, but the hash tables are only initialized late in their respective init functions. If the device was never fully started or if the init functions failed before initializing the hash tables, the pointers will be NULL. The issues are always reproducible from a VM because the MSI addressing initialization is failing.

Call trace for ath12k_link_sta_rhash_tbl_destroy: RIP: irq_work_sync+0x1e/0x70 rhashtable_destroy+0x12/0x60 ath12k_link_sta_rhash_tbl_destroy+0x19/0x40 [ath12k] ath12k_core_stop+0xe/0x80 [ath12k] ath12k_core_hw_group_cleanup+0x6b/0xb0 [ath12k] ath12k_pci_remove+0x60/0x110 [ath12k]

Call trace for ath12k_dp_link_peer_rhash_tbl_destroy: RIP: irq_work_sync+0x1e/0x70 rhashtable_destroy+0x12/0x60 ath12k_dp_link_peer_rhash_tbl_destroy+0x29/0x50 [ath12k] ath12k_dp_cmn_device_deinit+0x21/0x140 [ath12k] ath12k_core_hw_group_cleanup+0x6b/0xb0 [ath12k] ath12k_pci_remove+0x60/0x110 [ath12k]

Fix this by adding NULL checks before calling rhashtable_destroy() in both destroy functions.

The NULL check approach was chosen because the rhashtable pointer serves as the initialization state indicator. The init can fail at various points, leaving some components uninitialized. Checking the pointer directly is simpler than adding separate state flags that would need synchronization.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-68191"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-10T13:20:06Z",
    "severity": null
  },
  "details": "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.",
  "id": "GHSA-fcf7-j5wv-2rxv",
  "modified": "2026-08-10T15:33:40Z",
  "published": "2026-08-10T15:33:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68191"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/17a4298f7794843af0094035723dc5e7311c7453"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/70231dcd782201579990ded73e0435d18bb524ca"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-68191 (GCVE-0-2026-68191)

Vulnerability from cvelistv5 – Published: 2026-08-10 12:00 – Updated: 2026-08-17 05:00

Title

wifi: ath12k: fix NULL pointer dereference in rhash table destroy

Summary

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix NULL pointer dereference in rhash table destroy When unbinding the ath12k driver, kernel NULL pointer dereferences occur in irq_work_sync() called from rhashtable_destroy(). Two hash tables are affected: 1. ath12k_link_sta hash table in ath12k_base 2. ath12k_dp_link_peer hash table in ath12k_dp The issue happens because the destroy functions are called unconditionally in cleanup paths, but the hash tables are only initialized late in their respective init functions. If the device was never fully started or if the init functions failed before initializing the hash tables, the pointers will be NULL. The issues are always reproducible from a VM because the MSI addressing initialization is failing. Call trace for ath12k_link_sta_rhash_tbl_destroy: RIP: irq_work_sync+0x1e/0x70 rhashtable_destroy+0x12/0x60 ath12k_link_sta_rhash_tbl_destroy+0x19/0x40 [ath12k] ath12k_core_stop+0xe/0x80 [ath12k] ath12k_core_hw_group_cleanup+0x6b/0xb0 [ath12k] ath12k_pci_remove+0x60/0x110 [ath12k] Call trace for ath12k_dp_link_peer_rhash_tbl_destroy: RIP: irq_work_sync+0x1e/0x70 rhashtable_destroy+0x12/0x60 ath12k_dp_link_peer_rhash_tbl_destroy+0x29/0x50 [ath12k] ath12k_dp_cmn_device_deinit+0x21/0x140 [ath12k] ath12k_core_hw_group_cleanup+0x6b/0xb0 [ath12k] ath12k_pci_remove+0x60/0x110 [ath12k] Fix this by adding NULL checks before calling rhashtable_destroy() in both destroy functions. The NULL check approach was chosen because the rhashtable pointer serves as the initialization state indicator. The init can fail at various points, leaving some components uninitialized. Checking the pointer directly is simpler than adding separate state flags that would need synchronization.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/17a4298f7794843af…
https://git.kernel.org/stable/c/70231dcd782201579…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 57ccca410237285f8f25a988655e6910cadc63f2 , < 17a4298f7794843af0094035723dc5e7311c7453 (git) Affected: 57ccca410237285f8f25a988655e6910cadc63f2 , < 70231dcd782201579990ded73e0435d18bb524ca (git)
Linux	Linux	Affected: 7.0 Unaffected: 0 , < 7.0 (semver) Unaffected: 7.1.6 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/wireless/ath/ath12k/dp_peer.c",
            "drivers/net/wireless/ath/ath12k/peer.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "17a4298f7794843af0094035723dc5e7311c7453",
              "status": "affected",
              "version": "57ccca410237285f8f25a988655e6910cadc63f2",
              "versionType": "git"
            },
            {
              "lessThan": "70231dcd782201579990ded73e0435d18bb524ca",
              "status": "affected",
              "version": "57ccca410237285f8f25a988655e6910cadc63f2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/wireless/ath/ath12k/dp_peer.c",
            "drivers/net/wireless/ath/ath12k/peer.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.0"
            },
            {
              "lessThan": "7.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.6",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:00:33.856Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/17a4298f7794843af0094035723dc5e7311c7453"
        },
        {
          "url": "https://git.kernel.org/stable/c/70231dcd782201579990ded73e0435d18bb524ca"
        }
      ],
      "title": "wifi: ath12k: fix NULL pointer dereference in rhash table destroy",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-68191",
    "datePublished": "2026-08-10T12:00:09.069Z",
    "dateReserved": "2026-07-30T09:28:09.373Z",
    "dateUpdated": "2026-08-17T05:00:33.856Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.

Action not permitted

GHSA-FCF7-J5WV-2RXV

CVE-2026-68191 (GCVE-0-2026-68191)

Tags

Sightings

Nomenclature