Service interruption via stale DMA unmapping
Published May 8, 2026 · Updated May 8, 2026
Improper DMA handling in the Linux Kernel mlx5e driver allows remote attackers to corrupt DMA state and interrupt service during TX recovery. The mlx5e_reset_txqsq_cc_pc() path resets dma_fifo_cc but leaves dma_fifo_pc unchanged, so later completions unmap stale DMA addresses. Reachability requires an active mlx5e send queue and a TX error CQE; the documented result is an IOMMU warning and loss of availability.
Summary
What happened
Improper DMA handling in the Linux Kernel mlx5e driver allows remote attackers to corrupt DMA state and interrupt service during TX recovery. The mlx5e_reset_txqsq_cc_pc() path resets dma_fifo_cc but leaves dma_fifo_pc unchanged, so later completions unmap stale DMA addresses. Reachability requires an active mlx5e send queue and a TX error CQE; the documented result is an IOMMU warning and loss of availability.
The record
- CVE
- CVE-2026-43466
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.17
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <1633111d69053512d099658d4a05fc736fab36b0
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <383b37c04a4827ba60b2bafc1a6cdfd995aed58f
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <6eb68ecc5acc3b319986566c595990b8a7265b23
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <6f41f7812bfa7f991b732a4b45c5c52fc4be3b4e
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <821f85d619f7f22cda7b9d7de89cf5eeb1d11544
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <829efcccfa8f69db5dc8332961295587d218cee6
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <9c5ee9b981ee050b73fdf3f4a2464d6f1a8e10a8
- Affected versionversion=db75373c91b0cfb6a68ad6ae88721e4e21ae6261 <ce1b19dd0684eeb68a124c11085bd611260b36d9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo