<?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-09-29T20:51:38.530579+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-2026-97990</id>
    <title>CVE-2026-97990 — vdpa_sim_net: check TX pull result before RX copy</title>
    <updated>2026-09-29T20:51:38.545849+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>vdpa_sim_net: check TX pull result before RX copy</p>
<p>vringh_iov_pull_iotlb() returns a signed byte count.  A failed TX pull is
currently added to the unsigned byte counter and then passed as a size_t
length to receive_filter() and vringh_iov_push_iotlb().  A negative error
can therefore become a large length in the RX path.</p>
<p>Handle non-positive pull results before every length use.  Count the TX
error and complete the consumed TX descriptor with zero bytes.</p>
<p>I found this bug myself, though the patch was written with AI assistance.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-97990"/>
  </entry>
</feed>
