<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T12:38:07.106977+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2024-35981</id>
    <title>CVE-2024-35981 — virtio_net: Do not send RSS key if it is not supported</title>
    <updated>2026-10-04T12:38:07.123941+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>virtio_net: Do not send RSS key if it is not supported</p>
<p>There is a bug when setting the RSS options in virtio_net that can break
the whole machine, getting the kernel into an infinite loop.</p>
<p>Running the following command in any QEMU virtual machine with virtionet
will reproduce this problem:</p>
<p># ethtool -X eth0  hfunc toeplitz</p>
<p>This is how the problem happens:</p>
<p>1) ethtool_set_rxfh() calls virtnet_set_rxfh()</p>
<p>2) virtnet_set_rxfh() calls virtnet_commit_rss_command()</p>
<p>3) virtnet_commit_rss_command() populates 4 entries for the rss
scatter-gather</p>
<p>4) Since the command above does not have a key, then the last
scatter-gatter entry will be zeroed, since rss_key_size == 0.
sg_buf_size = vi-&gt;rss_key_size;</p>
<p>5) This buffer is passed to qemu, but qemu is not happy with a buffer
with zero length, and do the following in virtqueue_map_desc() (QEMU
function):</p>
<p>if (!sz) {
      virtio_error(vdev, "virtio: zero sized buffers are not allowed");</p>
<p>6) virtio_error() (also QEMU function) set the device as broken</p>
<p>vdev-&gt;broken = true;</p>
<p>7) Qemu bails out, and do not repond this crazy kernel.</p>
<p>8) The kernel is waiting for the response to come back (function
virtnet_send_command())</p>
<p>9) The kernel is waiting doing the following :</p>
<p>while (!virtqueue_get_buf(vi-&gt;cvq, &amp;tmp) &amp;&amp;
	     !virtqueue_is_broken(vi-&gt;cvq))
	      cpu_relax();</p>
<p>10) None of the following functions above is true, thus, the kernel
loops here forever. K…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-35981"/>
  </entry>
</feed>
