{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89732 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89732 is a denial of service vulnerability in Linux, published on 11 Sep 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-89732 and fix it if it is affected.\n\nWhat it is: CVE-2026-89732 is a denial of service vulnerability in Linux, published on 11 Sep 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-89732 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-89732/ (Markdown: https://insights.sbomify.com/CVE-2026-89732/index.md)","id":"CVE-2026-89732","markdown":"https://insights.sbomify.com/CVE-2026-89732/index.md","name":"CVE-2026-89732","record":{"aliases":["AZL-100160","BELL-CVE-2026-89732","DEBIAN-CVE-2026-89732","GHSA-95m6-h3qf-8pc2","UBUNTU-CVE-2026-89732"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB gadget","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel deadlock in the USB gadget functionfs driver by triggering a race condition during endpoint teardown, leading to system denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nusb: gadget: f_fs: Prevent deadlock during ep0 read loop\n\nCurrently, ffs_ep0_read() holds ffs-\u003emutex when it prepares to go to\nsleep waiting for an event. When no setup events are pending, it calls\nwait_event_interruptible_exclusive_locked_irq() with the mutex still\nheld. The wait macro deliberately drops the waitqueue spinlock before\nsleeping but does not drop the mutex.\n\nIf a userspace daemon is polling ep0 via read() and the gadget is\nasynchronously torn down via configfs (e.g., echo \"\" \u003e UDC), a\ndeadlock can occur:\n\n1. The configfs teardown calls functionfs_unbind(), which queues a\n   FUNCTIONFS_UNBIND event.\n2. The daemon wakes up, consumes the event, and drops the mutex.\n3. However, if the daemon loops and immediately issues another read()\n   before exiting, it reacquires ffs-\u003emutex and again goes into an\n   interruptible sleep.\n4. Meanwhile, functionfs_unbind() continues execution and attempts to\n   acquire ffs-\u003emutex to tear down ep0req.\n5. The kernel deadlocks because the configfs thread is stuck in an\n   uninterruptible sleep waiting for the mutex, while the userspace\n   daemon is in an interruptible sleep holding the mutex forever\n   because no more events will arrive.\n\nTo fix this, we drop both the waitqueue spinlock and ffs-\u003emutex before\ngoing to sleep, and use wait_event_interruptible_exclusive() instead.\nUpon waking up, we jump back to the `retry` label to safely reacquire\nthe mutex and re-evaluate the state machine. By not sleeping with\nffs-\u003emutex held, we natively decouple gadget teardowns (which require\nthe mutex) from userspace polling.","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":"usb: gadget: f_fs: Prevent deadlock during ep0 read loop","id":"CVE-2026-89732","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and uvc_function_unbind()","id":"CVE-2026-89733"},"packages":[],"prev":{"headline":"cxl/ras: Fix cxl_rch_get_aer_info() out-of-bounds AER register read","id":"CVE-2026-89731"},"products":["Linux"],"published":"2026-09-11","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-10-19","vendors":["Linux"]},"summary":"A local attacker can cause a kernel deadlock in the USB gadget functionfs driver by triggering a race condition during endpoint teardown, leading to system denial of service.","url":"https://insights.sbomify.com/CVE-2026-89732/"}