https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 22:02:45 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-89741 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-89741 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/euvd-2026-367711 EUVD-2026-367711 https://cve.radiocsirt.org/vuln/euvd-2026-367711 https://cve.radiocsirt.org/vuln/fkie_cve-2026-89741 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Revert &#34;media: v4l2-dev: fix error handling in __video_register_device()&#34;</p> <p>This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.</p> <p>The intentions of that patch were good, but it doesn&#39;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&#39;ll have a small memory leak. Which is a lot more robust.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Revert &#34;media: v4l2-dev: fix error handling in __video_register_device()&#34;</p> <p>This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.</p> <p>The intentions of that patch were good, but it doesn&#39;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&#39;ll have a small memory leak. Which is a lot more robust.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-89741 https://cve.radiocsirt.org/vuln/ghsa-x4c4-qfr2-c3vv <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Revert &#34;media: v4l2-dev: fix error handling in __video_register_device()&#34;</p> <p>This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.</p> <p>The intentions of that patch were good, but it doesn&#39;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&#39;ll have a small memory leak. Which is a lot more robust.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Revert &#34;media: v4l2-dev: fix error handling in __video_register_device()&#34;</p> <p>This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.</p> <p>The intentions of that patch were good, but it doesn&#39;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&#39;ll have a small memory leak. Which is a lot more robust.</p> https://cve.radiocsirt.org/vuln/ghsa-x4c4-qfr2-c3vv https://cve.radiocsirt.org/vuln/msrc_cve-2026-89741 msrc_CVE-2026-89741 https://cve.radiocsirt.org/vuln/msrc_cve-2026-89741 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1 <p>kernel-devel-7.2.7-1.1 on GA media</p> <p>kernel-devel-7.2.7-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89741 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 189 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Revert &#34;media: v4l2-dev: fix error handling in __video_register_device()&#34; This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a. The intentions of that patch were good, but it doesn&#39;t work. The idea is that if device_register fails, you have to do a put_device to let the ref counter release resources. 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. But the put_device() will already have freed the struct, so you end up in a double-free scenario. 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. That is a massive job, and it is very unlikely that device_register will fail. So rather than ending up in a double-free scenario, just revert this patch, and in that case we&#39;ll have a small memory leak. Which is a lot more robust.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 189 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Revert &#34;media: v4l2-dev: fix error handling in __video_register_device()&#34; This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a. The intentions of that patch were good, but it doesn&#39;t work. The idea is that if device_register fails, you have to do a put_device to let the ref counter release resources. 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. But the put_device() will already have freed the struct, so you end up in a double-free scenario. 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. That is a massive job, and it is very unlikely that device_register will fail. So rather than ending up in a double-free scenario, just revert this patch, and in that case we&#39;ll have a small memory leak. Which is a lot more robust.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89741 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321