CVE-2026-89871

media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.185cebaac609744414463d1ecc28fdecd26c1b9bc1
Vendor states this is fixed in 0e7f2cd72a4f9268ee09a13b13f3339e7cc71557 (fixed)
Vendor states this is fixed in 0fac63cac6689588da530764ccb6ba55ee8e4d8b (fixed)
Vendor states this is fixed in 3d1b10d81fe54852ed953f4129577b733bbd6907 (fixed)
Vendor states this is fixed in 52fd9d80c0cea7bf09e7ee36cad316e5c39b7fe6 (fixed)
Vendor states this is fixed in 5c35d380bea60503c4fe0986fe1de6a3263282b3 (fixed)
Vendor states this is fixed in 76e379754ba618989f6215be608d5c04774a611d (fixed)
Vendor states this is fixed in 968c5213e34c48d35febdfd09cf3dc58ad039140 (fixed)
Vendor states this is fixed in db0f4531aa55cfb0171684ebfffe3ff04b79d5a8 (fixed)
Vendor states this is fixed in 4.18 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card