Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54159: usb: mtu3: fix kernel panic at qmu transfer done irq handler

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 012936502a9cb7b0604e85bb961eb15e2bb40dd9, 26ca30516b2c49dd04c134cbdf122311c538df98, 3a7d4959560a2ee493ef222e3b63d359365f41ec.

Low priority for now. Upgrade to Linux Linux 012936502a9cb7b0604e85bb961eb15e2bb40dd9, 26ca30516b2c49dd04c134cbdf122311c538df98, 3a7d4959560a2ee493ef222e3b63d359365f41ec or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-54159

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.2affected
    • 48e0d3735aa557a8adaf94632ca3cf78798e8505 and later · before 26ca30516b2c49dd04c134cbdf122311c538df98affected · git
    • 48e0d3735aa557a8adaf94632ca3cf78798e8505 and later · before 012936502a9cb7b0604e85bb961eb15e2bb40dd9affected · git
    • 48e0d3735aa557a8adaf94632ca3cf78798e8505 and later · before ee53a7a88027cea765c68f3b00a50b8f58d6f786affected · git
    • 48e0d3735aa557a8adaf94632ca3cf78798e8505 and later · before f26273428657ef4ca74740e578ae45a3be492f6faffected · git
    • 48e0d3735aa557a8adaf94632ca3cf78798e8505 and later · before b636aff94a67be46582d4321d11743f1a10cc2c1affected · git
    • 48e0d3735aa557a8adaf94632ca3cf78798e8505 and later · before 3a7d4959560a2ee493ef222e3b63d359365f41ecaffected · git
    • 48e0d3735aa557a8adaf94632ca3cf78798e8505 and later · before d28f4091ea7ec3510fd6a3c6d433234e7a2bef14affected · git
    • before 5.2not affected · semver
    • 5.4.243 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.37-16.1.37-1
Debian:13linuxbefore 6.3.7-16.3.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54157Dec 24, 2025 · binder: fix UAF of alloc->vma in race with munmap()
    31Monitor
  • ← EarlierCVE-2023-54158Dec 24, 2025 · btrfs: don't free qgroup space unless specified
    0Monitor
  • Later →CVE-2023-54160Dec 24, 2025 · firmware: arm_sdei: Fix sleep from invalid context BUG
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux012936502a9cb7b0604e85bb961eb15e2bb40dd9Vendor (CNA)
Linux Linux26ca30516b2c49dd04c134cbdf122311c538df98Vendor (CNA)
Linux Linux3a7d4959560a2ee493ef222e3b63d359365f41ecVendor (CNA)
Linux Linuxb636aff94a67be46582d4321d11743f1a10cc2c1Vendor (CNA)
Linux Linuxd28f4091ea7ec3510fd6a3c6d433234e7a2bef14Vendor (CNA)
Linux Linuxee53a7a88027cea765c68f3b00a50b8f58d6f786Vendor (CNA)
Linux Linuxf26273428657ef4ca74740e578ae45a3be492f6fVendor (CNA)
debian:linux6.1.37-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records