CVE-2025-21954
published 2025-04-01CVE-2025-21954: In the Linux kernel, the following vulnerability has been resolved: netmem: prevent TX of unreadable skbs Currently on stable trees we have support for…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.46%
37.8th percentile
In the Linux kernel, the following vulnerability has been resolved:
netmem: prevent TX of unreadable skbs
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.
Fix this by preventing the xmit of unreadable skbs.
Tested by configuring tc redirect:
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
Before, I see unreadable skbs in the driver's TX path passed to dma
mapping APIs.
After, I don't see unreadable skbs in the driver's TX path passed to dma
mapping APIs.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.12.20-1 (forky) | linux 6.12.20-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 65249feb6b3df9e17bab5911ee56fa7b0971e231 < 454825019d2f0c59e5174ece9e713f45ad80beff | 454825019d2f0c59e5174ece9e713f45ad80beff |
| linux | linux | >= 65249feb6b3df9e17bab5911ee56fa7b0971e231 < 1c17c8ced25c5fbe424c7ad7ea11d33014a986b1 | 1c17c8ced25c5fbe424c7ad7ea11d33014a986b1 |
| linux | linux | >= 65249feb6b3df9e17bab5911ee56fa7b0971e231 < f3600c867c99a2cc8038680ecf211089c50e7971 | f3600c867c99a2cc8038680ecf211089c50e7971 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.12.20-1 | 6.12.20-1 |
| linux | linux_kernel | >= 0 < 6.12.20-1 | 6.12.20-1 |
| linux | linux_kernel | >= 6.12 < 6.12.20 | 6.12.20 |
| linux | linux_kernel | >= 6.13 < 6.13.8 | 6.13.8 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 6.12.19/6.13.7 netmem ip_proto memory leak (Nessus ID 249973 / WID-SEC-2025-0683)
vuldb·2026-07-31·CVSS 5.5
CVE-2025-21954 [MEDIUM] Linux Kernel up to 6.12.19/6.13.7 netmem ip_proto memory leak (Nessus ID 249973 / WID-SEC-2025-0683)
A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.12.19/6.13.7. This affects the function ip_proto of the component netmem. Performing a manipulation results in memory leak.
This vulnerability is reported as CVE-2025-21954. The attacker must have access to the local network to execute the attack. No exploit exists.
It is advisable to upgrade the affected component.
GHSA
GHSA-5mxp-4f79-c8g9: In the Linux kernel, the following vulnerability has been resolved:
netmem: prevent TX of unreadable skbs
Currently on stable trees we have support
ghsa_unreviewed·2025-04-01
CVE-2025-21954 [MEDIUM] CWE-401 GHSA-5mxp-4f79-c8g9: In the Linux kernel, the following vulnerability has been resolved:
netmem: prevent TX of unreadable skbs
Currently on stable trees we have support
In the Linux kernel, the following vulnerability has been resolved:
netmem: prevent TX of unreadable skbs
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.
Fix this by preventing the xmit of unreadable skbs.
Tested by configuring tc redirect:
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
Before, I see unreadable skbs in the driver's TX path passed to dma
mapping APIs.
After, I don't see unreadable skbs in the driver's TX path passed to dma
mapping APIs.
OSV
CVE-2025-21954: In the Linux kernel, the following vulnerability has been resolved: netmem: prevent TX of unreadable skbs Currently on stable trees we have support fo
osv·2025-04-01·CVSS 5.5
CVE-2025-21954 [MEDIUM] CVE-2025-21954: In the Linux kernel, the following vulnerability has been resolved: netmem: prevent TX of unreadable skbs Currently on stable trees we have support fo
In the Linux kernel, the following vulnerability has been resolved: netmem: prevent TX of unreadable skbs 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. Fix this by preventing the xmit of unreadable skbs. Tested by configuring tc redirect: 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 Before, I see unreadable skbs in the driver's TX path passed to dma mapping APIs. After, I don't see unreadable skbs in the driver's TX path passed to dma mapping APIs.
Red Hat
kernel: netmem: prevent TX of unreadable skbs
vendor_redhat·2025-04-01·CVSS 5.5
CVE-2025-21954 [MEDIUM] CWE-1287 kernel: netmem: prevent TX of unreadable skbs
kernel: netmem: prevent TX of unreadable skbs
In the Linux kernel, the following vulnerability has been resolved:
netmem: prevent TX of unreadable skbs
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.
Fix this by preventing the xmit of unreadable skbs.
Tested by configuring tc redirect:
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
Before, I see unreadable skbs in the driver's TX path passed to dma
mapping APIs.
After, I don't see unreadable skbs in the driver's TX
Debian
CVE-2025-21954: linux - In the Linux kernel, the following vulnerability has been resolved: netmem: pre...
vendor_debian·2025·CVSS 5.5
CVE-2025-21954 [MEDIUM] CVE-2025-21954: linux - In the Linux kernel, the following vulnerability has been resolved: netmem: pre...
In the Linux kernel, the following vulnerability has been resolved: netmem: prevent TX of unreadable skbs 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. Fix this by preventing the xmit of unreadable skbs. Tested by configuring tc redirect: 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 Before, I see unreadable skbs in the driver's TX path passed to dma mapping APIs. After, I don't see unreadable skbs in the driver's TX path passed to dma mapping APIs.
Scope: local
No detection rules found.
No public exploits indexed.
2025-04-01
Published