{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80659 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80659 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80659 and fix it if it is affected.\n\nWhat it is: CVE-2026-80659 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80659 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80659/ (Markdown: https://insights.sbomify.com/CVE-2026-80659/index.md)","id":"CVE-2026-80659","markdown":"https://insights.sbomify.com/CVE-2026-80659/index.md","name":"CVE-2026-80659","record":{"aliases":["BELL-CVE-2026-80659","DEBIAN-CVE-2026-80659","GHSA-7xh8-9fpc-p64f","UBUNTU-CVE-2026-80659"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A recursive locking bug in the vub300 MMC driver causes a deadlock and system hang when a USB command times out, requiring local access to trigger.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmmc: vub300: defer reset until cmd_mutex is unlocked\n\nvub300_cmndwork_thread() holds cmd_mutex while it sends a command and\nwaits for the command response.  If the response wait times out,\n__vub300_command_response() kills the command URBs and then synchronously\nresets the USB device through usb_reset_device().\n\nThat reset path re-enters the driver through vub300_pre_reset(), which\nalso takes cmd_mutex.  The worker therefore tries to acquire the same\nmutex recursively while it is still holding it from the command path.\n\nThis issue was found by our static analysis tool and then manually\nreviewed against the current tree.\n\nThe grounded PoC kept the real worker and timeout/reset carrier:\n\n  vub300_cmndwork_thread()\n  __vub300_command_response()\n  usb_lock_device_for_reset()\n  usb_reset_device()\n  vub300_pre_reset()\n\nLockdep reported the same-task recursive acquisition on cmd_mutex:\n\n  WARNING: possible recursive locking detected\n  ... (\u0026test_vub300.cmd_mutex) ... at: usb_reset_device... [vuln_msv]\n  ... (\u0026test_vub300.cmd_mutex) ... at: vub300_cmndwork_thread+0x12/0x20 [vuln_msv]\n  Workqueue: vub300_cmd_wq vub300_cmndwork_thread [vuln_msv]\n  *** DEADLOCK ***\n\nReturn a flag from __vub300_command_response() when the timeout path needs\na device reset, then perform the reset after vub300_cmndwork_thread() has\ncleared the in-flight command state and dropped cmd_mutex.  The reset is\nstill attempted before mmc_request_done(), preserving the existing request\ncompletion ordering while avoiding the recursive lock.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mmc: vub300: defer reset until cmd_mutex is unlocked","id":"CVE-2026-80659","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"hwmon: (occ) unregister sysfs devices outside occ lock","id":"CVE-2026-80660"},"packages":[],"prev":{"headline":"drm/rockchip: dw_dp: Fix null-ptr-deref in dw_dp_remove()","id":"CVE-2026-80658"},"products":["Linux"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-28","vendors":["Linux"]},"summary":"A recursive locking bug in the vub300 MMC driver causes a deadlock and system hang when a USB command times out, requiring local access to trigger.","url":"https://insights.sbomify.com/CVE-2026-80659/"}