<?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 17:06:36 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89541</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89541</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-89541</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-367620</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367620</link>
      <description>EUVD-2026-367620</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367620</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89541</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89541</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;SUNRPC: harden gss_unwrap_resp_priv length checks&lt;/p&gt;
&lt;p&gt;gss_unwrap_resp_priv() validates the RPCSEC_GSS opaque length with&lt;/p&gt;
&lt;p&gt;offset = (u8 *)(p) - (u8 *)head-&amp;gt;iov_base;
    if (offset + opaque_len &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    maj_stat = gss_unwrap(ctx-&amp;gt;gc_gss_ctx, offset,
                          offset + opaque_len, rcv_buf);&lt;/p&gt;
&lt;p&gt;Both operands are u32 and the sum is computed in u32. A reply with
opaque_len near 0xffffffff makes offset + opaque_len wrap to a small
value that is below rcv_buf-&amp;gt;len, so the bound check passes and
gss_unwrap() is called with end &amp;lt; begin. The check also lacks a
lower bound, so any opaque_len in [0, GSS_KRB5_TOK_HDR_LEN) is
accepted and forwarded to gss_krb5_unwrap_v2(), whose pre-decrypt
header reads at ptr+4 and ptr+6 then run past the token.&lt;/p&gt;
&lt;p&gt;A krb5p NFS server returning a crafted RPCSEC_GSS reply can drive
the client into out-of-bounds reads in gss_krb5_unwrap_v2() and the
rotate_left() loop that follows.&lt;/p&gt;
&lt;p&gt;Fix by replacing the single combined check with three guards that
are safe in u32 arithmetic and that enforce the RFC 4121 minimum
outer token length:&lt;/p&gt;
&lt;p&gt;if (offset &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    if (opaque_len &amp;gt; rcv_buf-&amp;gt;len - offset)
            goto unwrap_failed;
    if (opaque_len &amp;lt; GSS_KRB5_TOK_HDR_LEN)
            goto unwrap_failed;&lt;/p&gt;
&lt;p&gt;The first guard makes the subtraction in the second guard
unconditionally safe; offset is der…&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;SUNRPC: harden gss_unwrap_resp_priv length checks&lt;/p&gt;
&lt;p&gt;gss_unwrap_resp_priv() validates the RPCSEC_GSS opaque length with&lt;/p&gt;
&lt;p&gt;offset = (u8 *)(p) - (u8 *)head-&amp;gt;iov_base;
    if (offset + opaque_len &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    maj_stat = gss_unwrap(ctx-&amp;gt;gc_gss_ctx, offset,
                          offset + opaque_len, rcv_buf);&lt;/p&gt;
&lt;p&gt;Both operands are u32 and the sum is computed in u32. A reply with
opaque_len near 0xffffffff makes offset + opaque_len wrap to a small
value that is below rcv_buf-&amp;gt;len, so the bound check passes and
gss_unwrap() is called with end &amp;lt; begin. The check also lacks a
lower bound, so any opaque_len in [0, GSS_KRB5_TOK_HDR_LEN) is
accepted and forwarded to gss_krb5_unwrap_v2(), whose pre-decrypt
header reads at ptr+4 and ptr+6 then run past the token.&lt;/p&gt;
&lt;p&gt;A krb5p NFS server returning a crafted RPCSEC_GSS reply can drive
the client into out-of-bounds reads in gss_krb5_unwrap_v2() and the
rotate_left() loop that follows.&lt;/p&gt;
&lt;p&gt;Fix by replacing the single combined check with three guards that
are safe in u32 arithmetic and that enforce the RFC 4121 minimum
outer token length:&lt;/p&gt;
&lt;p&gt;if (offset &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    if (opaque_len &amp;gt; rcv_buf-&amp;gt;len - offset)
            goto unwrap_failed;
    if (opaque_len &amp;lt; GSS_KRB5_TOK_HDR_LEN)
            goto unwrap_failed;&lt;/p&gt;
&lt;p&gt;The first guard makes the subtraction in the second guard
unconditionally safe; offset is der…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89541</guid>
    </item>
    <item>
      <title>GHSA-8h82-j8r3-jr82</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8h82-j8r3-jr82</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;SUNRPC: harden gss_unwrap_resp_priv length checks&lt;/p&gt;
&lt;p&gt;gss_unwrap_resp_priv() validates the RPCSEC_GSS opaque length with&lt;/p&gt;
&lt;p&gt;offset = (u8 *)(p) - (u8 *)head-&amp;gt;iov_base;
    if (offset + opaque_len &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    maj_stat = gss_unwrap(ctx-&amp;gt;gc_gss_ctx, offset,
                          offset + opaque_len, rcv_buf);&lt;/p&gt;
&lt;p&gt;Both operands are u32 and the sum is computed in u32. A reply with
opaque_len near 0xffffffff makes offset + opaque_len wrap to a small
value that is below rcv_buf-&amp;gt;len, so the bound check passes and
gss_unwrap() is called with end &amp;lt; begin. The check also lacks a
lower bound, so any opaque_len in [0, GSS_KRB5_TOK_HDR_LEN) is
accepted and forwarded to gss_krb5_unwrap_v2(), whose pre-decrypt
header reads at ptr+4 and ptr+6 then run past the token.&lt;/p&gt;
&lt;p&gt;A krb5p NFS server returning a crafted RPCSEC_GSS reply can drive
the client into out-of-bounds reads in gss_krb5_unwrap_v2() and the
rotate_left() loop that follows.&lt;/p&gt;
&lt;p&gt;Fix by replacing the single combined check with three guards that
are safe in u32 arithmetic and that enforce the RFC 4121 minimum
outer token length:&lt;/p&gt;
&lt;p&gt;if (offset &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    if (opaque_len &amp;gt; rcv_buf-&amp;gt;len - offset)
            goto unwrap_failed;
    if (opaque_len &amp;lt; GSS_KRB5_TOK_HDR_LEN)
            goto unwrap_failed;&lt;/p&gt;
&lt;p&gt;The first guard makes the subtraction in the second guard
unconditionally safe; offset is der…&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;SUNRPC: harden gss_unwrap_resp_priv length checks&lt;/p&gt;
&lt;p&gt;gss_unwrap_resp_priv() validates the RPCSEC_GSS opaque length with&lt;/p&gt;
&lt;p&gt;offset = (u8 *)(p) - (u8 *)head-&amp;gt;iov_base;
    if (offset + opaque_len &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    maj_stat = gss_unwrap(ctx-&amp;gt;gc_gss_ctx, offset,
                          offset + opaque_len, rcv_buf);&lt;/p&gt;
&lt;p&gt;Both operands are u32 and the sum is computed in u32. A reply with
opaque_len near 0xffffffff makes offset + opaque_len wrap to a small
value that is below rcv_buf-&amp;gt;len, so the bound check passes and
gss_unwrap() is called with end &amp;lt; begin. The check also lacks a
lower bound, so any opaque_len in [0, GSS_KRB5_TOK_HDR_LEN) is
accepted and forwarded to gss_krb5_unwrap_v2(), whose pre-decrypt
header reads at ptr+4 and ptr+6 then run past the token.&lt;/p&gt;
&lt;p&gt;A krb5p NFS server returning a crafted RPCSEC_GSS reply can drive
the client into out-of-bounds reads in gss_krb5_unwrap_v2() and the
rotate_left() loop that follows.&lt;/p&gt;
&lt;p&gt;Fix by replacing the single combined check with three guards that
are safe in u32 arithmetic and that enforce the RFC 4121 minimum
outer token length:&lt;/p&gt;
&lt;p&gt;if (offset &amp;gt; rcv_buf-&amp;gt;len)
            goto unwrap_failed;
    if (opaque_len &amp;gt; rcv_buf-&amp;gt;len - offset)
            goto unwrap_failed;
    if (opaque_len &amp;lt; GSS_KRB5_TOK_HDR_LEN)
            goto unwrap_failed;&lt;/p&gt;
&lt;p&gt;The first guard makes the subtraction in the second guard
unconditionally safe; offset is der…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8h82-j8r3-jr82</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89541</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89541</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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: SUNRPC: harden gss_unwrap_resp_priv length checks gss_unwrap_resp_priv() validates the RPCSEC_GSS opaque length with     offset = (u8 *)(p) - (u8 *)head-&amp;gt;iov_base;     if (offset + opaque_len &amp;gt; rcv_buf-&amp;gt;len)             goto unwrap_failed;     maj_stat = gss_unwrap(ctx-&amp;gt;gc_gss_ctx, offset,                           offset + opaque_len, rcv_buf); Both operands are u32 and the sum is computed in u32. A reply with opaque_len near 0xffffffff makes offset + opaque_len wrap to a small value that is below rcv_buf-&amp;gt;len, so the bound check passes and gss_unwrap() is called with end &amp;lt; begin. The check also lacks a lower bound, so any opaque_len in [0, GSS_KRB5_TOK_HDR_LEN) is accepted and forwarded to gss_krb5_unwrap_v2(), whose pre-decrypt header reads at ptr+4 and ptr+6 then run past the token. A krb5p NFS server returning a crafted RPCSEC_GSS reply can drive the client into out-of-bounds reads in gss_krb5_unwrap_v2() and the rotate_left() loop that follows. Fix by replacing the single combined check with three guards that are safe in u32 arithmetic and that enforce the RFC 4121 minimum outer token length:     if (offset &amp;gt; rcv_buf-&amp;gt;len)             goto unwrap_failed;     if (opaque_len &amp;gt; rcv_buf-&amp;gt;len - offset)             goto unwrap_failed;     if (opaque_len &amp;lt; GSS_KRB5_TOK_HDR_LEN)             goto unwrap_failed; The first guard makes the subtraction in the second guard unconditionally safe; offset is derived fro…&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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: SUNRPC: harden gss_unwrap_resp_priv length checks gss_unwrap_resp_priv() validates the RPCSEC_GSS opaque length with     offset = (u8 *)(p) - (u8 *)head-&amp;gt;iov_base;     if (offset + opaque_len &amp;gt; rcv_buf-&amp;gt;len)             goto unwrap_failed;     maj_stat = gss_unwrap(ctx-&amp;gt;gc_gss_ctx, offset,                           offset + opaque_len, rcv_buf); Both operands are u32 and the sum is computed in u32. A reply with opaque_len near 0xffffffff makes offset + opaque_len wrap to a small value that is below rcv_buf-&amp;gt;len, so the bound check passes and gss_unwrap() is called with end &amp;lt; begin. The check also lacks a lower bound, so any opaque_len in [0, GSS_KRB5_TOK_HDR_LEN) is accepted and forwarded to gss_krb5_unwrap_v2(), whose pre-decrypt header reads at ptr+4 and ptr+6 then run past the token. A krb5p NFS server returning a crafted RPCSEC_GSS reply can drive the client into out-of-bounds reads in gss_krb5_unwrap_v2() and the rotate_left() loop that follows. Fix by replacing the single combined check with three guards that are safe in u32 arithmetic and that enforce the RFC 4121 minimum outer token length:     if (offset &amp;gt; rcv_buf-&amp;gt;len)             goto unwrap_failed;     if (opaque_len &amp;gt; rcv_buf-&amp;gt;len - offset)             goto unwrap_failed;     if (opaque_len &amp;lt; GSS_KRB5_TOK_HDR_LEN)             goto unwrap_failed; The first guard makes the subtraction in the second guard unconditionally safe; offset is derived fro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89541</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
