Vulnerability-Lookup

GHSA-HPC6-P9X9-M2FC

Vulnerability from github – Published: 2026-10-06 09:31 – Updated: 2026-10-07 09:32

Details

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

wifi: cfg80211: get the wiphy out of a dying network namespace

When a network namespace is destroyed, cfg80211_pernet_exit() moves any wiphy back to the initial namespace, and just warns if that fails. But moving an interface can fail (due to allocation failures), and then the wiphy is left behind with a garbage netns pointer:

Kernel mode fault at addr 0x30 genlmsg_multicast_netns.constprop.0+0x46/0xcf [cfg80211] nl80211_notify_wiphy+0xcd/0xe8 [cfg80211] wiphy_unregister+0x169/0x3fc [cfg80211]

Note that commit debac3a20dec ("net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().") fixed another path that could reach it without allocation failures.

Remove interfaces that cannot be moved instead of failing the switch, so that the wiphy always ends up in the initial namespace. In this case the netdev core will unregister the interfaces anyway.

Severity

7.0 (High)


                  
                    CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-98330"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-06T09:18:25Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: get the wiphy out of a dying network namespace\n\nWhen a network namespace is destroyed, cfg80211_pernet_exit() moves any\nwiphy back to the initial namespace, and just warns if that fails. But\nmoving an interface can fail (due to allocation failures), and then the\nwiphy is left behind with a garbage netns pointer:\n\n  Kernel mode fault at addr 0x30\n  genlmsg_multicast_netns.constprop.0+0x46/0xcf [cfg80211]\n  nl80211_notify_wiphy+0xcd/0xe8 [cfg80211]\n  wiphy_unregister+0x169/0x3fc [cfg80211]\n\nNote that commit debac3a20dec (\"net: Remove conflicting altnames for\ndying netns in __dev_change_net_namespace().\") fixed another path\nthat could reach it without allocation failures.\n\nRemove interfaces that cannot be moved instead of failing the switch,\nso that the wiphy always ends up in the initial namespace. In this\ncase the netdev core will unregister the interfaces anyway.",
  "id": "GHSA-hpc6-p9x9-m2fc",
  "modified": "2026-10-07T09:32:16Z",
  "published": "2026-10-06T09:31:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98330"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4635b1a1c1d693178a537446a6e09963f0fdae52"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b949b2720688691f1e41bdbfbe3df2b6dc77c34d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/caa02072b2986d4b0e7a824de05782ef7b03a0ba"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-98330 (GCVE-0-2026-98330)

Vulnerability from cvelistv5 – Published: 2026-10-06 08:46 – Updated: 2026-10-07 06:50

Title

wifi: cfg80211: get the wiphy out of a dying network namespace

Summary

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: get the wiphy out of a dying network namespace When a network namespace is destroyed, cfg80211_pernet_exit() moves any wiphy back to the initial namespace, and just warns if that fails. But moving an interface can fail (due to allocation failures), and then the wiphy is left behind with a garbage netns pointer: Kernel mode fault at addr 0x30 genlmsg_multicast_netns.constprop.0+0x46/0xcf [cfg80211] nl80211_notify_wiphy+0xcd/0xe8 [cfg80211] wiphy_unregister+0x169/0x3fc [cfg80211] Note that commit debac3a20dec ("net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().") fixed another path that could reach it without allocation failures. Remove interfaces that cannot be moved instead of failing the switch, so that the wiphy always ends up in the initial namespace. In this case the netdev core will unregister the interfaces anyway.

Severity

7 (High)


                        
                          CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Assigner

Linux CNA under the mitre root

CNA scorecard D 54/100 over 6633 records in the last 180 days details

References

3 references

URL	Tags
https://git.kernel.org/stable/c/caa02072b2986d4b0…
https://git.kernel.org/stable/c/b949b2720688691f1…
https://git.kernel.org/stable/c/4635b1a1c1d693178…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 463d018323851a608eef52a9427b0585005c647f , < caa02072b2986d4b0e7a824de05782ef7b03a0ba (git) Affected: 463d018323851a608eef52a9427b0585005c647f , < b949b2720688691f1e41bdbfbe3df2b6dc77c34d (git) Affected: 463d018323851a608eef52a9427b0585005c647f , < 4635b1a1c1d693178a537446a6e09963f0fdae52 (git)
Linux	Linux	Affected: 2.6.32 Unaffected: 0 , < 2.6.32 (semver) Unaffected: 6.18.54 , ≤ 6.18.* (semver) Unaffected: 7.2.8 , ≤ 7.2.* (semver) Unaffected: 7.3-rc4 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/wireless/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "caa02072b2986d4b0e7a824de05782ef7b03a0ba",
              "status": "affected",
              "version": "463d018323851a608eef52a9427b0585005c647f",
              "versionType": "git"
            },
            {
              "lessThan": "b949b2720688691f1e41bdbfbe3df2b6dc77c34d",
              "status": "affected",
              "version": "463d018323851a608eef52a9427b0585005c647f",
              "versionType": "git"
            },
            {
              "lessThan": "4635b1a1c1d693178a537446a6e09963f0fdae52",
              "status": "affected",
              "version": "463d018323851a608eef52a9427b0585005c647f",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/wireless/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.32"
            },
            {
              "lessThan": "2.6.32",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.54",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc4",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.54",
                  "versionStartIncluding": "2.6.32",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.8",
                  "versionStartIncluding": "2.6.32",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc4",
                  "versionStartIncluding": "2.6.32",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: get the wiphy out of a dying network namespace\n\nWhen a network namespace is destroyed, cfg80211_pernet_exit() moves any\nwiphy back to the initial namespace, and just warns if that fails. But\nmoving an interface can fail (due to allocation failures), and then the\nwiphy is left behind with a garbage netns pointer:\n\n  Kernel mode fault at addr 0x30\n  genlmsg_multicast_netns.constprop.0+0x46/0xcf [cfg80211]\n  nl80211_notify_wiphy+0xcd/0xe8 [cfg80211]\n  wiphy_unregister+0x169/0x3fc [cfg80211]\n\nNote that commit debac3a20dec (\"net: Remove conflicting altnames for\ndying netns in __dev_change_net_namespace().\") fixed another path\nthat could reach it without allocation failures.\n\nRemove interfaces that cannot be moved instead of failing the switch,\nso that the wiphy always ends up in the initial namespace. In this\ncase the netdev core will unregister the interfaces anyway."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Everything is local netlink: NL80211_CMD_SET_WIPHY_NETNS moves the wiphy into a namespace, RTM_NEWLINKPROP adds an altname, and the namespace is then torn down. cfg80211_pernet_exit() calls __cfg80211_switch_netns(); dev_change_net_namespace() fails and the wiphy keeps a pointer to the freed netns. No WiFi frame is involved.\nAC:H - A wiphy only reaches a non-init netns if real root delegates it, since hwsim radios made in a userns are deleted by hwsim_exit_net() first. The forced failure (an altname clashing with an init_net device) works only on kernels without debac3a20dec; on others the switch fails only on allocation failure. The attacker cannot cause either precondition.\nPR:L - Once a wiphy has been delegated to a container, container root needs only CAP_NET_ADMIN in its own user namespace. That passes GENL_UNS_ADMIN_PERM and the ns_capable() check on the target in nl80211_wiphy_netns() for a nested netns, and lets it add the clashing altname with RTM_NEWLINKPROP. No init-namespace privilege is required.\nUI:N - The attacker moves the wiphy, adds the altname and destroys the nested netns on their own, so no victim action is needed.\nS:U - The dangling wiphy netns pointer is a kernel memory-safety bug inside the same kernel security authority. No VM or IOMMU boundary is crossed.\nC:H - After the switch fails, rdev-\u003ewiphy keeps a pointer to a freed struct net from net_cachep. Later wiphy_net() users such as nl80211_notify_wiphy() and genlmsg_multicast_netns() dereference that freed object, a use-after-free that can be exploited for kernel memory disclosure.\nI:H - The freed struct net can be reallocated, for example by the attacker creating new namespaces. The stale wiphy then works on attacker-influenced net state, and this use-after-free of a core kernel object could be exploited for memory corruption.\nA:H - syzbot hit a kernel fault in genlmsg_multicast_netns() via nl80211_notify_wiphy() in wiphy_unregister() when it touched the dangling netns pointer, which crashes the kernel."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-07T06:50:05.324Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/caa02072b2986d4b0e7a824de05782ef7b03a0ba"
        },
        {
          "url": "https://git.kernel.org/stable/c/b949b2720688691f1e41bdbfbe3df2b6dc77c34d"
        },
        {
          "url": "https://git.kernel.org/stable/c/4635b1a1c1d693178a537446a6e09963f0fdae52"
        }
      ],
      "title": "wifi: cfg80211: get the wiphy out of a dying network namespace",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-98330",
    "datePublished": "2026-10-06T08:46:22.688Z",
    "dateReserved": "2026-09-25T10:25:14.341Z",
    "dateUpdated": "2026-10-07T06:50:05.324Z",
    "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.

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.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

GHSA-HPC6-P9X9-M2FC

CVE-2026-98330 (GCVE-0-2026-98330)

Tags

Sightings

Nomenclature

Related by attack behaviour