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-2023-54159usb: mtu3: fix kernel panic at qmu transfer done irq handler

Description

In the Linux kernel, the following vulnerability has been resolved: usb: mtu3: fix kernel panic at qmu transfer done irq handler When handle qmu transfer irq, it will unlock @mtu->lock before give back request, if another thread handle disconnect event at the same time, and try to disable ep, it may lock @mtu->lock and free qmu ring, then qmu irq hanlder may get a NULL gpd, avoid the KE by checking gpd's value before handling it. e.g. qmu done irq on cpu0 thread running on cpu1 qmu_done_tx() handle gpd [0] mtu3_requ_complete() mtu3_gadget_ep_disable() unlock @mtu->lock give back request lock @mtu->lock mtu3_ep_disable() mtu3_gpd_ring_free() unlock @mtu->lock lock @mtu->lock get next gpd [1] [1]: goto [0] to handle next gpd, and next gpd may be NULL.

Timeline

  1. ID reserved

    By Linux

  2. 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 89% 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: Not scored.

Affected products

  • Linux · Linux

    • affected 48e0d3735aa557a8adaf94632ca3cf78798e8505 – < 26ca30516b2c49dd04c134cbdf122311c538df98
    • affected 48e0d3735aa557a8adaf94632ca3cf78798e8505 – < 012936502a9cb7b0604e85bb961eb15e2bb40dd9
    • affected 48e0d3735aa557a8adaf94632ca3cf78798e8505 – < ee53a7a88027cea765c68f3b00a50b8f58d6f786
    • affected 48e0d3735aa557a8adaf94632ca3cf78798e8505 – < f26273428657ef4ca74740e578ae45a3be492f6f
    • affected 48e0d3735aa557a8adaf94632ca3cf78798e8505 – < b636aff94a67be46582d4321d11743f1a10cc2c1
    • affected 48e0d3735aa557a8adaf94632ca3cf78798e8505 – < 3a7d4959560a2ee493ef222e3b63d359365f41ec
    • affected 48e0d3735aa557a8adaf94632ca3cf78798e8505 – < d28f4091ea7ec3510fd6a3c6d433234e7a2bef14
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 5.4.243 – ≤ 5.4.*
    • unaffected 5.10.180 – ≤ 5.10.*
    • unaffected 5.15.111 – ≤ 5.15.*
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .