<?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 20:16:46 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72342</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72342</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-72342</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-354033</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354033</link>
      <description>EUVD-2026-354033</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354033</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72342</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72342</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix HV VHCA stats agent registration race&lt;/p&gt;
&lt;p&gt;mlx5e_hv_vhca_stats_create() registers the stats agent through
mlx5_hv_vhca_agent_create(). The helper publishes the agent in
hv_vhca-&amp;gt;agents[type] under agents_lock and immediately schedules an
asynchronous control invalidation on the HV VHCA workqueue before
returning to mlx5e.&lt;/p&gt;
&lt;p&gt;The asynchronous invalidation invokes the control agent&amp;#39;s invalidate
callback, which reads the hypervisor control block and forwards the
command to mlx5e_hv_vhca_stats_control(). That callback may either:&lt;/p&gt;
&lt;p&gt;- call cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_agent.work), or
  - call queue_delayed_work(priv-&amp;gt;wq, &amp;amp;sagent-&amp;gt;work, sagent-&amp;gt;delay).&lt;/p&gt;
&lt;p&gt;However, the delayed_work and priv-&amp;gt;stats_agent.agent are only
initialized after mlx5_hv_vhca_agent_create() returns to mlx5e:&lt;/p&gt;
&lt;p&gt;agent = mlx5_hv_vhca_agent_create(...);   /* publish + invalidate */
    ...
    priv-&amp;gt;stats_agent.agent = agent;          /* too late */
    INIT_DELAYED_WORK(&amp;amp;priv-&amp;gt;stats_agent.work, ...); /* too late */&lt;/p&gt;
&lt;p&gt;If the asynchronous control path runs before the two assignments
above, it can:&lt;/p&gt;
&lt;p&gt;- Operate on an uninitialized delayed_work whose timer.function is
    NULL. queue_delayed_work() calls add_timer() unconditionally, so
    when the timer expires the timer softirq invokes a NULL function
    pointer.
  - Re-initialize the timer later through INIT_DELAYED_WORK() while
    the timer is already enqueued in the timer…&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;net/mlx5e: Fix HV VHCA stats agent registration race&lt;/p&gt;
&lt;p&gt;mlx5e_hv_vhca_stats_create() registers the stats agent through
mlx5_hv_vhca_agent_create(). The helper publishes the agent in
hv_vhca-&amp;gt;agents[type] under agents_lock and immediately schedules an
asynchronous control invalidation on the HV VHCA workqueue before
returning to mlx5e.&lt;/p&gt;
&lt;p&gt;The asynchronous invalidation invokes the control agent&amp;#39;s invalidate
callback, which reads the hypervisor control block and forwards the
command to mlx5e_hv_vhca_stats_control(). That callback may either:&lt;/p&gt;
&lt;p&gt;- call cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_agent.work), or
  - call queue_delayed_work(priv-&amp;gt;wq, &amp;amp;sagent-&amp;gt;work, sagent-&amp;gt;delay).&lt;/p&gt;
&lt;p&gt;However, the delayed_work and priv-&amp;gt;stats_agent.agent are only
initialized after mlx5_hv_vhca_agent_create() returns to mlx5e:&lt;/p&gt;
&lt;p&gt;agent = mlx5_hv_vhca_agent_create(...);   /* publish + invalidate */
    ...
    priv-&amp;gt;stats_agent.agent = agent;          /* too late */
    INIT_DELAYED_WORK(&amp;amp;priv-&amp;gt;stats_agent.work, ...); /* too late */&lt;/p&gt;
&lt;p&gt;If the asynchronous control path runs before the two assignments
above, it can:&lt;/p&gt;
&lt;p&gt;- Operate on an uninitialized delayed_work whose timer.function is
    NULL. queue_delayed_work() calls add_timer() unconditionally, so
    when the timer expires the timer softirq invokes a NULL function
    pointer.
  - Re-initialize the timer later through INIT_DELAYED_WORK() while
    the timer is already enqueued in the timer…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72342</guid>
    </item>
    <item>
      <title>GHSA-q42x-cp58-jpg7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q42x-cp58-jpg7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix HV VHCA stats agent registration race&lt;/p&gt;
&lt;p&gt;mlx5e_hv_vhca_stats_create() registers the stats agent through
mlx5_hv_vhca_agent_create(). The helper publishes the agent in
hv_vhca-&amp;gt;agents[type] under agents_lock and immediately schedules an
asynchronous control invalidation on the HV VHCA workqueue before
returning to mlx5e.&lt;/p&gt;
&lt;p&gt;The asynchronous invalidation invokes the control agent&amp;#39;s invalidate
callback, which reads the hypervisor control block and forwards the
command to mlx5e_hv_vhca_stats_control(). That callback may either:&lt;/p&gt;
&lt;p&gt;- call cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_agent.work), or
  - call queue_delayed_work(priv-&amp;gt;wq, &amp;amp;sagent-&amp;gt;work, sagent-&amp;gt;delay).&lt;/p&gt;
&lt;p&gt;However, the delayed_work and priv-&amp;gt;stats_agent.agent are only
initialized after mlx5_hv_vhca_agent_create() returns to mlx5e:&lt;/p&gt;
&lt;p&gt;agent = mlx5_hv_vhca_agent_create(...);   /* publish + invalidate */
    ...
    priv-&amp;gt;stats_agent.agent = agent;          /* too late */
    INIT_DELAYED_WORK(&amp;amp;priv-&amp;gt;stats_agent.work, ...); /* too late */&lt;/p&gt;
&lt;p&gt;If the asynchronous control path runs before the two assignments
above, it can:&lt;/p&gt;
&lt;p&gt;- Operate on an uninitialized delayed_work whose timer.function is
    NULL. queue_delayed_work() calls add_timer() unconditionally, so
    when the timer expires the timer softirq invokes a NULL function
    pointer.
  - Re-initialize the timer later through INIT_DELAYED_WORK() while
    the timer is already enqueued in the timer…&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;net/mlx5e: Fix HV VHCA stats agent registration race&lt;/p&gt;
&lt;p&gt;mlx5e_hv_vhca_stats_create() registers the stats agent through
mlx5_hv_vhca_agent_create(). The helper publishes the agent in
hv_vhca-&amp;gt;agents[type] under agents_lock and immediately schedules an
asynchronous control invalidation on the HV VHCA workqueue before
returning to mlx5e.&lt;/p&gt;
&lt;p&gt;The asynchronous invalidation invokes the control agent&amp;#39;s invalidate
callback, which reads the hypervisor control block and forwards the
command to mlx5e_hv_vhca_stats_control(). That callback may either:&lt;/p&gt;
&lt;p&gt;- call cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_agent.work), or
  - call queue_delayed_work(priv-&amp;gt;wq, &amp;amp;sagent-&amp;gt;work, sagent-&amp;gt;delay).&lt;/p&gt;
&lt;p&gt;However, the delayed_work and priv-&amp;gt;stats_agent.agent are only
initialized after mlx5_hv_vhca_agent_create() returns to mlx5e:&lt;/p&gt;
&lt;p&gt;agent = mlx5_hv_vhca_agent_create(...);   /* publish + invalidate */
    ...
    priv-&amp;gt;stats_agent.agent = agent;          /* too late */
    INIT_DELAYED_WORK(&amp;amp;priv-&amp;gt;stats_agent.work, ...); /* too late */&lt;/p&gt;
&lt;p&gt;If the asynchronous control path runs before the two assignments
above, it can:&lt;/p&gt;
&lt;p&gt;- Operate on an uninitialized delayed_work whose timer.function is
    NULL. queue_delayed_work() calls add_timer() unconditionally, so
    when the timer expires the timer softirq invokes a NULL function
    pointer.
  - Re-initialize the timer later through INIT_DELAYED_WORK() while
    the timer is already enqueued in the timer…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q42x-cp58-jpg7</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-72342</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72342</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 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix HV VHCA stats agent registration race mlx5e_hv_vhca_stats_create() registers the stats agent through mlx5_hv_vhca_agent_create(). The helper publishes the agent in hv_vhca-&amp;gt;agents[type] under agents_lock and immediately schedules an asynchronous control invalidation on the HV VHCA workqueue before returning to mlx5e. The asynchronous invalidation invokes the control agent&amp;#39;s invalidate callback, which reads the hypervisor control block and forwards the command to mlx5e_hv_vhca_stats_control(). That callback may either:   - call cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_agent.work), or   - call queue_delayed_work(priv-&amp;gt;wq, &amp;amp;sagent-&amp;gt;work, sagent-&amp;gt;delay). However, the delayed_work and priv-&amp;gt;stats_agent.agent are only initialized after mlx5_hv_vhca_agent_create() returns to mlx5e:     agent = mlx5_hv_vhca_agent_create(...);   /* publish + invalidate */     ...     priv-&amp;gt;stats_agent.agent = agent;          /* too late */     INIT_DELAYED_WORK(&amp;amp;priv-&amp;gt;stats_agent.work, ...); /* too late */ If the asynchronous control path runs before the two assignments above, it can:   - Operate on an uninitialized delayed_work whose timer.function is     NULL. queue_delayed_work() calls add_timer() unconditionally, so     when the timer expires the timer softirq invokes a NULL function     pointer.   - Re-initialize the timer later through INIT_DELAYED_WORK() while     the timer is already enqueued in the timer wheel, c…&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 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix HV VHCA stats agent registration race mlx5e_hv_vhca_stats_create() registers the stats agent through mlx5_hv_vhca_agent_create(). The helper publishes the agent in hv_vhca-&amp;gt;agents[type] under agents_lock and immediately schedules an asynchronous control invalidation on the HV VHCA workqueue before returning to mlx5e. The asynchronous invalidation invokes the control agent&amp;#39;s invalidate callback, which reads the hypervisor control block and forwards the command to mlx5e_hv_vhca_stats_control(). That callback may either:   - call cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_agent.work), or   - call queue_delayed_work(priv-&amp;gt;wq, &amp;amp;sagent-&amp;gt;work, sagent-&amp;gt;delay). However, the delayed_work and priv-&amp;gt;stats_agent.agent are only initialized after mlx5_hv_vhca_agent_create() returns to mlx5e:     agent = mlx5_hv_vhca_agent_create(...);   /* publish + invalidate */     ...     priv-&amp;gt;stats_agent.agent = agent;          /* too late */     INIT_DELAYED_WORK(&amp;amp;priv-&amp;gt;stats_agent.work, ...); /* too late */ If the asynchronous control path runs before the two assignments above, it can:   - Operate on an uninitialized delayed_work whose timer.function is     NULL. queue_delayed_work() calls add_timer() unconditionally, so     when the timer expires the timer softirq invokes a NULL function     pointer.   - Re-initialize the timer later through INIT_DELAYED_WORK() while     the timer is already enqueued in the timer wheel, c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72342</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>
