You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jira VULN-53466
cve CVE-2024-58002
commit-author Ricardo Ribalda <[email protected]>
commit 221cd51
upstream-diff We are missing 54da6a0 - "locking: Introduce __cleanup()
based infrastructure" which is part of an extremely large
changeset. Integrating this is not viable, so we're going to
use the same update as the KERNEL_ORG-LT 5.15 backport:
117f7a2. This replaces the guard with a standard
mutex_lock().
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.
Cc: [email protected]
Fixes: e5225c8 ("media: uvcvideo: Send a control event when a Control Change interrupt arrives")
Reviewed-by: Hans de Goede <[email protected]>
Signed-off-by: Ricardo Ribalda <[email protected]>
Reviewed-by: Laurent Pinchart <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Laurent Pinchart <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
(cherry picked from commit 221cd51)
Signed-off-by: Jonathan Maple <[email protected]>
0 commit comments