<?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 13:12:49 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74371</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74371</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-74371</guid>
    </item>
    <item>
      <title>EUVD-2026-367505</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367505</link>
      <description>EUVD-2026-367505</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367505</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74371</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74371</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: fix BPF_PROG_QUERY OOB write and cgroup backward compat&lt;/p&gt;
&lt;p&gt;BPF_PROG_QUERY writes back the &amp;#39;query.revision&amp;#39; field unconditionally to
userspace. If userspace passes a smaller &amp;#39;bpf_attr&amp;#39; structure (e.g. 40
bytes, which was the layout before the addition of &amp;#39;query.revision&amp;#39;),
the kernel performs an out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Fix this by propagating the user-provided attribute size &amp;#39;uattr_size&amp;#39;
down to the cgroup query handlers, and conditionally skipping writing
the revision field to userspace when the provided buffer size is
insufficient.&lt;/p&gt;
&lt;p&gt;query.revision in bpf_mprog_query is structurally identical to the
cgroup case: a late tail field, written unconditionally.&lt;/p&gt;
&lt;p&gt;But the backward-compat hazard is not the same.&lt;/p&gt;
&lt;p&gt;The min-historical-size test is per command, and bpf_mprog_query only
serves attach types that were born with revision in the struct:&lt;/p&gt;
&lt;p&gt;- tcx_prog_query -&amp;gt; BPF_TCX_INGRESS/EGRESS
- netkit_prog_query -&amp;gt; BPF_NETKIT_PRIMARY/PEER&lt;/p&gt;
&lt;p&gt;tcx, netkit, the revision field, and bpf_mprog_query itself all landed in
the same v6.6 merge window (053c8e1f235d added the mprog query API +
revision; tcx in e420bed02507, netkit in 35dfaad7188c). There has never
been a tcx/netkit BPF_PROG_QUERY userspace that doesn&amp;#39;t know about
revision. So for these commands the minimum legitimate struct already
covers offset 56-64 — no old binary can be broken here.&lt;/p&gt;
&lt;p&gt;Contrast with cgroup: BPF_PROG_QUERY on cgroup attach types shipped in
2017; rev…&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;bpf: fix BPF_PROG_QUERY OOB write and cgroup backward compat&lt;/p&gt;
&lt;p&gt;BPF_PROG_QUERY writes back the &amp;#39;query.revision&amp;#39; field unconditionally to
userspace. If userspace passes a smaller &amp;#39;bpf_attr&amp;#39; structure (e.g. 40
bytes, which was the layout before the addition of &amp;#39;query.revision&amp;#39;),
the kernel performs an out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Fix this by propagating the user-provided attribute size &amp;#39;uattr_size&amp;#39;
down to the cgroup query handlers, and conditionally skipping writing
the revision field to userspace when the provided buffer size is
insufficient.&lt;/p&gt;
&lt;p&gt;query.revision in bpf_mprog_query is structurally identical to the
cgroup case: a late tail field, written unconditionally.&lt;/p&gt;
&lt;p&gt;But the backward-compat hazard is not the same.&lt;/p&gt;
&lt;p&gt;The min-historical-size test is per command, and bpf_mprog_query only
serves attach types that were born with revision in the struct:&lt;/p&gt;
&lt;p&gt;- tcx_prog_query -&amp;gt; BPF_TCX_INGRESS/EGRESS
- netkit_prog_query -&amp;gt; BPF_NETKIT_PRIMARY/PEER&lt;/p&gt;
&lt;p&gt;tcx, netkit, the revision field, and bpf_mprog_query itself all landed in
the same v6.6 merge window (053c8e1f235d added the mprog query API +
revision; tcx in e420bed02507, netkit in 35dfaad7188c). There has never
been a tcx/netkit BPF_PROG_QUERY userspace that doesn&amp;#39;t know about
revision. So for these commands the minimum legitimate struct already
covers offset 56-64 — no old binary can be broken here.&lt;/p&gt;
&lt;p&gt;Contrast with cgroup: BPF_PROG_QUERY on cgroup attach types shipped in
2017; rev…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74371</guid>
    </item>
    <item>
      <title>GHSA-wg9f-h9hg-j36p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wg9f-h9hg-j36p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: fix BPF_PROG_QUERY OOB write and cgroup backward compat&lt;/p&gt;
&lt;p&gt;BPF_PROG_QUERY writes back the &amp;#39;query.revision&amp;#39; field unconditionally to
userspace. If userspace passes a smaller &amp;#39;bpf_attr&amp;#39; structure (e.g. 40
bytes, which was the layout before the addition of &amp;#39;query.revision&amp;#39;),
the kernel performs an out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Fix this by propagating the user-provided attribute size &amp;#39;uattr_size&amp;#39;
down to the cgroup query handlers, and conditionally skipping writing
the revision field to userspace when the provided buffer size is
insufficient.&lt;/p&gt;
&lt;p&gt;query.revision in bpf_mprog_query is structurally identical to the
cgroup case: a late tail field, written unconditionally.&lt;/p&gt;
&lt;p&gt;But the backward-compat hazard is not the same.&lt;/p&gt;
&lt;p&gt;The min-historical-size test is per command, and bpf_mprog_query only
serves attach types that were born with revision in the struct:&lt;/p&gt;
&lt;p&gt;- tcx_prog_query -&amp;gt; BPF_TCX_INGRESS/EGRESS
- netkit_prog_query -&amp;gt; BPF_NETKIT_PRIMARY/PEER&lt;/p&gt;
&lt;p&gt;tcx, netkit, the revision field, and bpf_mprog_query itself all landed in
the same v6.6 merge window (053c8e1f235d added the mprog query API +
revision; tcx in e420bed02507, netkit in 35dfaad7188c). There has never
been a tcx/netkit BPF_PROG_QUERY userspace that doesn&amp;#39;t know about
revision. So for these commands the minimum legitimate struct already
covers offset 56-64 — no old binary can be broken here.&lt;/p&gt;
&lt;p&gt;Contrast with cgroup: BPF_PROG_QUERY on cgroup attach types shipped in
2017; rev…&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;bpf: fix BPF_PROG_QUERY OOB write and cgroup backward compat&lt;/p&gt;
&lt;p&gt;BPF_PROG_QUERY writes back the &amp;#39;query.revision&amp;#39; field unconditionally to
userspace. If userspace passes a smaller &amp;#39;bpf_attr&amp;#39; structure (e.g. 40
bytes, which was the layout before the addition of &amp;#39;query.revision&amp;#39;),
the kernel performs an out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Fix this by propagating the user-provided attribute size &amp;#39;uattr_size&amp;#39;
down to the cgroup query handlers, and conditionally skipping writing
the revision field to userspace when the provided buffer size is
insufficient.&lt;/p&gt;
&lt;p&gt;query.revision in bpf_mprog_query is structurally identical to the
cgroup case: a late tail field, written unconditionally.&lt;/p&gt;
&lt;p&gt;But the backward-compat hazard is not the same.&lt;/p&gt;
&lt;p&gt;The min-historical-size test is per command, and bpf_mprog_query only
serves attach types that were born with revision in the struct:&lt;/p&gt;
&lt;p&gt;- tcx_prog_query -&amp;gt; BPF_TCX_INGRESS/EGRESS
- netkit_prog_query -&amp;gt; BPF_NETKIT_PRIMARY/PEER&lt;/p&gt;
&lt;p&gt;tcx, netkit, the revision field, and bpf_mprog_query itself all landed in
the same v6.6 merge window (053c8e1f235d added the mprog query API +
revision; tcx in e420bed02507, netkit in 35dfaad7188c). There has never
been a tcx/netkit BPF_PROG_QUERY userspace that doesn&amp;#39;t know about
revision. So for these commands the minimum legitimate struct already
covers offset 56-64 — no old binary can be broken here.&lt;/p&gt;
&lt;p&gt;Contrast with cgroup: BPF_PROG_QUERY on cgroup attach types shipped in
2017; rev…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wg9f-h9hg-j36p</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74371</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74371</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: fix BPF_PROG_QUERY OOB write and cgroup backward compat BPF_PROG_QUERY writes back the &amp;#39;query.revision&amp;#39; field unconditionally to userspace. If userspace passes a smaller &amp;#39;bpf_attr&amp;#39; structure (e.g. 40 bytes, which was the layout before the addition of &amp;#39;query.revision&amp;#39;), the kernel performs an out-of-bounds write. Fix this by propagating the user-provided attribute size &amp;#39;uattr_size&amp;#39; down to the cgroup query handlers, and conditionally skipping writing the revision field to userspace when the provided buffer size is insufficient. query.revision in bpf_mprog_query is structurally identical to the cgroup case: a late tail field, written unconditionally. But the backward-compat hazard is not the same. The min-historical-size test is per command, and bpf_mprog_query only serves attach types that were born with revision in the struct: - tcx_prog_query -&amp;gt; BPF_TCX_INGRESS/EGRESS - netkit_prog_query -&amp;gt; BPF_NETKIT_PRIMARY/PEER tcx, netkit, the revision field, and bpf_mprog_query itself all landed in the same v6.6 merge window (053c8e1f235d added the mprog query API + revision; tcx in e420bed02507, netkit in 35dfaad7188c). There has never been a tcx/netkit BPF_PROG_QUERY userspace that doesn&amp;#39;t know about revision. So for these commands the minimum legitimate struct already covers offset 56-64 — no old binary can be broken here. Contrast with cgroup: BPF_PROG_QUERY on cgroup attach types shipped in 2017; revision wri…&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: fix BPF_PROG_QUERY OOB write and cgroup backward compat BPF_PROG_QUERY writes back the &amp;#39;query.revision&amp;#39; field unconditionally to userspace. If userspace passes a smaller &amp;#39;bpf_attr&amp;#39; structure (e.g. 40 bytes, which was the layout before the addition of &amp;#39;query.revision&amp;#39;), the kernel performs an out-of-bounds write. Fix this by propagating the user-provided attribute size &amp;#39;uattr_size&amp;#39; down to the cgroup query handlers, and conditionally skipping writing the revision field to userspace when the provided buffer size is insufficient. query.revision in bpf_mprog_query is structurally identical to the cgroup case: a late tail field, written unconditionally. But the backward-compat hazard is not the same. The min-historical-size test is per command, and bpf_mprog_query only serves attach types that were born with revision in the struct: - tcx_prog_query -&amp;gt; BPF_TCX_INGRESS/EGRESS - netkit_prog_query -&amp;gt; BPF_NETKIT_PRIMARY/PEER tcx, netkit, the revision field, and bpf_mprog_query itself all landed in the same v6.6 merge window (053c8e1f235d added the mprog query API + revision; tcx in e420bed02507, netkit in 35dfaad7188c). There has never been a tcx/netkit BPF_PROG_QUERY userspace that doesn&amp;#39;t know about revision. So for these commands the minimum legitimate struct already covers offset 56-64 — no old binary can be broken here. Contrast with cgroup: BPF_PROG_QUERY on cgroup attach types shipped in 2017; revision wri…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74371</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
