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-2022-49661can: gs_usb: gs_usb_open/close(): fix memory leak

Description

In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b ("can: esd_usb2: fix memory leak").

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 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

CVSS scores of CVE-2022-49661, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < 339fa9f80d3b94177a7a459c6d115d3b56007d5a
    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < c1d806bc29ff7ffe0e2a023583c8720ed96cb0b0
    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < d91492638b054f4a359621ef216242be5973ed6b
    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < 6f655b5e13fa4b27e915b6c209ac0da74fd75963
    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < d0b8e223998866b3e7b2895927d4e9689b0a80d8
    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < 0e60230bc64355c80abe993d1719fdb318094e20
    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < ffb6cc6601ec7c8fa963dcf76025df4a02f2cf5c
    • affected d08e973a77d128b25e01a08c34d89593fdf222da – < 2bda24ef95c0311ab93bda00db40486acf30bd0a
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 4.9.323 – ≤ 4.9.*
    • unaffected 4.14.288 – ≤ 4.14.*
    • unaffected 4.19.252 – ≤ 4.19.*
    • unaffected 5.4.205 – ≤ 5.4.*
    • unaffected 5.10.130 – ≤ 5.10.*
    • unaffected 5.15.54 – ≤ 5.15.*
    • unaffected 5.18.11 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .