<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T18:04:02.821165+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2025-21954</id>
    <title>CVE-2025-21954 — netmem: prevent TX of unreadable skbs</title>
    <updated>2026-10-06T18:04:02.843761+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>netmem: prevent TX of unreadable skbs</p>
<p>Currently on stable trees we have support for netmem/devmem RX but not
TX. It is not safe to forward/redirect an RX unreadable netmem packet
into the device's TX path, as the device may call dma-mapping APIs on
dma addrs that should not be passed to it.</p>
<p>Fix this by preventing the xmit of unreadable skbs.</p>
<p>Tested by configuring tc redirect:</p>
<p>sudo tc qdisc add dev eth1 ingress
sudo tc filter add dev eth1 ingress protocol ip prio 1 flower ip_proto \
	tcp src_ip 192.168.1.12 action mirred egress redirect dev eth1</p>
<p>Before, I see unreadable skbs in the driver's TX path passed to dma
mapping APIs.</p>
<p>After, I don't see unreadable skbs in the driver's TX path passed to dma
mapping APIs.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-21954"/>
  </entry>
</feed>
