<?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>Thu, 15 Oct 2026 11:41:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26698 — hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26698</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove&lt;/p&gt;
&lt;p&gt;In commit ac5047671758 (&amp;#34;hv_netvsc: Disable NAPI before closing the
VMBus channel&amp;#34;), napi_disable was getting called for all channels,
including all subchannels without confirming if they are enabled or not.&lt;/p&gt;
&lt;p&gt;This caused hv_netvsc getting hung at napi_disable, when netvsc_probe()
has finished running but nvdev-&amp;gt;subchan_work has not started yet.
netvsc_subchan_work() -&amp;gt; rndis_set_subchannel() has not created the
sub-channels and because of that netvsc_sc_open() is not running.
netvsc_remove() calls cancel_work_sync(&amp;amp;nvdev-&amp;gt;subchan_work), for which
netvsc_subchan_work did not run.&lt;/p&gt;
&lt;p&gt;netif_napi_add() sets the bit NAPI_STATE_SCHED because it ensures NAPI
cannot be scheduled. Then netvsc_sc_open() -&amp;gt; napi_enable will clear the
NAPIF_STATE_SCHED bit, so it can be scheduled. napi_disable() does the
opposite.&lt;/p&gt;
&lt;p&gt;Now during netvsc_device_remove(), when napi_disable is called for those
subchannels, napi_disable gets stuck on infinite msleep.&lt;/p&gt;
&lt;p&gt;This fix addresses this problem by ensuring that napi_disable() is not
getting called for non-enabled NAPI struct.
But netif_napi_del() is still necessary for these non-enabled NAPI struct
for cleanup purpose.&lt;/p&gt;
&lt;p&gt;Call trace:
[  654.559417] task:modprobe        state:D stack:    0 pid: 2321 ppid:  1091 flags:0x00004002
[  654.568030] Call Trace:
[  654.571221]  &amp;lt;TASK&amp;gt;
[  654.573790]  __schedule+0x2d6/0x960
[  654.57…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove&lt;/p&gt;
&lt;p&gt;In commit ac5047671758 (&amp;#34;hv_netvsc: Disable NAPI before closing the
VMBus channel&amp;#34;), napi_disable was getting called for all channels,
including all subchannels without confirming if they are enabled or not.&lt;/p&gt;
&lt;p&gt;This caused hv_netvsc getting hung at napi_disable, when netvsc_probe()
has finished running but nvdev-&amp;gt;subchan_work has not started yet.
netvsc_subchan_work() -&amp;gt; rndis_set_subchannel() has not created the
sub-channels and because of that netvsc_sc_open() is not running.
netvsc_remove() calls cancel_work_sync(&amp;amp;nvdev-&amp;gt;subchan_work), for which
netvsc_subchan_work did not run.&lt;/p&gt;
&lt;p&gt;netif_napi_add() sets the bit NAPI_STATE_SCHED because it ensures NAPI
cannot be scheduled. Then netvsc_sc_open() -&amp;gt; napi_enable will clear the
NAPIF_STATE_SCHED bit, so it can be scheduled. napi_disable() does the
opposite.&lt;/p&gt;
&lt;p&gt;Now during netvsc_device_remove(), when napi_disable is called for those
subchannels, napi_disable gets stuck on infinite msleep.&lt;/p&gt;
&lt;p&gt;This fix addresses this problem by ensuring that napi_disable() is not
getting called for non-enabled NAPI struct.
But netif_napi_del() is still necessary for these non-enabled NAPI struct
for cleanup purpose.&lt;/p&gt;
&lt;p&gt;Call trace:
[  654.559417] task:modprobe        state:D stack:    0 pid: 2321 ppid:  1091 flags:0x00004002
[  654.568030] Call Trace:
[  654.571221]  &amp;lt;TASK&amp;gt;
[  654.573790]  __schedule+0x2d6/0x960
[  654.57…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26698</guid>
    </item>
    <item>
      <title>USN-6766-1 — linux, linux-azure, linux-azure-5.15, linux-azure-fde, linux-azure-fde-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linu…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-6766-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-azure-5.15, Ubuntu:20.04:LTS: linux-azure-fde-5.15, Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-gkeop-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-azure, Ubuntu:22.04:LTS: linux-azure-fde and 8 more&lt;/p&gt;
&lt;p&gt;It was discovered that the Open vSwitch implementation in the Linux kernel
could overflow its stack during recursive action operations under certain
conditions. A local attacker could use this to cause a denial of service
(system crash). (CVE-2024-1151)&lt;/p&gt;
&lt;p&gt;Sander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida
discovered that the Linux kernel mitigations for the initial Branch History
Injection vulnerability (CVE-2022-0001) were insufficient for Intel
processors. A local attacker could potentially use this to expose sensitive
information. (CVE-2024-2201)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - PowerPC architecture;
  - S390 architecture;
  - Core kernel;
  - Block layer subsystem;
  - Android drivers;
  - Power management core;
  - Bus devices;
  - Hardware random number generator core;
  - Cryptographic API;
  - Device frequency;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - IIO Magnetometer sensors drivers;
  - InfiniBand drivers;
  - Media drivers…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-azure-5.15, Ubuntu:20.04:LTS: linux-azure-fde-5.15, Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-gkeop-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-azure, Ubuntu:22.04:LTS: linux-azure-fde and 8 more&lt;/p&gt;
&lt;p&gt;It was discovered that the Open vSwitch implementation in the Linux kernel
could overflow its stack during recursive action operations under certain
conditions. A local attacker could use this to cause a denial of service
(system crash). (CVE-2024-1151)&lt;/p&gt;
&lt;p&gt;Sander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida
discovered that the Linux kernel mitigations for the initial Branch History
Injection vulnerability (CVE-2022-0001) were insufficient for Intel
processors. A local attacker could potentially use this to expose sensitive
information. (CVE-2024-2201)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - PowerPC architecture;
  - S390 architecture;
  - Core kernel;
  - Block layer subsystem;
  - Android drivers;
  - Power management core;
  - Bus devices;
  - Hardware random number generator core;
  - Cryptographic API;
  - Device frequency;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - IIO Magnetometer sensors drivers;
  - InfiniBand drivers;
  - Media drivers…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-6766-1</guid>
    </item>
  </channel>
</rss>
