<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 19:43:11 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-68204</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-68204</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-68204</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069</link>
      <description>certfr-2026-avi-1069</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069</guid>
    </item>
    <item>
      <title>EUVD-2026-356131</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-356131</link>
      <description>EUVD-2026-356131</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-356131</guid>
    </item>
    <item>
      <title>fkie_cve-2026-68204</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-68204</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: vivid: check for vb2_is_busy() when toggling caps&lt;/p&gt;
&lt;p&gt;The vivid_update_format_cap/out() functions must only be called if the
capture/output queue are not busy. But for the controls that select
the CROP/COMPOSE/SCALE capability that is not checked.&lt;/p&gt;
&lt;p&gt;Only when streaming starts will they be set to &amp;#39;grabbed&amp;#39; and it is
impossible to change the control, but between REQBUFS and STREAMON you
are still allowed to set these controls. Since vivid_update_format_cap/out
will change the format, this can cause unexpected results.&lt;/p&gt;
&lt;p&gt;Besides adding these checks, also add a WARN_ON in
vivid_update_format_cap/out() if the queue is busy.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m 90% certain that this is the cause of this syzbot bug:&lt;/p&gt;
&lt;p&gt;https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89&lt;/p&gt;
&lt;p&gt;But since we never have reproducers, it is hard to be certain. In any case,
these checks are needed regardless.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: vivid: check for vb2_is_busy() when toggling caps&lt;/p&gt;
&lt;p&gt;The vivid_update_format_cap/out() functions must only be called if the
capture/output queue are not busy. But for the controls that select
the CROP/COMPOSE/SCALE capability that is not checked.&lt;/p&gt;
&lt;p&gt;Only when streaming starts will they be set to &amp;#39;grabbed&amp;#39; and it is
impossible to change the control, but between REQBUFS and STREAMON you
are still allowed to set these controls. Since vivid_update_format_cap/out
will change the format, this can cause unexpected results.&lt;/p&gt;
&lt;p&gt;Besides adding these checks, also add a WARN_ON in
vivid_update_format_cap/out() if the queue is busy.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m 90% certain that this is the cause of this syzbot bug:&lt;/p&gt;
&lt;p&gt;https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89&lt;/p&gt;
&lt;p&gt;But since we never have reproducers, it is hard to be certain. In any case,
these checks are needed regardless.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-68204</guid>
    </item>
    <item>
      <title>GHSA-5xgr-hpwf-wcm3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5xgr-hpwf-wcm3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: vivid: check for vb2_is_busy() when toggling caps&lt;/p&gt;
&lt;p&gt;The vivid_update_format_cap/out() functions must only be called if the
capture/output queue are not busy. But for the controls that select
the CROP/COMPOSE/SCALE capability that is not checked.&lt;/p&gt;
&lt;p&gt;Only when streaming starts will they be set to &amp;#39;grabbed&amp;#39; and it is
impossible to change the control, but between REQBUFS and STREAMON you
are still allowed to set these controls. Since vivid_update_format_cap/out
will change the format, this can cause unexpected results.&lt;/p&gt;
&lt;p&gt;Besides adding these checks, also add a WARN_ON in
vivid_update_format_cap/out() if the queue is busy.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m 90% certain that this is the cause of this syzbot bug:&lt;/p&gt;
&lt;p&gt;https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89&lt;/p&gt;
&lt;p&gt;But since we never have reproducers, it is hard to be certain. In any case,
these checks are needed regardless.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: vivid: check for vb2_is_busy() when toggling caps&lt;/p&gt;
&lt;p&gt;The vivid_update_format_cap/out() functions must only be called if the
capture/output queue are not busy. But for the controls that select
the CROP/COMPOSE/SCALE capability that is not checked.&lt;/p&gt;
&lt;p&gt;Only when streaming starts will they be set to &amp;#39;grabbed&amp;#39; and it is
impossible to change the control, but between REQBUFS and STREAMON you
are still allowed to set these controls. Since vivid_update_format_cap/out
will change the format, this can cause unexpected results.&lt;/p&gt;
&lt;p&gt;Besides adding these checks, also add a WARN_ON in
vivid_update_format_cap/out() if the queue is busy.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m 90% certain that this is the cause of this syzbot bug:&lt;/p&gt;
&lt;p&gt;https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89&lt;/p&gt;
&lt;p&gt;But since we never have reproducers, it is hard to be certain. In any case,
these checks are needed regardless.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5xgr-hpwf-wcm3</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-68204 — media: vivid: check for vb2_is_busy() when toggling caps</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-68204</link>
      <description>msrc_CVE-2026-68204</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-68204</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23477-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-68204</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68204</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to &amp;#39;grabbed&amp;#39; and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I&amp;#39;m 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to &amp;#39;grabbed&amp;#39; and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I&amp;#39;m 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68204</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2730 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730</guid>
    </item>
  </channel>
</rss>
