<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T02:11:28.515310+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-89741</id>
    <title>CVE-2026-89741 — Revert "media: v4l2-dev: fix error handling in __video_register_device()"</title>
    <updated>2026-10-07T02:11:28.516750+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Revert "media: v4l2-dev: fix error handling in __video_register_device()"</p>
<p>This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.</p>
<p>The intentions of that patch were good, but it doesn't work.</p>
<p>The idea is that if device_register fails, you have to do a put_device
to let the ref counter release resources.</p>
<p>However, the V4L2 API says that if video_register_device() fails, then
you have to call video_device_release(), which kfree()s the video_device
struct.</p>
<p>But the put_device() will already have freed the struct, so you end
up in a double-free scenario.</p>
<p>There is not really a good way of fixing this without breaking
video_register_device() into two parts, one that initializes everything,
and one that does the actual device_register, and then converting all
V4L2 drivers to this new model.</p>
<p>That is a massive job, and it is very unlikely that device_register
will fail.</p>
<p>So rather than ending up in a double-free scenario, just revert this
patch, and in that case we'll have a small memory leak. Which is a lot
more robust.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-89741"/>
  </entry>
</feed>
