<?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 23:01:40 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01283</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-01283</link>
      <description>bdu:2026-01283</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-01283</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>EUVD-2026-311191</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311191</link>
      <description>EUVD-2026-311191</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311191</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50379</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50379</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix race between quota enable and quota rescan ioctl&lt;/p&gt;
&lt;p&gt;When enabling quotas, at btrfs_quota_enable(), after committing the
transaction, we change fs_info-&amp;gt;quota_root to point to the quota root we
created and set BTRFS_FS_QUOTA_ENABLED at fs_info-&amp;gt;flags. Then we try
to start the qgroup rescan worker, first by initializing it with a call
to qgroup_rescan_init() - however if that fails we end up freeing the
quota root but we leave fs_info-&amp;gt;quota_root still pointing to it, this
can later result in a use-after-free somewhere else.&lt;/p&gt;
&lt;p&gt;We have previously set the flags BTRFS_FS_QUOTA_ENABLED and
BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at
btrfs_quota_enable(), which is possible if someone already called the
quota rescan ioctl, and therefore started the rescan worker.&lt;/p&gt;
&lt;p&gt;So fix this by ignoring an -EINPROGRESS and asserting we can&amp;#39;t get any
other error.&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;btrfs: fix race between quota enable and quota rescan ioctl&lt;/p&gt;
&lt;p&gt;When enabling quotas, at btrfs_quota_enable(), after committing the
transaction, we change fs_info-&amp;gt;quota_root to point to the quota root we
created and set BTRFS_FS_QUOTA_ENABLED at fs_info-&amp;gt;flags. Then we try
to start the qgroup rescan worker, first by initializing it with a call
to qgroup_rescan_init() - however if that fails we end up freeing the
quota root but we leave fs_info-&amp;gt;quota_root still pointing to it, this
can later result in a use-after-free somewhere else.&lt;/p&gt;
&lt;p&gt;We have previously set the flags BTRFS_FS_QUOTA_ENABLED and
BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at
btrfs_quota_enable(), which is possible if someone already called the
quota rescan ioctl, and therefore started the rescan worker.&lt;/p&gt;
&lt;p&gt;So fix this by ignoring an -EINPROGRESS and asserting we can&amp;#39;t get any
other error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50379</guid>
    </item>
    <item>
      <title>GHSA-ffg2-pg2r-fw6w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ffg2-pg2r-fw6w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix race between quota enable and quota rescan ioctl&lt;/p&gt;
&lt;p&gt;When enabling quotas, at btrfs_quota_enable(), after committing the
transaction, we change fs_info-&amp;gt;quota_root to point to the quota root we
created and set BTRFS_FS_QUOTA_ENABLED at fs_info-&amp;gt;flags. Then we try
to start the qgroup rescan worker, first by initializing it with a call
to qgroup_rescan_init() - however if that fails we end up freeing the
quota root but we leave fs_info-&amp;gt;quota_root still pointing to it, this
can later result in a use-after-free somewhere else.&lt;/p&gt;
&lt;p&gt;We have previously set the flags BTRFS_FS_QUOTA_ENABLED and
BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at
btrfs_quota_enable(), which is possible if someone already called the
quota rescan ioctl, and therefore started the rescan worker.&lt;/p&gt;
&lt;p&gt;So fix this by ignoring an -EINPROGRESS and asserting we can&amp;#39;t get any
other error.&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;btrfs: fix race between quota enable and quota rescan ioctl&lt;/p&gt;
&lt;p&gt;When enabling quotas, at btrfs_quota_enable(), after committing the
transaction, we change fs_info-&amp;gt;quota_root to point to the quota root we
created and set BTRFS_FS_QUOTA_ENABLED at fs_info-&amp;gt;flags. Then we try
to start the qgroup rescan worker, first by initializing it with a call
to qgroup_rescan_init() - however if that fails we end up freeing the
quota root but we leave fs_info-&amp;gt;quota_root still pointing to it, this
can later result in a use-after-free somewhere else.&lt;/p&gt;
&lt;p&gt;We have previously set the flags BTRFS_FS_QUOTA_ENABLED and
BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at
btrfs_quota_enable(), which is possible if someone already called the
quota rescan ioctl, and therefore started the rescan worker.&lt;/p&gt;
&lt;p&gt;So fix this by ignoring an -EINPROGRESS and asserting we can&amp;#39;t get any
other error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ffg2-pg2r-fw6w</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03615-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03615-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-2025:03615-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50379</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50379</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota rescan ioctl When enabling quotas, at btrfs_quota_enable(), after committing the transaction, we change fs_info-&amp;gt;quota_root to point to the quota root we created and set BTRFS_FS_QUOTA_ENABLED at fs_info-&amp;gt;flags. Then we try to start the qgroup rescan worker, first by initializing it with a call to qgroup_rescan_init() - however if that fails we end up freeing the quota root but we leave fs_info-&amp;gt;quota_root still pointing to it, this can later result in a use-after-free somewhere else. We have previously set the flags BTRFS_FS_QUOTA_ENABLED and BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at btrfs_quota_enable(), which is possible if someone already called the quota rescan ioctl, and therefore started the rescan worker. So fix this by ignoring an -EINPROGRESS and asserting we can&amp;#39;t get any other error.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota rescan ioctl When enabling quotas, at btrfs_quota_enable(), after committing the transaction, we change fs_info-&amp;gt;quota_root to point to the quota root we created and set BTRFS_FS_QUOTA_ENABLED at fs_info-&amp;gt;flags. Then we try to start the qgroup rescan worker, first by initializing it with a call to qgroup_rescan_init() - however if that fails we end up freeing the quota root but we leave fs_info-&amp;gt;quota_root still pointing to it, this can later result in a use-after-free somewhere else. We have previously set the flags BTRFS_FS_QUOTA_ENABLED and BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at btrfs_quota_enable(), which is possible if someone already called the quota rescan ioctl, and therefore started the rescan worker. So fix this by ignoring an -EINPROGRESS and asserting we can&amp;#39;t get any other error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50379</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2092 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</guid>
    </item>
  </channel>
</rss>
