CVE-2026-80659

CVE CVE-2026-80659EUVD EUVD-2026-67535Published 2026-08-28T06:49:04.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: mmc: vub300: defer reset until cmd_mutex is unlocked vub300_cmndwork_thread() holds cmd_mutex while it sends a command and waits for the command response. If the response wait times out, __vub300_command_response() kills the command URBs and then synchronously resets the USB device through usb_reset_device(). That reset path re-enters the driver through vub300_pre_reset(), which also takes cmd_mutex. The worker therefore tries to acquire the same mutex recursively while it is still holding it from the command path. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the real worker and timeout/reset carrier: vub300_cmndwork_thread() __vub300_command_response() usb_lock_device_for_reset() usb_reset_device() vub300_pre_reset() Lockdep reported the same-task recursive acquisition on cmd_mutex: WARNING: possible recursive locking detected ... (&test_vub300.cmd_mutex) ... at: usb_reset_device... [vuln_msv] ... (&test_vub300.cmd_mutex) ... at: vub300_cmndwork_thread+0x12/0x20 [vuln_msv] Workqueue: vub300_cmd_wq vub300_cmndwork_thread [vuln_msv] *** DEADLOCK *** Return a flag from __vub300_command_response() when the timeout path needs a device reset, then perform the reset after vub300_cmndwork_thread() has cleared the in-flight command state and dropped cmd_mutex. The reset is still attempted before mmc_request_done(), preserving the existing request completion ordering while avoiding the recursive lock.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.2; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <c2e1d33929565fa14c48d8a5a45edc3ebfc941b2; patch: 7.1.5; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <9f5e04235a0b59e6e30af9f45511addf2604d757; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <8672b8bdbd2063b3fcbd75f729e4706fcdad2257; patch: 5.15.212; patch: 6.18.40; patch: 6.12.97; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <7ee7a77ec2f446109ab52cc80ace7acc22ab6211; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <2e6b9a394206c76dd417c991312f349435ef35e6; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <ee5fb641c4ccac8406c668d3e947eb20ce44f233; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <bf9848a22a8e50d39d5e8d871581f0a8110f16b3; 3.0; 88095e7b473a3d9ec3b9c60429576e9cbd327c89 <8344611477c9241f45f20981990780fc5f0996f8; patch: 6.1.178; patch: 5.10.261; patch: 6.6.145; patch: 0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.