CVE-2026-43445

e1000/e1000e: Fix leak in DMA error cleanup

MEDIUM
5.5
CVSS Score
Published: May 8, 2026 at 02:22 PM UTC
Updated: June 17, 2026 at 10:49 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: e1000/e1000e: Fix leak in DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented after a successful 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 would leak. In these commits, a faulty while condition caused an infinite loop in dma_error: Commit 03b1320dfcee ("e1000e: remove use of skb_dma_map from e1000e driver") Commit 602c0554d7b0 ("e1000: remove use of skb_dma_map from e1000 driver") Commit c1fa347f20f1 ("e1000/e1000e/igb/igbvf/ixgb/ixgbe: Fix tests of unsigned in *_tx_map()") fixed the infinite loop, but introduced the off-by-one error. This issue may still exist in the igbvf driver, but I did not address it in this patch.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.33 ≤ v < 5.10.2532.6.33 ≤ v < 5.15.2032.6.33 ≤ v < 6.1.1672.6.33 ≤ v < 6.12.782.6.33 ≤ v < 6.18.192.6.33 ≤ v < 6.19.92.6.33 ≤ v < 6.6.1302.6.33 ≤ v < 7.02.6.33.1 ≤ v < 5.10.2535.11 ≤ v < 5.15.2035.16 ≤ v < 6.1.1676.13 ≤ v < 6.18.196.19 ≤ v < 6.19.96.2 ≤ v < 6.6.1306.7 ≤ v < 6.12.782.6.332.6.33 rc62.6.33 rc72.6.33 rc87.0 rc17.0 rc27.0 rc3c1fa347f20f17f14a4a1575727fa24340e8a9117
Vendor states this is fixed in 0606c24a745bafd1be5d66c48361638cd9cad74b (fixed)
Vendor states this is fixed in 0a1fc25deabab4efce64610e3c449485c4fa8f5f (fixed)
Vendor states this is fixed in 10b5e65959e955a1c8894e0a5413944b5a70204a (fixed)
Vendor states this is fixed in 30e87ade8d678c25a8546cf38c0b498fa5cb27d3 (fixed)
Vendor states this is fixed in 519051c711dfd239ef6e4b28878efee400a035f9 (fixed)
Vendor states this is fixed in 7eaeb778bfaa3b2a804f89321c234d59c74569db (fixed)
Vendor states this is fixed in e94eaef11142b01f77bf8ba4d0b59720b7858109 (fixed)
Vendor states this is fixed in fa5ba9867a55e640df0dc79bf0199770fb043f03 (fixed)
Vendor states this is fixed in 2.6.33 (unaffected)
Vendor states this is fixed in 5.10.253 (unaffected)
Vendor states this is fixed in 5.15.203 (unaffected)
Vendor states this is fixed in 6.1.167 (unaffected)
Vendor states this is fixed in 6.12.78 (unaffected)
Vendor states this is fixed in 6.18.19 (unaffected)
Vendor states this is fixed in 6.19.9 (unaffected)
Vendor states this is fixed in 6.6.130 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card