media: uvcvideo: Remove dangling pointers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e5225c820c057537dc780244760e2e24c7d27366 · < 438bda062b2c40ddd7df23b932e29ffe0a448cac| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: uvcvideo: Remove dangling pointers
When an async control is written, we copy a pointer to the file handle that started the operation. That pointer will be used when the device is done. Which could be anytime in the future.
If the user closes that file descriptor, its structure will be freed, and there will be one dangling pointer per pending async control, that the driver will try to use.
Clean all the dangling pointers during release().
To avoid adding a performance penalty in the most common case (no async operation), a counter has been introduced with some logic to make sure that it is properly handled.
From the CVE record · Linux
The Linux kernel’s uvcvideo driver can retain a pointer to a file handle while an asynchronous control operation is pending. If a local user closes that file descriptor before the operation completes, the driver may use the freed handle.
Anyone running Linux kernels with the affected uvcvideo driver should check their kernel version against the vendor advisory; affected versions were not provided.