<?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>Fri, 02 Oct 2026 20:53:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89537</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89537</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-89537</guid>
    </item>
    <item>
      <title>EUVD-2026-367294</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367294</link>
      <description>EUVD-2026-367294</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367294</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89537</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89537</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2&lt;/p&gt;
&lt;p&gt;gss_krb5_verify_mic_v2() reads the token ID at ptr[0..1], the flags
byte at ptr[2], and padding at ptr[3..7], then passes
ptr + GSS_KRB5_TOK_HDR_LEN and cksum_len to gss_krb5_mic_build_sg().
None of these accesses check read_token-&amp;gt;len first.&lt;/p&gt;
&lt;p&gt;The minimum safe token size is GSS_KRB5_TOK_HDR_LEN (16) plus
ctx-&amp;gt;krb5e-&amp;gt;cksum_len (12-24, depending on the enctype).  All callers
accept shorter tokens from the wire:&lt;/p&gt;
&lt;p&gt;- gss_unwrap_resp_integ() enforces only an upper bound
   (offset + len &amp;lt;= rcv_buf-&amp;gt;len) before allocating
   mic.data = kmalloc(len) and passing it to gss_verify_mic().
   A malicious NFS server can therefore supply a short checksum
   opaque, producing a small slab allocation that the Kerberos MIC
   verifier reads past.&lt;/p&gt;
&lt;p&gt;- gss_validate() enforces only len &amp;lt;= RPC_MAX_AUTH_SIZE (400)
   before passing the wire-supplied length to
   gss_validate_seqno_mic(), which constructs a mic xdr_netobj
   and calls gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_verify_header() enforces only
   checksum.len &amp;gt;= XDR_UNIT (4 bytes) before dispatching to
   gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_unwrap_integ() checks only that the checksum fits
   in gsd-&amp;gt;gsd_scratch.&lt;/p&gt;
&lt;p&gt;Add a length guard at the top of gss_krb5_verify_mic_v2(), before any
ptr[] access or scatterlist construction.  Well-formed MIC tokens from
gss_krb5_get_mic_v2() already have exactly GSS_KRB5_TOK_HDR…&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: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2&lt;/p&gt;
&lt;p&gt;gss_krb5_verify_mic_v2() reads the token ID at ptr[0..1], the flags
byte at ptr[2], and padding at ptr[3..7], then passes
ptr + GSS_KRB5_TOK_HDR_LEN and cksum_len to gss_krb5_mic_build_sg().
None of these accesses check read_token-&amp;gt;len first.&lt;/p&gt;
&lt;p&gt;The minimum safe token size is GSS_KRB5_TOK_HDR_LEN (16) plus
ctx-&amp;gt;krb5e-&amp;gt;cksum_len (12-24, depending on the enctype).  All callers
accept shorter tokens from the wire:&lt;/p&gt;
&lt;p&gt;- gss_unwrap_resp_integ() enforces only an upper bound
   (offset + len &amp;lt;= rcv_buf-&amp;gt;len) before allocating
   mic.data = kmalloc(len) and passing it to gss_verify_mic().
   A malicious NFS server can therefore supply a short checksum
   opaque, producing a small slab allocation that the Kerberos MIC
   verifier reads past.&lt;/p&gt;
&lt;p&gt;- gss_validate() enforces only len &amp;lt;= RPC_MAX_AUTH_SIZE (400)
   before passing the wire-supplied length to
   gss_validate_seqno_mic(), which constructs a mic xdr_netobj
   and calls gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_verify_header() enforces only
   checksum.len &amp;gt;= XDR_UNIT (4 bytes) before dispatching to
   gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_unwrap_integ() checks only that the checksum fits
   in gsd-&amp;gt;gsd_scratch.&lt;/p&gt;
&lt;p&gt;Add a length guard at the top of gss_krb5_verify_mic_v2(), before any
ptr[] access or scatterlist construction.  Well-formed MIC tokens from
gss_krb5_get_mic_v2() already have exactly GSS_KRB5_TOK_HDR…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89537</guid>
    </item>
    <item>
      <title>GHSA-8jwh-2pr5-8fq7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8jwh-2pr5-8fq7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2&lt;/p&gt;
&lt;p&gt;gss_krb5_verify_mic_v2() reads the token ID at ptr[0..1], the flags
byte at ptr[2], and padding at ptr[3..7], then passes
ptr + GSS_KRB5_TOK_HDR_LEN and cksum_len to gss_krb5_mic_build_sg().
None of these accesses check read_token-&amp;gt;len first.&lt;/p&gt;
&lt;p&gt;The minimum safe token size is GSS_KRB5_TOK_HDR_LEN (16) plus
ctx-&amp;gt;krb5e-&amp;gt;cksum_len (12-24, depending on the enctype).  All callers
accept shorter tokens from the wire:&lt;/p&gt;
&lt;p&gt;- gss_unwrap_resp_integ() enforces only an upper bound
   (offset + len &amp;lt;= rcv_buf-&amp;gt;len) before allocating
   mic.data = kmalloc(len) and passing it to gss_verify_mic().
   A malicious NFS server can therefore supply a short checksum
   opaque, producing a small slab allocation that the Kerberos MIC
   verifier reads past.&lt;/p&gt;
&lt;p&gt;- gss_validate() enforces only len &amp;lt;= RPC_MAX_AUTH_SIZE (400)
   before passing the wire-supplied length to
   gss_validate_seqno_mic(), which constructs a mic xdr_netobj
   and calls gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_verify_header() enforces only
   checksum.len &amp;gt;= XDR_UNIT (4 bytes) before dispatching to
   gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_unwrap_integ() checks only that the checksum fits
   in gsd-&amp;gt;gsd_scratch.&lt;/p&gt;
&lt;p&gt;Add a length guard at the top of gss_krb5_verify_mic_v2(), before any
ptr[] access or scatterlist construction.  Well-formed MIC tokens from
gss_krb5_get_mic_v2() already have exactly GSS_KRB5_TOK_HDR…&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: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2&lt;/p&gt;
&lt;p&gt;gss_krb5_verify_mic_v2() reads the token ID at ptr[0..1], the flags
byte at ptr[2], and padding at ptr[3..7], then passes
ptr + GSS_KRB5_TOK_HDR_LEN and cksum_len to gss_krb5_mic_build_sg().
None of these accesses check read_token-&amp;gt;len first.&lt;/p&gt;
&lt;p&gt;The minimum safe token size is GSS_KRB5_TOK_HDR_LEN (16) plus
ctx-&amp;gt;krb5e-&amp;gt;cksum_len (12-24, depending on the enctype).  All callers
accept shorter tokens from the wire:&lt;/p&gt;
&lt;p&gt;- gss_unwrap_resp_integ() enforces only an upper bound
   (offset + len &amp;lt;= rcv_buf-&amp;gt;len) before allocating
   mic.data = kmalloc(len) and passing it to gss_verify_mic().
   A malicious NFS server can therefore supply a short checksum
   opaque, producing a small slab allocation that the Kerberos MIC
   verifier reads past.&lt;/p&gt;
&lt;p&gt;- gss_validate() enforces only len &amp;lt;= RPC_MAX_AUTH_SIZE (400)
   before passing the wire-supplied length to
   gss_validate_seqno_mic(), which constructs a mic xdr_netobj
   and calls gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_verify_header() enforces only
   checksum.len &amp;gt;= XDR_UNIT (4 bytes) before dispatching to
   gss_verify_mic().&lt;/p&gt;
&lt;p&gt;- svcauth_gss_unwrap_integ() checks only that the checksum fits
   in gsd-&amp;gt;gsd_scratch.&lt;/p&gt;
&lt;p&gt;Add a length guard at the top of gss_krb5_verify_mic_v2(), before any
ptr[] access or scatterlist construction.  Well-formed MIC tokens from
gss_krb5_get_mic_v2() already have exactly GSS_KRB5_TOK_HDR…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8jwh-2pr5-8fq7</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-89537 — SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-89537</link>
      <description>msrc_CVE-2026-89537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-89537</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-89537</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89537</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: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2 gss_krb5_verify_mic_v2() reads the token ID at ptr[0..1], the flags byte at ptr[2], and padding at ptr[3..7], then passes ptr + GSS_KRB5_TOK_HDR_LEN and cksum_len to gss_krb5_mic_build_sg(). None of these accesses check read_token-&amp;gt;len first. The minimum safe token size is GSS_KRB5_TOK_HDR_LEN (16) plus ctx-&amp;gt;krb5e-&amp;gt;cksum_len (12-24, depending on the enctype).  All callers accept shorter tokens from the wire:  - gss_unwrap_resp_integ() enforces only an upper bound    (offset + len &amp;lt;= rcv_buf-&amp;gt;len) before allocating    mic.data = kmalloc(len) and passing it to gss_verify_mic().    A malicious NFS server can therefore supply a short checksum    opaque, producing a small slab allocation that the Kerberos MIC    verifier reads past.  - gss_validate() enforces only len &amp;lt;= RPC_MAX_AUTH_SIZE (400)    before passing the wire-supplied length to    gss_validate_seqno_mic(), which constructs a mic xdr_netobj    and calls gss_verify_mic().  - svcauth_gss_verify_header() enforces only    checksum.len &amp;gt;= XDR_UNIT (4 bytes) before dispatching to    gss_verify_mic().  - svcauth_gss_unwrap_integ() checks only that the checksum fits    in gsd-&amp;gt;gsd_scratch. Add a length guard at the top of gss_krb5_verify_mic_v2(), before any ptr[] access or scatterlist construction.  Well-formed MIC tokens from gss_krb5_get_mic_v2() already have exactly GSS_KRB5_TOK_HDR_LEN + c…&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: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2 gss_krb5_verify_mic_v2() reads the token ID at ptr[0..1], the flags byte at ptr[2], and padding at ptr[3..7], then passes ptr + GSS_KRB5_TOK_HDR_LEN and cksum_len to gss_krb5_mic_build_sg(). None of these accesses check read_token-&amp;gt;len first. The minimum safe token size is GSS_KRB5_TOK_HDR_LEN (16) plus ctx-&amp;gt;krb5e-&amp;gt;cksum_len (12-24, depending on the enctype).  All callers accept shorter tokens from the wire:  - gss_unwrap_resp_integ() enforces only an upper bound    (offset + len &amp;lt;= rcv_buf-&amp;gt;len) before allocating    mic.data = kmalloc(len) and passing it to gss_verify_mic().    A malicious NFS server can therefore supply a short checksum    opaque, producing a small slab allocation that the Kerberos MIC    verifier reads past.  - gss_validate() enforces only len &amp;lt;= RPC_MAX_AUTH_SIZE (400)    before passing the wire-supplied length to    gss_validate_seqno_mic(), which constructs a mic xdr_netobj    and calls gss_verify_mic().  - svcauth_gss_verify_header() enforces only    checksum.len &amp;gt;= XDR_UNIT (4 bytes) before dispatching to    gss_verify_mic().  - svcauth_gss_unwrap_integ() checks only that the checksum fits    in gsd-&amp;gt;gsd_scratch. Add a length guard at the top of gss_krb5_verify_mic_v2(), before any ptr[] access or scatterlist construction.  Well-formed MIC tokens from gss_krb5_get_mic_v2() already have exactly GSS_KRB5_TOK_HDR_LEN + c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89537</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>
