# CVE-2025-68759: wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring()

> A memory leak in the Linux kernel rtl818x Wi-Fi driver allows attackers to cause denial of service by exhausting system memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2026
- **Updated:** 11 May 2026
- **Also known as:** AZL-73406, BELL-CVE-2025-68759, DEBIAN-CVE-2025-68759, GHSA-55hf-cr49-h3r7, ROOT-OS-DEBIAN-11-CVE-2025-68759, ROOT-OS-DEBIAN-12-CVE-2025-68759, ROOT-OS-DEBIAN-13-CVE-2025-68759, ROOT-OS-UBUNTU-2204-CVE-2025-68759, ROOT-OS-UBUNTU-2404-CVE-2025-68759, UBUNTU-CVE-2025-68759

## What is CVE-2025-68759?

CVE-2025-68759 is a memory corruption vulnerability in Linux, published on 5 Jan 2026. 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: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring()

In rtl8180_init_rx_ring(), memory is allocated for skb packets and DMA
allocations in a loop. When an allocation fails, the previously
successful allocations are not freed on exit.

Fix that by jumping to err_free_rings label on error, which calls
rtl8180_free_rx_ring() to free the allocations. Remove the free of
rx_ring in rtl8180_init_rx_ring() error path, and set the freed
priv->rx_buf entry to null, to avoid double free.

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


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

Apply the vendor's patch.

## Is CVE-2025-68759 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68759 is a memory corruption vulnerability in Linux, published on 5 Jan 2026. 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-2025-68759 in the wild and no public exploit code.

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

## Sources

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

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