CVE-2025-68759: wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 3677c01891fb0239361e444afee8398868e34bdf, 89caaeee8dd95fae8bb4f4964e6fe3ca688500c4, 9b5b9c042b30befc5b37e4539ace95af70843473; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 3677c01891fb0239361e444afee8398868e34bdf, 89caaeee8dd95fae8bb4f4964e6fe3ca688500c4, 9b5b9c042b30befc5b37e4539ace95af70843473; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 5, 2026
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.25affected
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before 3677c01891fb0239361e444afee8398868e34bdfaffected · git
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before 89caaeee8dd95fae8bb4f4964e6fe3ca688500c4affected · git
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before a4fb7cca9837378878e6c94d9e7af019c8fdfcdbaffected · git
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before bf8513dfa31ea015c9cf415796dca2113d293840affected · git
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before ee7db11742b30641f21306105ad27a275e3c61d7affected · git
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before a813a74570212cb5f3a7d3b05c0cb0cd00bace1daffected · git
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before c9d1c4152e6d32fa74034464854bee262a60bc43affected · git
- f653211197f3841f383fa9757ef8ce182c6cf627 and later · before 9b5b9c042b30befc5b37e4539ace95af70843473affected · git
- before 2.6.25not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68756Jan 5, 2026 · block: Use RCU in blk_mq_[un]quiesce_tagset() instead of set->tag_list_lock0Monitor
- ← EarlierCVE-2025-68758Jan 5, 2026 · backlight: led-bl: Add devlink to supplier LEDs0Monitor
- Later →CVE-2025-68760Jan 5, 2026 · iommu/amd: Fix potential out-of-bounds read in iommu_mmio_show0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3677c01891fb0239361e444afee8398868e34bdf | Vendor (CNA) |
| Linux Linux | 89caaeee8dd95fae8bb4f4964e6fe3ca688500c4 | Vendor (CNA) |
| Linux Linux | 9b5b9c042b30befc5b37e4539ace95af70843473 | Vendor (CNA) |
| Linux Linux | a4fb7cca9837378878e6c94d9e7af019c8fdfcdb | Vendor (CNA) |
| Linux Linux | a813a74570212cb5f3a7d3b05c0cb0cd00bace1d | Vendor (CNA) |
| Linux Linux | bf8513dfa31ea015c9cf415796dca2113d293840 | Vendor (CNA) |
| Linux Linux | c9d1c4152e6d32fa74034464854bee262a60bc43 | Vendor (CNA) |
| Linux Linux | ee7db11742b30641f21306105ad27a275e3c61d7 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/89caaeee8dd95fae8bb4f4964e6fe3ca688500c4
- git.kernel.org/stable/c/9b5b9c042b30befc5b37e4539ace95af70843473
- git.kernel.org/stable/c/a4fb7cca9837378878e6c94d9e7af019c8fdfcdb
- git.kernel.org/stable/c/a813a74570212cb5f3a7d3b05c0cb0cd00bace1d
- git.kernel.org/stable/c/bf8513dfa31ea015c9cf415796dca2113d293840
- git.kernel.org/stable/c/c9d1c4152e6d32fa74034464854bee262a60bc43
- git.kernel.org/stable/c/ee7db11742b30641f21306105ad27a275e3c61d7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.