LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57898: wifi: cfg80211: clear link ID from bitmap during link delete after clean up

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-57898 is a Linux kernel Wi-Fi subsystem bug where link cleanup happens in the wrong order. The documented impact is a kernel WARN_ON condition during link deletion. Public sources do not provide CVSS, CWE, confirmed exploitation, or a broader impact claim, so business risk should be treated as uncertain until vendor guidance is reviewed.

Executive priority

Handle through normal kernel patch governance unless internal evidence shows crashes or service disruption. There is no sourced active exploitation or severity score, but kernel Wi-Fi defects still merit timely remediation on laptops, access points, appliances, and embedded Linux systems using affected kernels.

Technical view

In cfg80211 link deletion, the link ID is cleared from valid_links before cleanup completes. cfg80211_cac_event() may still require that link ID during the nl80211_remove_link() cleanup path, causing WARN_ON. The upstream resolution delays clearing the link ID until after link cleanup finishes.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or builds containing the vulnerable cfg80211 behavior, especially wireless-capable systems. The CVE data identifies Linux kernel 6.12-related versions and referenced stable commits, but distribution backports may change practical exposure.

Exploitation context

The provided sources do not state active exploitation, public exploit availability, required attacker position, or reliable security impact beyond triggering WARN_ON. KEV status is false in the supplied bundle. Treat exploitation context as incomplete rather than assuming remote exploitability.

Researcher notes

Focus validation on cfg80211/nl80211 multi-link deletion behavior and whether valid_links is cleared before ieee80211 cleanup paths complete. The source evidence supports a WARN_ON due to ordering, not a confirmed privilege escalation, data exposure, or remote code execution claim.

Mitigation direction

  • Review Linux vendor or distribution advisories for CVE-2024-57898.
  • Update to a kernel containing the referenced stable cfg80211 fix.
  • Prioritize wireless-capable systems running affected 6.12-era kernels.
  • Track distro backports, because fixed package versions may differ from upstream tags.

Validation and detection

  • Inventory kernel versions on wireless-capable Linux assets.
  • Confirm whether the referenced stable commits or distro equivalents are present.
  • Review kernel logs for WARN_ON events involving cfg80211 link deletion paths.
  • Verify vendor advisory status for each supported Linux distribution.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-57898 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd74380ee99b59a2e46612c12c85e701ab213f4ea, d74380ee99b59a2e46612c12c85e701ab213f4eaunaffected
LinuxLinux6.12, 0, 6.12.9, 6.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.