<?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-02T17:38:26.299520+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-74495</id>
    <title>CVE-2026-74495 — igbvf: Fix leak in TX DMA error cleanup</title>
    <updated>2026-10-02T17:38:26.301212+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>igbvf: Fix leak in TX DMA error cleanup</p>
<p>If an error is encountered while mapping TX buffers, the driver should
unmap any buffers already mapped for that skb.</p>
<p>Because count is incremented before each frag mapping, it will always
match the correct number of unmappings needed when dma_error is reached.
Decrementing count before the while loop in dma_error causes an
off-by-one error. If any mapping was successful before an unsuccessful
mapping, exactly one DMA mapping (the head) would leak.</p>
<p>This bug was introduced by a 2010 fix for an endless loop in dma_error.
All other affected drivers have already been fixed.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74495"/>
  </entry>
</feed>
