<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 07:16:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89871 — media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89871</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure&lt;/p&gt;
&lt;p&gt;kthread_run() returns an ERR_PTR on failure, not NULL.
When start_streaming() fails, data-&amp;gt;kthread_vid_cap is left holding
this error pointer instead of being cleared.&lt;/p&gt;
&lt;p&gt;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 &amp;#39;kthread_vid_cap == NULL&amp;#39; which
   is false for an error pointer, and proceeds to call kthread_stop()
   on the error pointer, leading to a kernel crash.&lt;/p&gt;
&lt;p&gt;Fix this by resetting kthread_vid_cap to NULL on failure before
jumping to the error path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure&lt;/p&gt;
&lt;p&gt;kthread_run() returns an ERR_PTR on failure, not NULL.
When start_streaming() fails, data-&amp;gt;kthread_vid_cap is left holding
this error pointer instead of being cleared.&lt;/p&gt;
&lt;p&gt;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 &amp;#39;kthread_vid_cap == NULL&amp;#39; which
   is false for an error pointer, and proceeds to call kthread_stop()
   on the error pointer, leading to a kernel crash.&lt;/p&gt;
&lt;p&gt;Fix this by resetting kthread_vid_cap to NULL on failure before
jumping to the error path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89871</guid>
    </item>
  </channel>
</rss>
