<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T21:52:51.237371+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-80871</id>
    <title>BELL-CVE-2026-80871</title>
    <updated>2026-10-03T21:52:51.243670+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-80871"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-363911</id>
    <title>EUVD-2026-363911</title>
    <updated>2026-10-03T21:52:51.243711+00:00</updated>
    <content>EUVD-2026-363911</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-363911"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80871</id>
    <title>fkie_cve-2026-80871</title>
    <updated>2026-10-03T21:52:51.243727+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>crypto: xilinx-trng - Remove crypto_rng interface</p>
<p>Implementing the crypto_rng interface has no purpose, as it isn't used
in practice.  It's being removed from other drivers too.  Just remove
it.  This leaves hwrng, which is actually used.</p>
<p>Tagging with 'Cc stable' due to the bugs that this removes:</p>
<p>- xtrng_trng_generate() sometimes returned success even when it didn't
    fill in all the bytes.</p>
<p>- It was possible for xtrng_trng_generate() and
    xtrng_hwrng_trng_read() to run concurrently and interfere with each
    other, as the locking code in xtrng_hwrng_trng_read() was broken.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-80871"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qx96-qjpp-7jj8</id>
    <title>GHSA-qx96-qjpp-7jj8</title>
    <updated>2026-10-03T21:52:51.243760+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>crypto: xilinx-trng - Remove crypto_rng interface</p>
<p>Implementing the crypto_rng interface has no purpose, as it isn't used
in practice.  It's being removed from other drivers too.  Just remove
it.  This leaves hwrng, which is actually used.</p>
<p>Tagging with 'Cc stable' due to the bugs that this removes:</p>
<p>- xtrng_trng_generate() sometimes returned success even when it didn't
    fill in all the bytes.</p>
<p>- It was possible for xtrng_trng_generate() and
    xtrng_hwrng_trng_read() to run concurrently and interfere with each
    other, as the locking code in xtrng_hwrng_trng_read() was broken.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qx96-qjpp-7jj8"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80871</id>
    <title>UBUNTU-CVE-2026-80871</title>
    <updated>2026-10-03T21:52:51.243783+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 117 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: crypto: xilinx-trng - Remove crypto_rng interface Implementing the crypto_rng interface has no purpose, as it isn't used in practice.  It's being removed from other drivers too.  Just remove it.  This leaves hwrng, which is actually used. Tagging with 'Cc stable' due to the bugs that this removes:   - xtrng_trng_generate() sometimes returned success even when it didn't     fill in all the bytes.   - It was possible for xtrng_trng_generate() and     xtrng_hwrng_trng_read() to run concurrently and interfere with each     other, as the locking code in xtrng_hwrng_trng_read() was broken.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80871"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211</id>
    <title>WID-SEC-W-2026-3211 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T21:52:51.243914+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211"/>
  </entry>
</feed>
