# CVE-2024-20019: Denial of service in MT7925, MT7927

> A memory leak in the MediaTek Wi-Fi driver allows remote attackers to cause a denial of service without user interaction or privileges.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6h38-c284-95hc

## What is CVE-2024-20019?

CVE-2024-20019 is a medium-severity denial of service vulnerability in MediaTek, Inc. MT7925, MT7927, published on 4 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In wlan driver, there is a possible memory leak due to improper input handling. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00351241; Issue ID: MSV-1173.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Mediatek Software Package.

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

No fix has been published for CVE-2024-20019 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-20019 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-20019 is a medium-severity denial of service vulnerability in MediaTek, Inc. MT7925, MT7927, published on 4 Mar 2024. 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-2024-20019 in the wild and no public exploit code.

Affected product: MediaTek, Inc. MT7925, MT7927. 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-20019/ (Markdown: https://insights.sbomify.com/CVE-2024-20019/index.md)
```

## Sources

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

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