Skip to main content
VulnerabilityPublished Updated

CVE-2026-80659: Linux kernel · mmc: vub300: defer reset until cmd_mutex is unlocked

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ee5fb641c4ccac8406c668d3e947eb20ce44f233 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:41 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ee5fb641c4ccac8406c668d3e947eb20ce44f233, c2e1d33929565fa14c48d8a5a45edc3ebfc941b2, bf9848a22a8e50d39d5e8d871581f0a8110f16b3 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 88095e7b473a3d9ec3b9c60429576e9cbd327c89, < ee5fb641c4ccac8406c668d3e947eb20ce44f233
Fixed in
  • ee5fb641c4ccac8406c668d3e947eb20ce44f233
LinuxLinuxAffected
  • ≥ 88095e7b473a3d9ec3b9c60429576e9cbd327c89, < c2e1d33929565fa14c48d8a5a45edc3ebfc941b2
Fixed in
  • c2e1d33929565fa14c48d8a5a45edc3ebfc941b2
LinuxLinuxAffected
  • ≥ 88095e7b473a3d9ec3b9c60429576e9cbd327c89, < bf9848a22a8e50d39d5e8d871581f0a8110f16b3
Fixed in
  • bf9848a22a8e50d39d5e8d871581f0a8110f16b3
LinuxLinuxAffected
  • ≥ 88095e7b473a3d9ec3b9c60429576e9cbd327c89, < 8344611477c9241f45f20981990780fc5f0996f8
Fixed in
  • 8344611477c9241f45f20981990780fc5f0996f8
LinuxLinuxAffected
  • ≥ 88095e7b473a3d9ec3b9c60429576e9cbd327c89, < 8672b8bdbd2063b3fcbd75f729e4706fcdad2257
Fixed in
  • 8672b8bdbd2063b3fcbd75f729e4706fcdad2257
LinuxLinuxAffected
  • ≥ 88095e7b473a3d9ec3b9c60429576e9cbd327c89, < 9f5e04235a0b59e6e30af9f45511addf2604d757
Fixed in
  • 9f5e04235a0b59e6e30af9f45511addf2604d757

AI-suggested

A fix is available in the Linux kernel as indicated by multiple fixed commit versions. Users should update to a Linux kernel version that includes these fixes to avoid the deadlock issue. No additional mitigation is required beyond applying the official fix.

Description

A deadlock vulnerability in the Linux kernel's mmc vub300 driver was fixed by deferring USB device reset until after the cmd_mutex is released. The issue involved recursive locking of cmd_mutex during a device reset triggered by a command timeout, causing a deadlock.

References

Community reviews

Loading reviews…