media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5cebaac609744414463d1ecc28fdecd26c1b9bc1 · < 52fd9d80c0cea7bf09e7ee36cad316e5c39b7fe6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure
kthread_run() returns an ERR_PTR on failure, not NULL. When start_streaming() fails, data->kthread_vid_cap is left holding this error pointer instead of being cleared.
This causes two subsequent bugs: 1. A future call to start_streaming() sees a non-NULL kthread_vid_cap and returns 0 (success) immediately, without actually starting the capture thread. 2. A call to stop_streaming() checks 'kthread_vid_cap == NULL' which is false for an error pointer, and proceeds to call kthread_stop() on the error pointer, leading to a kernel crash.
Fix this by resetting kthread_vid_cap to NULL on failure before jumping to the error path.
From the CVE record · Linux
In the Linux kernel's video-i2c component, a failed capture-thread start leaves an error pointer in place. A later stop can crash the kernel, while a later start can report success without starting capture. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the video-i2c component should check their builds; affected versions are not specified.