CVE-2024-58002

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.

Weakness

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.

Affected Software

Potential Mitigations

References

• https://git.kernel.org/stable/c/117f7a2975baa4b7d702d3f4830d5a4ebd0c6d50
• https://git.kernel.org/stable/c/221cd51efe4565501a3dbf04cc011b537dcce7fb
• https://git.kernel.org/stable/c/2a29413ace64627e178fd422dd8a5d95219a2c0b
• https://git.kernel.org/stable/c/438bda062b2c40ddd7df23b932e29ffe0a448cac
• https://git.kernel.org/stable/c/4dbaa738c583a0e947803c69e8996e88cf98d971
• https://git.kernel.org/stable/c/653993f46861f2971e95e9a0e36a34b49dec542c
• https://git.kernel.org/stable/c/9edc7d25f7e49c33a1ce7a5ffadea2222065516c
• https://git.kernel.org/stable/c/ac18d781466252cd35a3e311e0a4b264260fd927
• https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
• https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html