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-68413wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one()

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one() The memory allocated in the ipw2100_alloc_device() function is not freed in some of the error paths in ipw2100_pci_init_one(). Fix that by converting the direct return into a goto to the error path return. The error path when pci_enable_device() fails cannot jump to fail, since at this point priv is not set, so perform error handling inline.

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 (15 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 2c86c275015c880e810830304a3a4ab94803b38b – < 71614326ab43e8b8f392ba865aeb6d7e327dff7d
    • affected 2c86c275015c880e810830304a3a4ab94803b38b – < 9b080198a22fd809c4e7f6793eafab53ac2643fd
    • affected 2c86c275015c880e810830304a3a4ab94803b38b – < 768a701362a8f77b62c14f8202ad559b7ecbb0c6
    • affected 2c86c275015c880e810830304a3a4ab94803b38b – < f75b9a2a9d8334ae0f9c5e47df7b31f7aeb1fdbe
    • affected 2c86c275015c880e810830304a3a4ab94803b38b – < 836a19c654dcb1b01878a70090af016fbd0fd7e5
    • affected 2c86c275015c880e810830304a3a4ab94803b38b – < f442e581a88937671a22ceb3806c186265ef6254
    • affected 2c86c275015c880e810830304a3a4ab94803b38b – < 7cbda50eebcd9aa00b0de382f776287cf7a36cf8
    • affected 2c86c275015c880e810830304a3a4ab94803b38b – < 0d388f62031dbabcba0f44bb91b59f10e88cac17
  • Linux · Linux

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

Record last updated .