<?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 23:29:29 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72221</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72221</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-72221</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1164 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1164</link>
      <description>certfr-2026-avi-1164</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1164</guid>
    </item>
    <item>
      <title>EUVD-2026-353977</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353977</link>
      <description>EUVD-2026-353977</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353977</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72221</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72221</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sunrpc: wait for in-flight TLS handshake callback when cancel loses race&lt;/p&gt;
&lt;p&gt;When wait_for_completion_interruptible_timeout() in
svc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and
tls_handshake_cancel() then returns false, handshake_complete() has
won the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and
is about to invoke svc_tcp_handshake_done(), but the callback&amp;#39;s
side effects on xpt_flags and on svsk-&amp;gt;sk_handshake_done have not
yet committed.&lt;/p&gt;
&lt;p&gt;The current code reads xpt_flags immediately to decide whether the
session succeeded. Two races result.&lt;/p&gt;
&lt;p&gt;If the callback has executed set_bit(XPT_TLS_SESSION) but not yet
clear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session,
enqueues the transport, and returns. svc_xprt_received() then
clears XPT_BUSY, a worker thread picks the transport up, the
dispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set,
and xpo_handshake is invoked a second time. That svc_tcp_handshake()
calls init_completion(&amp;amp;svsk-&amp;gt;sk_handshake_done) while the original
callback concurrently calls complete_all() on it, corrupting the
embedded swait_queue.&lt;/p&gt;
&lt;p&gt;If the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet
entered svc_tcp_handshake_done(), svc_tcp_handshake() reads
XPT_TLS_SESSION as clear and tears the connection down even though
the handshake is about to succeed.&lt;/p&gt;
&lt;p&gt;Wait for the callback to commit before inspecting xpt_flags. The
completion is gua…&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: wait for in-flight TLS handshake callback when cancel loses race&lt;/p&gt;
&lt;p&gt;When wait_for_completion_interruptible_timeout() in
svc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and
tls_handshake_cancel() then returns false, handshake_complete() has
won the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and
is about to invoke svc_tcp_handshake_done(), but the callback&amp;#39;s
side effects on xpt_flags and on svsk-&amp;gt;sk_handshake_done have not
yet committed.&lt;/p&gt;
&lt;p&gt;The current code reads xpt_flags immediately to decide whether the
session succeeded. Two races result.&lt;/p&gt;
&lt;p&gt;If the callback has executed set_bit(XPT_TLS_SESSION) but not yet
clear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session,
enqueues the transport, and returns. svc_xprt_received() then
clears XPT_BUSY, a worker thread picks the transport up, the
dispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set,
and xpo_handshake is invoked a second time. That svc_tcp_handshake()
calls init_completion(&amp;amp;svsk-&amp;gt;sk_handshake_done) while the original
callback concurrently calls complete_all() on it, corrupting the
embedded swait_queue.&lt;/p&gt;
&lt;p&gt;If the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet
entered svc_tcp_handshake_done(), svc_tcp_handshake() reads
XPT_TLS_SESSION as clear and tears the connection down even though
the handshake is about to succeed.&lt;/p&gt;
&lt;p&gt;Wait for the callback to commit before inspecting xpt_flags. The
completion is gua…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72221</guid>
    </item>
    <item>
      <title>GHSA-5gf3-c25p-fm95</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5gf3-c25p-fm95</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sunrpc: wait for in-flight TLS handshake callback when cancel loses race&lt;/p&gt;
&lt;p&gt;When wait_for_completion_interruptible_timeout() in
svc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and
tls_handshake_cancel() then returns false, handshake_complete() has
won the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and
is about to invoke svc_tcp_handshake_done(), but the callback&amp;#39;s
side effects on xpt_flags and on svsk-&amp;gt;sk_handshake_done have not
yet committed.&lt;/p&gt;
&lt;p&gt;The current code reads xpt_flags immediately to decide whether the
session succeeded. Two races result.&lt;/p&gt;
&lt;p&gt;If the callback has executed set_bit(XPT_TLS_SESSION) but not yet
clear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session,
enqueues the transport, and returns. svc_xprt_received() then
clears XPT_BUSY, a worker thread picks the transport up, the
dispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set,
and xpo_handshake is invoked a second time. That svc_tcp_handshake()
calls init_completion(&amp;amp;svsk-&amp;gt;sk_handshake_done) while the original
callback concurrently calls complete_all() on it, corrupting the
embedded swait_queue.&lt;/p&gt;
&lt;p&gt;If the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet
entered svc_tcp_handshake_done(), svc_tcp_handshake() reads
XPT_TLS_SESSION as clear and tears the connection down even though
the handshake is about to succeed.&lt;/p&gt;
&lt;p&gt;Wait for the callback to commit before inspecting xpt_flags. The
completion is gua…&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: wait for in-flight TLS handshake callback when cancel loses race&lt;/p&gt;
&lt;p&gt;When wait_for_completion_interruptible_timeout() in
svc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and
tls_handshake_cancel() then returns false, handshake_complete() has
won the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and
is about to invoke svc_tcp_handshake_done(), but the callback&amp;#39;s
side effects on xpt_flags and on svsk-&amp;gt;sk_handshake_done have not
yet committed.&lt;/p&gt;
&lt;p&gt;The current code reads xpt_flags immediately to decide whether the
session succeeded. Two races result.&lt;/p&gt;
&lt;p&gt;If the callback has executed set_bit(XPT_TLS_SESSION) but not yet
clear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session,
enqueues the transport, and returns. svc_xprt_received() then
clears XPT_BUSY, a worker thread picks the transport up, the
dispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set,
and xpo_handshake is invoked a second time. That svc_tcp_handshake()
calls init_completion(&amp;amp;svsk-&amp;gt;sk_handshake_done) while the original
callback concurrently calls complete_all() on it, corrupting the
embedded swait_queue.&lt;/p&gt;
&lt;p&gt;If the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet
entered svc_tcp_handshake_done(), svc_tcp_handshake() reads
XPT_TLS_SESSION as clear and tears the connection down even though
the handshake is about to succeed.&lt;/p&gt;
&lt;p&gt;Wait for the callback to commit before inspecting xpt_flags. The
completion is gua…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5gf3-c25p-fm95</guid>
    </item>
    <item>
      <title>OESA-2026-3703 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3703</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: qcom: Fix sc7280 lpass potential buffer overflow&lt;/p&gt;
&lt;p&gt;Case values introduced in commit
5f78e1fb7a3e (&amp;amp;quot;ASoC: qcom: Add driver support for audioreach solution&amp;amp;quot;)
cause out of bounds access in arrays of sc7280 driver data (e.g. in case
of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).&lt;/p&gt;
&lt;p&gt;Redefine LPASS_MAX_PORTS to consider the maximum possible port id for
q6dsp as sc7280 driver utilizes some of those values.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37979)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization&lt;/p&gt;
&lt;p&gt;Syzbot reported shift-out-of-bounds exception on MDIO bus initialization.&lt;/p&gt;
&lt;p&gt;The PHY address should be masked to 5 bits (0-31). Without this
mask, invalid PHY addresses could be used, potentially causing issues
with MDIO bus operations.&lt;/p&gt;
&lt;p&gt;Fix this by masking the PHY address with 0x1f (31 decimal) to ensure
it stays within the valid range.(CVE-2025-38736)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl&lt;/p&gt;
&lt;p&gt;When page reassignment was added to af_alg_pull_tsgl the original
loop wasn&amp;amp;apos;t updated so it may try to reassign one more page than
necessary.&lt;/p&gt;
&lt;p&gt;Add the check to the reassignment so that this does not happen.&lt;/p&gt;
&lt;p&gt;Also u…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: qcom: Fix sc7280 lpass potential buffer overflow&lt;/p&gt;
&lt;p&gt;Case values introduced in commit
5f78e1fb7a3e (&amp;amp;quot;ASoC: qcom: Add driver support for audioreach solution&amp;amp;quot;)
cause out of bounds access in arrays of sc7280 driver data (e.g. in case
of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).&lt;/p&gt;
&lt;p&gt;Redefine LPASS_MAX_PORTS to consider the maximum possible port id for
q6dsp as sc7280 driver utilizes some of those values.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37979)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization&lt;/p&gt;
&lt;p&gt;Syzbot reported shift-out-of-bounds exception on MDIO bus initialization.&lt;/p&gt;
&lt;p&gt;The PHY address should be masked to 5 bits (0-31). Without this
mask, invalid PHY addresses could be used, potentially causing issues
with MDIO bus operations.&lt;/p&gt;
&lt;p&gt;Fix this by masking the PHY address with 0x1f (31 decimal) to ensure
it stays within the valid range.(CVE-2025-38736)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl&lt;/p&gt;
&lt;p&gt;When page reassignment was added to af_alg_pull_tsgl the original
loop wasn&amp;amp;apos;t updated so it may try to reassign one more page than
necessary.&lt;/p&gt;
&lt;p&gt;Add the check to the reassignment so that this does not happen.&lt;/p&gt;
&lt;p&gt;Also u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3703</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-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:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23477-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:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72221</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72221</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sunrpc: wait for in-flight TLS handshake callback when cancel loses race When wait_for_completion_interruptible_timeout() in svc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and tls_handshake_cancel() then returns false, handshake_complete() has won the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and is about to invoke svc_tcp_handshake_done(), but the callback&amp;#39;s side effects on xpt_flags and on svsk-&amp;gt;sk_handshake_done have not yet committed. The current code reads xpt_flags immediately to decide whether the session succeeded. Two races result. If the callback has executed set_bit(XPT_TLS_SESSION) but not yet clear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session, enqueues the transport, and returns. svc_xprt_received() then clears XPT_BUSY, a worker thread picks the transport up, the dispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set, and xpo_handshake is invoked a second time. That svc_tcp_handshake() calls init_completion(&amp;amp;svsk-&amp;gt;sk_handshake_done) while the original callback concurrently calls complete_all() on it, corrupting the embedded swait_queue. If the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet entered svc_tcp_handshake_done(), svc_tcp_handshake() reads XPT_TLS_SESSION as clear and tears the connection down even though the handshake is about to succeed. Wait for the callback to commit before inspecting xpt_flags. The completion is guarantee…&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sunrpc: wait for in-flight TLS handshake callback when cancel loses race When wait_for_completion_interruptible_timeout() in svc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and tls_handshake_cancel() then returns false, handshake_complete() has won the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and is about to invoke svc_tcp_handshake_done(), but the callback&amp;#39;s side effects on xpt_flags and on svsk-&amp;gt;sk_handshake_done have not yet committed. The current code reads xpt_flags immediately to decide whether the session succeeded. Two races result. If the callback has executed set_bit(XPT_TLS_SESSION) but not yet clear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session, enqueues the transport, and returns. svc_xprt_received() then clears XPT_BUSY, a worker thread picks the transport up, the dispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set, and xpo_handshake is invoked a second time. That svc_tcp_handshake() calls init_completion(&amp;amp;svsk-&amp;gt;sk_handshake_done) while the original callback concurrently calls complete_all() on it, corrupting the embedded swait_queue. If the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet entered svc_tcp_handshake_done(), svc_tcp_handshake() reads XPT_TLS_SESSION as clear and tears the connection down even though the handshake is about to succeed. Wait for the callback to commit before inspecting xpt_flags. The completion is guarantee…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72221</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>
