<?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>Sun, 04 Oct 2026 05:36:22 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12809</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12809</link>
      <description>bdu:2026-12809</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12809</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-43280</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-43280</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-43280</guid>
    </item>
    <item>
      <title>EUVD-2026-347883</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347883</link>
      <description>EUVD-2026-347883</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347883</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43280</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43280</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise&lt;/p&gt;
&lt;p&gt;When user provides a bogus pat_index value through the madvise IOCTL, the
xe_pat_index_get_coh_mode() function performs an array access without
validating bounds. This allows a malicious user to trigger an out-of-bounds
kernel read from the xe-&amp;gt;pat.table array.&lt;/p&gt;
&lt;p&gt;The vulnerability exists because the validation in madvise_args_are_sane()
directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without
first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries).&lt;/p&gt;
&lt;p&gt;Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug
builds, it still performs the unsafe array access in production kernels.&lt;/p&gt;
&lt;p&gt;v2(Matthew Auld)
- Using array_index_nospec() to mitigate spectre attacks when the value
is used&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Put the declarations at the start of the block&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&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;drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise&lt;/p&gt;
&lt;p&gt;When user provides a bogus pat_index value through the madvise IOCTL, the
xe_pat_index_get_coh_mode() function performs an array access without
validating bounds. This allows a malicious user to trigger an out-of-bounds
kernel read from the xe-&amp;gt;pat.table array.&lt;/p&gt;
&lt;p&gt;The vulnerability exists because the validation in madvise_args_are_sane()
directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without
first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries).&lt;/p&gt;
&lt;p&gt;Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug
builds, it still performs the unsafe array access in production kernels.&lt;/p&gt;
&lt;p&gt;v2(Matthew Auld)
- Using array_index_nospec() to mitigate spectre attacks when the value
is used&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Put the declarations at the start of the block&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43280</guid>
    </item>
    <item>
      <title>GHSA-cmxm-m5w5-f84q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cmxm-m5w5-f84q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise&lt;/p&gt;
&lt;p&gt;When user provides a bogus pat_index value through the madvise IOCTL, the
xe_pat_index_get_coh_mode() function performs an array access without
validating bounds. This allows a malicious user to trigger an out-of-bounds
kernel read from the xe-&amp;gt;pat.table array.&lt;/p&gt;
&lt;p&gt;The vulnerability exists because the validation in madvise_args_are_sane()
directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without
first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries).&lt;/p&gt;
&lt;p&gt;Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug
builds, it still performs the unsafe array access in production kernels.&lt;/p&gt;
&lt;p&gt;v2(Matthew Auld)
- Using array_index_nospec() to mitigate spectre attacks when the value
is used&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Put the declarations at the start of the block&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&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;drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise&lt;/p&gt;
&lt;p&gt;When user provides a bogus pat_index value through the madvise IOCTL, the
xe_pat_index_get_coh_mode() function performs an array access without
validating bounds. This allows a malicious user to trigger an out-of-bounds
kernel read from the xe-&amp;gt;pat.table array.&lt;/p&gt;
&lt;p&gt;The vulnerability exists because the validation in madvise_args_are_sane()
directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without
first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries).&lt;/p&gt;
&lt;p&gt;Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug
builds, it still performs the unsafe array access in production kernels.&lt;/p&gt;
&lt;p&gt;v2(Matthew Auld)
- Using array_index_nospec() to mitigate spectre attacks when the value
is used&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Put the declarations at the start of the block&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cmxm-m5w5-f84q</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43280</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43280</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise When user provides a bogus pat_index value through the madvise IOCTL, the xe_pat_index_get_coh_mode() function performs an array access without validating bounds. This allows a malicious user to trigger an out-of-bounds kernel read from the xe-&amp;gt;pat.table array. The vulnerability exists because the validation in madvise_args_are_sane() directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries). Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug builds, it still performs the unsafe array access in production kernels. v2(Matthew Auld) - Using array_index_nospec() to mitigate spectre attacks when the value is used v3(Matthew Auld) - Put the declarations at the start of the block (cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise When user provides a bogus pat_index value through the madvise IOCTL, the xe_pat_index_get_coh_mode() function performs an array access without validating bounds. This allows a malicious user to trigger an out-of-bounds kernel read from the xe-&amp;gt;pat.table array. The vulnerability exists because the validation in madvise_args_are_sane() directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries). Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug builds, it still performs the unsafe array access in production kernels. v2(Matthew Auld) - Using array_index_nospec() to mitigate spectre attacks when the value is used v3(Matthew Auld) - Put the declarations at the start of the block (cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43280</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1405 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405</guid>
    </item>
  </channel>
</rss>
