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-23058can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak

Description

In the Linux kernel, the following vulnerability has been resolved: can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In ems_usb_open(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback ems_usb_read_bulk_callback(), the URBs are processed and resubmitted. In ems_usb_close() the URBs are freed by calling usb_kill_anchored_urbs(&dev->rx_submitted). However, this does not take into account that the USB framework unanchors the URB before the complete function is called. This means that once an in-URB has been completed, it is no longer anchored and is ultimately not released in ems_usb_close(). Fix the memory leak by anchoring the URB in the ems_usb_read_bulk_callback() to the dev->rx_submitted anchor.

Timeline

  1. ID reserved

    By Linux

  2. · 22 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: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 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 702171adeed3607ee9603ec30ce081411e36ae42 – < e2c71030dc464d437110bcfb367c493fd402bddb
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < f48eabd15194b216030b32445f44230df95f5fe0
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 61e6d3674c3d1da1475dc207b3e75c55d678d18e
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < e9410fdd4d5f7eaa6526d8c80e83029d7c86a8e8
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 46a191ff7eeec33a2ccb2a1bfea34e18fbc5dc1a
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 68c62b3e53901846b5f68c5a8bade72a5d9c0b87
    • affected 702171adeed3607ee9603ec30ce081411e36ae42 – < 0ce73a0eb5a27070957b67fd74059b6da89cc516
  • Linux · Linux

    • affected 2.6.32
    • unaffected < 2.6.32
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .