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-68362wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb() The rtl8187_rx_cb() calculates the rx descriptor header address by subtracting its size from the skb tail pointer. However, it does not validate if the received packet (skb->len from urb->actual_length) is large enough to contain this header. If a truncated packet is received, this will lead to a buffer underflow, reading memory before the start of the skb data area, and causing a kernel panic. Add length checks for both rtl8187 and rtl8187b descriptor headers before attempting to access them, dropping the packet cleanly if the check fails.

Timeline

  1. ID reserved

    By Linux

  2. · 8 days later

    Published

  3. · 5 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.21% · top 88% of all CVEs (15 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 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < 118e12bf3e4288cf845cd3759bd9d4c99f91aab5
    • affected 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < 6a96bd0d94305fd04a6ac64446ec113bae289384
    • affected 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < e2f3ea15e804607e0a4a34a2f6c331c8750b68bc
    • affected 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < dc153401fb26c1640a2b279c47b65e1c416af276
    • affected 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < 4758770a673c60d8f615809304d72e1432fa6355
    • affected 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < 638d4148e166d114a4cd7becaae992ce1a815ed8
    • affected 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < 5ebf0fe7eaef9f6173a4c6ea77c5353e21645d15
    • affected 6f7853f3cbe457067e9fe05461f56c7ea4ac488c – < b647d2574e4583c2e3b0ab35568f60c88e910840
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • 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-68362 badge
[![CVE-2025-68362](https://cveledger.app/badge/CVE-2025-68362.svg)](https://cveledger.app/cve/CVE-2025-68362)

Record last updated .