CVE-2026-99469
media: gspca: use vb2_video_unregister_device() on disconnect
What happened?
In the Linux kernel, the following vulnerability has been resolved:
media: gspca: use vb2_video_unregister_device() on disconnect
gspca uses vb2_fop_release(), but gspca_disconnect() only unregisters the video device. If the queue owner closes the device after USB disconnect, vb2_fop_release() releases the queue and invokes gspca_stop_streaming() at that point.
gspca_stream_off() calls subdriver stop callbacks and usb_set_interface() through gspca_dev->dev. By the time the late close runs, the USB core can have freed the usb_device, resulting in a use-after-free. This was observed as a KASAN use-after-free in sd_stopN().
Use vb2_video_unregister_device() so the queue is released and streaming is stopped synchronously during disconnect, while the usb_device is still valid. Since the helper takes the queue lock, which is usb_lock, call it after dropping that lock.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: f729ef5796d82a95758d9edc7eea5879a3a12b25 to < fda9ca3cbee24f6e48c04946a8d2f66565d2d4b2; affected: f729ef5796d82a95758d9edc7eea5879a3a12b25 to < d02a2ed057372d3739ab23d778fc4e04d3330513; affected: f729ef5796d82a95758d9edc7eea5879a3a12b25 to < f6b21af3e32f142bf3e591dbb10044c60472f716; affected: f729ef5796d82a95758d9edc7eea5879a3a12b25 to < 3dbbbc3cafa2de377d9b97af4e35b8b6b5282047 | See vendor advisory |
| LinuxLinux | affected: 5.10; unaffected: 0 to < 5.10; 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-99469
- https://git.kernel.org/stable/c/fda9ca3cbee24f6e48c04946a8d2f66565d2d4b2
- https://git.kernel.org/stable/c/d02a2ed057372d3739ab23d778fc4e04d3330513
- https://git.kernel.org/stable/c/f6b21af3e32f142bf3e591dbb10044c60472f716
- https://git.kernel.org/stable/c/3dbbbc3cafa2de377d9b97af4e35b8b6b5282047