<?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:16:17.692273+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-2025-21788</id>
    <title>CVE-2025-21788 — net: ethernet: ti: am65-cpsw: fix memleak in certain XDP cases</title>
    <updated>2026-09-29T20:16:17.712991+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>net: ethernet: ti: am65-cpsw: fix memleak in certain XDP cases</p>
<p>If the XDP program doesn't result in XDP_PASS then we leak the
memory allocated by am65_cpsw_build_skb().</p>
<p>It is pointless to allocate SKB memory before running the XDP
program as we would be wasting CPU cycles for cases other than XDP_PASS.
Move the SKB allocation after evaluating the XDP program result.</p>
<p>This fixes the memleak. A performance boost is seen for XDP_DROP test.</p>
<p>XDP_DROP test:
Before: 460256 rx/s                  0 err/s
After:  784130 rx/s                  0 err/s</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-21788"/>
  </entry>
</feed>
