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

> A logic error in the Linux kernel WiFi subsystem causes a kernel warning and potential crash during link deletion, leading to denial of service.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jan 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-62705, AZL-68573, BELL-CVE-2024-57898, DEBIAN-CVE-2024-57898, GHSA-9w4x-56rq-p7vj, ROOT-OS-DEBIAN-11-CVE-2024-57898, ROOT-OS-DEBIAN-12-CVE-2024-57898, ROOT-OS-UBUNTU-2204-CVE-2024-57898, UBUNTU-CVE-2024-57898

## What is CVE-2024-57898?

CVE-2024-57898 is a low-severity vulnerability in Linux kernel, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2024-57898?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-57898?

Apply the vendor's patch.

## Is CVE-2024-57898 being exploited?

There is no known exploitation of CVE-2024-57898 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-57898 and fix it if it is affected.

What it is: CVE-2024-57898 is a low-severity vulnerability in Linux kernel, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-57898 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-57898/ (Markdown: https://insights.sbomify.com/CVE-2024-57898/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-57898
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-57898
- OSV: https://osv.dev/vulnerability/CVE-2024-57898

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-57898/
Summaries are generated and may contain mistakes; the official description above is the record.