<?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 04:06:47 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53273</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53273</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-53273</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>cnvd-2026-25962</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2026-25962</link>
      <description>cnvd-2026-25962</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2026-25962</guid>
    </item>
    <item>
      <title>EUVD-2026-348226</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348226</link>
      <description>EUVD-2026-348226</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348226</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53273</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53273</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tee: optee: prevent use-after-free when the client exits before the supplicant&lt;/p&gt;
&lt;p&gt;Commit 70b0d6b0a199 (&amp;#34;tee: optee: Fix supplicant wait loop&amp;#34;) made the
client wait as killable so it can be interrupted during shutdown or
after a supplicant crash. This changes the original lifetime expectations:
the client task can now terminate while the supplicant is still processing
its request.&lt;/p&gt;
&lt;p&gt;If the client exits first it removes the request from its queue and
kfree()s it, while the request ID remains in supp-&amp;gt;idr. A subsequent
lookup on the supplicant path then dereferences freed memory, leading to
a use-after-free.&lt;/p&gt;
&lt;p&gt;Serialise access to the request with supp-&amp;gt;mutex:&lt;/p&gt;
&lt;p&gt;* Hold supp-&amp;gt;mutex in optee_supp_recv() and optee_supp_send() while
    looking up and touching the request.
  * Let optee_supp_thrd_req() notice that the client has terminated and
    signal optee_supp_send() accordingly.&lt;/p&gt;
&lt;p&gt;With these changes the request cannot be freed while the supplicant still
has a reference, eliminating the race.&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;tee: optee: prevent use-after-free when the client exits before the supplicant&lt;/p&gt;
&lt;p&gt;Commit 70b0d6b0a199 (&amp;#34;tee: optee: Fix supplicant wait loop&amp;#34;) made the
client wait as killable so it can be interrupted during shutdown or
after a supplicant crash. This changes the original lifetime expectations:
the client task can now terminate while the supplicant is still processing
its request.&lt;/p&gt;
&lt;p&gt;If the client exits first it removes the request from its queue and
kfree()s it, while the request ID remains in supp-&amp;gt;idr. A subsequent
lookup on the supplicant path then dereferences freed memory, leading to
a use-after-free.&lt;/p&gt;
&lt;p&gt;Serialise access to the request with supp-&amp;gt;mutex:&lt;/p&gt;
&lt;p&gt;* Hold supp-&amp;gt;mutex in optee_supp_recv() and optee_supp_send() while
    looking up and touching the request.
  * Let optee_supp_thrd_req() notice that the client has terminated and
    signal optee_supp_send() accordingly.&lt;/p&gt;
&lt;p&gt;With these changes the request cannot be freed while the supplicant still
has a reference, eliminating the race.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53273</guid>
    </item>
    <item>
      <title>GHSA-q972-3fgv-wchc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q972-3fgv-wchc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tee: optee: prevent use-after-free when the client exits before the supplicant&lt;/p&gt;
&lt;p&gt;Commit 70b0d6b0a199 (&amp;#34;tee: optee: Fix supplicant wait loop&amp;#34;) made the
client wait as killable so it can be interrupted during shutdown or
after a supplicant crash. This changes the original lifetime expectations:
the client task can now terminate while the supplicant is still processing
its request.&lt;/p&gt;
&lt;p&gt;If the client exits first it removes the request from its queue and
kfree()s it, while the request ID remains in supp-&amp;gt;idr. A subsequent
lookup on the supplicant path then dereferences freed memory, leading to
a use-after-free.&lt;/p&gt;
&lt;p&gt;Serialise access to the request with supp-&amp;gt;mutex:&lt;/p&gt;
&lt;p&gt;* Hold supp-&amp;gt;mutex in optee_supp_recv() and optee_supp_send() while
    looking up and touching the request.
  * Let optee_supp_thrd_req() notice that the client has terminated and
    signal optee_supp_send() accordingly.&lt;/p&gt;
&lt;p&gt;With these changes the request cannot be freed while the supplicant still
has a reference, eliminating the race.&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;tee: optee: prevent use-after-free when the client exits before the supplicant&lt;/p&gt;
&lt;p&gt;Commit 70b0d6b0a199 (&amp;#34;tee: optee: Fix supplicant wait loop&amp;#34;) made the
client wait as killable so it can be interrupted during shutdown or
after a supplicant crash. This changes the original lifetime expectations:
the client task can now terminate while the supplicant is still processing
its request.&lt;/p&gt;
&lt;p&gt;If the client exits first it removes the request from its queue and
kfree()s it, while the request ID remains in supp-&amp;gt;idr. A subsequent
lookup on the supplicant path then dereferences freed memory, leading to
a use-after-free.&lt;/p&gt;
&lt;p&gt;Serialise access to the request with supp-&amp;gt;mutex:&lt;/p&gt;
&lt;p&gt;* Hold supp-&amp;gt;mutex in optee_supp_recv() and optee_supp_send() while
    looking up and touching the request.
  * Let optee_supp_thrd_req() notice that the client has terminated and
    signal optee_supp_send() accordingly.&lt;/p&gt;
&lt;p&gt;With these changes the request cannot be freed while the supplicant still
has a reference, eliminating the race.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q972-3fgv-wchc</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21555-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53273</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53273</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tee: optee: prevent use-after-free when the client exits before the supplicant Commit 70b0d6b0a199 (&amp;#34;tee: optee: Fix supplicant wait loop&amp;#34;) made the client wait as killable so it can be interrupted during shutdown or after a supplicant crash. This changes the original lifetime expectations: the client task can now terminate while the supplicant is still processing its request. If the client exits first it removes the request from its queue and kfree()s it, while the request ID remains in supp-&amp;gt;idr. A subsequent lookup on the supplicant path then dereferences freed memory, leading to a use-after-free. Serialise access to the request with supp-&amp;gt;mutex:   * Hold supp-&amp;gt;mutex in optee_supp_recv() and optee_supp_send() while     looking up and touching the request.   * Let optee_supp_thrd_req() notice that the client has terminated and     signal optee_supp_send() accordingly. With these changes the request cannot be freed while the supplicant still has a reference, eliminating the race.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tee: optee: prevent use-after-free when the client exits before the supplicant Commit 70b0d6b0a199 (&amp;#34;tee: optee: Fix supplicant wait loop&amp;#34;) made the client wait as killable so it can be interrupted during shutdown or after a supplicant crash. This changes the original lifetime expectations: the client task can now terminate while the supplicant is still processing its request. If the client exits first it removes the request from its queue and kfree()s it, while the request ID remains in supp-&amp;gt;idr. A subsequent lookup on the supplicant path then dereferences freed memory, leading to a use-after-free. Serialise access to the request with supp-&amp;gt;mutex:   * Hold supp-&amp;gt;mutex in optee_supp_recv() and optee_supp_send() while     looking up and touching the request.   * Let optee_supp_thrd_req() notice that the client has terminated and     signal optee_supp_send() accordingly. With these changes the request cannot be freed while the supplicant still has a reference, eliminating the race.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53273</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2077 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</guid>
    </item>
  </channel>
</rss>
