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-2026-68349wifi: carl9170: fix buffer overflow in rx_stream failover path

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: fix buffer overflow in rx_stream failover path The failover continuation in carl9170_rx_stream() copies the full tlen from the second USB transfer instead of capping at rx_failover_missing bytes. When both transfers are near maximum size, the total exceeds the 65535-byte failover SKB, triggering skb_over_panic. Limit the copy size to the missing byte count. [Fix checkpatch CHECK:PARENTHESIS_ALIGNMENT]

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 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: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < 5fb00a09e9b0375e1ad9d4fefc4a62a67e7ea658
    • affected a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < 48c81fb523ecdc6a4b8654944ff32e499f21e6d0
    • affected a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < a1ce01764a812c22a47d30aea78e347aebd3eea1
    • affected a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < 5acfa18de66b6089b81c1c0bf1a3ae3c940ec39e
    • affected a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < b9dfee5e63ee9b5c47be9e344ebc5bd3f43fca78
    • affected a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < 4503829843353dbb18b879c35be1cdfc9af677b7
    • affected a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < 21f59906ea75618fdd46a7e32754d54fbee083ea
    • affected a84fab3cbfdc427e7d366f1cc844f27b2084c26c – < a1a21995c2e1cc2ca6b2226cfe4f5f018370182a
  • Linux · Linux

    • affected 2.6.37
    • unaffected < 2.6.37
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .