CVE-2026-99449
usb: gadget: fix refcount underflow in gadgetfs_bind() error path
What happened?
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: fix refcount underflow in gadgetfs_bind() error path
gadgetfs_bind() calls get_dev() only on the success path, but gadgetfs_unbind() called from the enomem error label unconditionally calls put_dev(). When bind fails (e.g. ENOMEM), put_dev() fires without a matching get_dev(), leaving the refcount unbalanced.
A subsequent close of the ep0 file descriptor calls dev_release() -> put_dev() which hits zero and frees the object; then gadgetfs_kill_sb() calls put_dev(the_device) again on the already-freed pointer, triggering a refcount underflow and use-after-free.
Fix by calling get_dev() at the start of gadgetfs_bind(), before any error path that invokes gadgetfs_unbind(), so the reference is always balanced regardless of whether bind succeeds or fails.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < a28791bdb256abd0f338a9b32a95392907d1c987; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < e7e89759445e97ccb445758c6c8d5caed4eb42f9; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < adb693d0369cd7f08f9424588fdd1f613c22d43b; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < cb3b441f2698455a48e9a023d5f7f4e3fcb94c73; affected: 0 to < 6.12.117; affected: 0 to < 6.18.61; affected: 0 to < 7.3.2 | See vendor advisory |
| LinuxLinux | unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99449
- https://git.kernel.org/stable/c/a28791bdb256abd0f338a9b32a95392907d1c987
- https://git.kernel.org/stable/c/e7e89759445e97ccb445758c6c8d5caed4eb42f9
- https://git.kernel.org/stable/c/adb693d0369cd7f08f9424588fdd1f613c22d43b
- https://git.kernel.org/stable/c/cb3b441f2698455a48e9a023d5f7f4e3fcb94c73