# CVE-2025-24912: Denial of service in hostapd

> An attacker positioned between hostapd and the RADIUS server can inject crafted packets to cause authentication failures, resulting in a denial of service.

- **Severity:** Low 3.7 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2025
- **Updated:** 12 Mar 2025
- **Also known as:** AZL-58604, AZL-58610, CLSA-2026-1786108949, CLSA-2026-1790066310, GHSA-97x4-g54c-4pvm, MGASA-2025-0113, OESA-2026-1438, OESA-2026-1439, OESA-2026-3177, SUSE-SU-2025:0977-1, SUSE-SU-2026:23038-1, SUSE-SU-2026:3159-1, SUSE-SU-2026:3281-1, SUSE-SU-2026:3490-1, openSUSE-SU-2025:14899-1, openSUSE-SU-2026:20985-1

## What is CVE-2025-24912?

CVE-2025-24912 is a low-severity denial of service vulnerability in Jouni Malinen hostapd, published on 12 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hostapd fails to process crafted RADIUS packets properly. When hostapd authenticates wi-fi devices with RADIUS authentication, an attacker in the position between the hostapd and the RADIUS server may inject crafted RADIUS packets and force RADIUS authentications to fail.

Weakness: CWE-826 (Premature Release of Resource During Expected Lifetime)

## Which versions are affected by CVE-2025-24912?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wpa_supplicant` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.9-150000.4.42.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.9-150000.4.42.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.10-150500.3.6.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 2.10-150600.7.6.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.9-23.23.1 |
| `wpa_supplicant` | SUSE:Linux Micro 6.0 | All versions | 2.10-6.1 |
| `wpa_supplicant` | openSUSE:Leap 15.6 | All versions | 2.10-150600.7.6.1 |
| `hostapd` | openSUSE:Leap 16.0 | All versions | 2.11-bp160.2.1 |
| `wpa_supplicant` | openSUSE:Tumbleweed | All versions | 2.11-4.1 |

Products: W1.fi Hostapd.

## How do I fix CVE-2025-24912?

Apply the vendor's patch.

## Is CVE-2025-24912 being exploited?

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

## Other vulnerabilities in Jouni Malinen hostapd

- [CVE-2016-10743](https://insights.sbomify.com/CVE-2016-10743/): Weak cryptography in n/a (high 7.5)
- [CVE-2019-5061](https://insights.sbomify.com/CVE-2019-5061/): Denial of service in W1.f1 (high 7.4)
- [CVE-2019-5062](https://insights.sbomify.com/CVE-2019-5062/): Denial of service in W1.f1 (high 7.4)
- [CVE-2026-58374](https://insights.sbomify.com/CVE-2026-58374/): Memory corruption in hostapd (medium 6.5)
- [CVE-2022-37660](https://insights.sbomify.com/CVE-2022-37660/): Other in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24912 and fix it if it is affected.

What it is: CVE-2025-24912 is a low-severity denial of service vulnerability in Jouni Malinen hostapd, published on 12 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24912 in the wild and no public exploit code.

Affected product: Jouni Malinen hostapd. 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-2025-24912/ (Markdown: https://insights.sbomify.com/CVE-2025-24912/index.md)
```

## Sources

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

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