Skip to content
Heist/ feed
Back to feed
UnratedFix available

wifi: mac80211: reject VHT opmode for unsupported channel widths

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: reject VHT opmode for unsupported channel widths VHT operating mode notifications are not defined for channel widths below 20 MHz. In particular, 5 MHz and 10 MHz are not valid under the VHT specification and must be rejected. Without this check, malformed notifications using these widths may reach ieee80211_chan_width_to_rx_bw(), leading to a WARN_ON due to invalid input. This issue was reported by syzbot. Reject these unsupported widths early in sta_link_apply_parameters() when opmode_notif is used. The accepted set includes 20, 40, 80, 160, and 80+80 MHz, which are valid for VHT. While 320 MHz is not defined for VHT, it is allowed to avoid rejecting HE or EHT clients that may still send a VHT opmode notification.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.15.7
CVEs
CVE-2025-38509
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 00:32 UTC · Revision 1

Source evidence

wifi: mac80211: reject VHT opmode for unsupported channel widths

core-osv · Original source

Published 16 Aug 2025, 10:54 UTC

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: reject VHT opmode for unsupported channel widths VHT operating mode notifications are not defined for channel widths below 20 MHz. In particular, 5 MHz and 10 MHz are not valid under the VHT specification and must be rejected. Without this check, malformed notifications using these widths may reach ieee80211_chan_width_to_rx_bw(), leading to a WARN_ON due to invalid input. This issue was reported by syzbot. Reject these unsupported widths early in sta_link_apply_parameters() when opmode_notif is used. The accepted set includes 20, 40, 80, 160, and 80+80 MHz, which are valid for VHT. While 320 MHz is not defined for VHT, it is allowed to avoid rejecting HE or EHT clients that may still send a VHT opmode notification.

osv:CVE-2025-38509

Kernel

Fixed versions: 6.15.7

Complete source record
{
  "id": "f337a1848e4c238a4c6822a3e5747520bb561526f2f628b7f62374e153fc7124",
  "url": "https://osv.dev/vulnerability/CVE-2025-38509",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "wifi: mac80211: reject VHT opmode for unsupported channel widths",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: reject VHT opmode for unsupported channel widths VHT operating mode notifications are not defined for channel widths below 20 MHz. In particular, 5 MHz and 10 MHz are not valid under the VHT specification and must be rejected. Without this check, malformed notifications using these widths may reach ieee80211_chan_width_to_rx_bw(), leading to a WARN_ON due to invalid input. This issue was reported by syzbot. Reject these unsupported widths early in sta_link_apply_parameters() when opmode_notif is used. The accepted set includes 20, 40, 80, 160, and 80+80 MHz, which are valid for VHT. While 320 MHz is not defined for VHT, it is allowed to avoid rejecting HE or EHT clients that may still send a VHT opmode notification.",
    "evidence": "osv:CVE-2025-38509",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.15.7",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-38509",
      "aliases": [
        "CVE-2025-38509"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "751e7489c1d74b94ffffbed619d8fd724eeff4ee"
                },
                {
                  "fixed": "18eca59a04500b68a90e0c5c873f97c9d1ea2bfa"
                },
                {
                  "fixed": "58fcb1b4287ce38850402bb2bb16d09bf77b91d9"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38509.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.15.7"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38509.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:32.653734634Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/18eca59a04500b68a90e0c5c873f97c9d1ea2bfa",
        "https://git.kernel.org/stable/c/58fcb1b4287ce38850402bb2bb16d09bf77b91d9",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38509.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-38509",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38509.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-38509",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 499342,
  "published_at": "2025-08-16T10:54:46.493+00:00"
}