Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 12 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < 3677c01891fb0239361e444afee8398868e34bdf
    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < 89caaeee8dd95fae8bb4f4964e6fe3ca688500c4
    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < a4fb7cca9837378878e6c94d9e7af019c8fdfcdb
    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < bf8513dfa31ea015c9cf415796dca2113d293840
    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < ee7db11742b30641f21306105ad27a275e3c61d7
    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < a813a74570212cb5f3a7d3b05c0cb0cd00bace1d
    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < c9d1c4152e6d32fa74034464854bee262a60bc43
    • affected f653211197f3841f383fa9757ef8ce182c6cf627 – < 9b5b9c042b30befc5b37e4539ace95af70843473
  • Linux · Linux

    • affected 2.6.25
    • unaffected < 2.6.25
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.63 – ≤ 6.12.*
    • unaffected 6.17.13 – ≤ 6.17.*
    • unaffected 6.18.2 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68759 badge
[![CVE-2025-68759](https://cveledger.app/badge/CVE-2025-68759.svg)](https://cveledger.app/cve/CVE-2025-68759)

Record last updated .