CVE-2026-43445
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 6.1.170-1 |
| debian | bullseye | fixed | 5.10.257-1 |
| debian | forky | fixed | 6.19.10-1 |
| debian | sid | fixed | 6.19.10-1 |
| debian | trixie | fixed | 6.12.85-1 |
| linux-kernel | affected | 5.10.253 | |
| linux-kernel | 2.6.33 | affected | |
| linux-kernel | 7.0 | affected | |
References
- https://git.kernel.org/stable/c/0606c24a745bafd1be5d66c48361638cd9cad74b
- https://git.kernel.org/stable/c/0a1fc25deabab4efce64610e3c449485c4fa8f5f
- https://git.kernel.org/stable/c/10b5e65959e955a1c8894e0a5413944b5a70204a
- https://git.kernel.org/stable/c/30e87ade8d678c25a8546cf38c0b498fa5cb27d3
- https://git.kernel.org/stable/c/519051c711dfd239ef6e4b28878efee400a035f9
- https://git.kernel.org/stable/c/7eaeb778bfaa3b2a804f89321c234d59c74569db
- https://git.kernel.org/stable/c/e94eaef11142b01f77bf8ba4d0b59720b7858109
- https://git.kernel.org/stable/c/fa5ba9867a55e640df0dc79bf0199770fb043f03
- https://www.suse.com/security/cve/CVE-2026-43445.html
- https://security-tracker.debian.org/tracker/CVE-2026-43445
CWEs
CWE-401
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.