Skip to content
Heist/ feed
Back to feed
UnratedFix available

wifi: cfg80211: clear link ID from bitmap during link delete after clean up

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: clear link ID from bitmap during link delete after clean up Currently, during link deletion, the link ID is first removed from the valid_links bitmap before performing any clean-up operations. However, some functions require the link ID to remain in the valid_links bitmap. One such example is cfg80211_cac_event(). The flow is - nl80211_remove_link() cfg80211_remove_link() ieee80211_del_intf_link() ieee80211_vif_set_links() ieee80211_vif_update_links() ieee80211_link_stop() cfg80211_cac_event() cfg80211_cac_event() requires link ID to be present but it is cleared already in cfg80211_remove_link(). Ultimately, WARN_ON() is hit. Therefore, clear the link ID from the bitmap only after completing the link clean-up.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.9
CVEs
CVE-2024-57898
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 11:53 UTC · Revision 1

Source evidence

wifi: cfg80211: clear link ID from bitmap during link delete after clean up

core-osv · Original source

Published 15 Jan 2025, 13:05 UTC

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: clear link ID from bitmap during link delete after clean up Currently, during link deletion, the link ID is first removed from the valid_links bitmap before performing any clean-up operations. However, some functions require the link ID to remain in the valid_links bitmap. One such example is cfg80211_cac_event(). The flow is - nl80211_remove_link() cfg80211_remove_link() ieee80211_del_intf_link() ieee80211_vif_set_links() ieee80211_vif_update_links() ieee80211_link_stop() cfg80211_cac_event() cfg80211_cac_event() requires link ID to be present but it is cleared already in cfg80211_remove_link(). Ultimately, WARN_ON() is hit. Therefore, clear the link ID from the bitmap only after completing the link clean-up.

osv:CVE-2024-57898

Kernel

Fixed versions: 6.12.9

Complete source record
{
  "id": "f09080dd3d3e14b415a462a87ac0fd8b41e2d7010601591a245081bd245b01da",
  "url": "https://osv.dev/vulnerability/CVE-2024-57898",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "wifi: cfg80211: clear link ID from bitmap during link delete after clean up",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: clear link ID from bitmap during link delete after clean up Currently, during link deletion, the link ID is first removed from the valid_links bitmap before performing any clean-up operations. However, some functions require the link ID to remain in the valid_links bitmap. One such example is cfg80211_cac_event(). The flow is - nl80211_remove_link() cfg80211_remove_link() ieee80211_del_intf_link() ieee80211_vif_set_links() ieee80211_vif_update_links() ieee80211_link_stop() cfg80211_cac_event() cfg80211_cac_event() requires link ID to be present but it is cleared already in cfg80211_remove_link(). Ultimately, WARN_ON() is hit. Therefore, clear the link ID from the bitmap only after completing the link clean-up.",
    "evidence": "osv:CVE-2024-57898",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.12.9",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2024-57898",
      "aliases": [
        "CVE-2024-57898"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "d74380ee99b59a2e46612c12c85e701ab213f4ea"
                },
                {
                  "fixed": "ae07daf440d3220d0986e676317a5da66e4f9dfd"
                },
                {
                  "fixed": "b5c32ff6a3a38c74facdd1fe34c0d709a55527fd"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-57898.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.12.0"
                },
                {
                  "fixed": "6.12.9"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-57898.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:35.302246343Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/ae07daf440d3220d0986e676317a5da66e4f9dfd",
        "https://git.kernel.org/stable/c/b5c32ff6a3a38c74facdd1fe34c0d709a55527fd",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/57xxx/CVE-2024-57898.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-57898",
        "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/2024/57xxx/CVE-2024-57898.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-57898",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 502187,
  "published_at": "2025-01-15T13:05:49.718+00:00"
}