Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < db0f4531aa55cfb0171684ebfffe3ff04b79d5a8
    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < 0fac63cac6689588da530764ccb6ba55ee8e4d8b
    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < 5c35d380bea60503c4fe0986fe1de6a3263282b3
    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < 3d1b10d81fe54852ed953f4129577b733bbd6907
    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < 968c5213e34c48d35febdfd09cf3dc58ad039140
    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < 52fd9d80c0cea7bf09e7ee36cad316e5c39b7fe6
    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < 0e7f2cd72a4f9268ee09a13b13f3339e7cc71557
    • affected 5cebaac609744414463d1ecc28fdecd26c1b9bc1 – < 76e379754ba618989f6215be608d5c04774a611d
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89871 badge
[![CVE-2026-89871](https://cveledger.app/badge/CVE-2026-89871.svg)](https://cveledger.app/cve/CVE-2026-89871)

Record last updated .