CVE-2026-80659

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.

• https://git.kernel.org/stable/c/2e6b9a394206c76dd417c991312f349435ef35e6
• https://git.kernel.org/stable/c/7ee7a77ec2f446109ab52cc80ace7acc22ab6211
• https://git.kernel.org/stable/c/8344611477c9241f45f20981990780fc5f0996f8
• https://git.kernel.org/stable/c/8672b8bdbd2063b3fcbd75f729e4706fcdad2257
• https://git.kernel.org/stable/c/9f5e04235a0b59e6e30af9f45511addf2604d757
• https://git.kernel.org/stable/c/bf9848a22a8e50d39d5e8d871581f0a8110f16b3
• https://git.kernel.org/stable/c/c2e1d33929565fa14c48d8a5a45edc3ebfc941b2
• https://git.kernel.org/stable/c/ee5fb641c4ccac8406c668d3e947eb20ce44f233

Published

Aug 28, 2026

Last Modified

Aug 28, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-80653In the Linux kernel, the following vulnerability has been re…8.4
• CVE-2026-80654In the Linux kernel, the following vulnerability has been re…
• CVE-2026-80655In the Linux kernel, the following vulnerability has been re…
• CVE-2026-80656In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80657In the Linux kernel, the following vulnerability has been re…
• CVE-2026-80658In the Linux kernel, the following vulnerability has been re…
• CVE-2026-80660In the Linux kernel, the following vulnerability has been re…
• CVE-2026-80661In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80662In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-80663In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-80664In the Linux kernel, the following vulnerability has been re…7.3
• CVE-2026-80665In the Linux kernel, the following vulnerability has been re…7.1