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

Status: published. Published: 2026-05-08. Updated: 2026-11-06.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < 7eaeb778bfaa3b2a804f89321c234d59c74569db (affected, git); ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < 0606c24a745bafd1be5d66c48361638cd9cad74b (affected, git); ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < 519051c711dfd239ef6e4b28878efee400a035f9 (affected, git); ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < 0a1fc25deabab4efce64610e3c449485c4fa8f5f (affected, git); ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < fa5ba9867a55e640df0dc79bf0199770fb043f03 (affected, git); ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < 30e87ade8d678c25a8546cf38c0b498fa5cb27d3 (affected, git); ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < 10b5e65959e955a1c8894e0a5413944b5a70204a (affected, git); ≥ c1fa347f20f17f14a4a1575727fa24340e8a9117; < e94eaef11142b01f77bf8ba4d0b59720b7858109 (affected, git). Source: CNA: Linux
- Linux / Linux: 2.6.33 (affected); ≥ 0; < 2.6.33 (unaffected, semver); ≥ 5.10.253; ≤ 5.10.* (unaffected, semver); ≥ 5.15.203; ≤ 5.15.* (unaffected, semver); ≥ 6.1.167; ≤ 6.1.* (unaffected, semver); ≥ 6.6.130; ≤ 6.6.* (unaffected, semver); ≥ 6.12.78; ≤ 6.12.* (unaffected, semver); ≥ 6.18.19; ≤ 6.18.* (unaffected, semver); ≥ 6.19.9; ≤ 6.19.* (unaffected, semver); ≥ 7.0; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.12% as of 2026-11-06; percentile 2.05%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/7eaeb778bfaa3b2a804f89321c234d59c74569db (CNA: Linux)

- https://git.kernel.org/stable/c/0606c24a745bafd1be5d66c48361638cd9cad74b (CNA: Linux)

- https://git.kernel.org/stable/c/519051c711dfd239ef6e4b28878efee400a035f9 (CNA: Linux)

- https://git.kernel.org/stable/c/0a1fc25deabab4efce64610e3c449485c4fa8f5f (CNA: Linux)

- https://git.kernel.org/stable/c/fa5ba9867a55e640df0dc79bf0199770fb043f03 (CNA: Linux)

- https://git.kernel.org/stable/c/30e87ade8d678c25a8546cf38c0b498fa5cb27d3 (CNA: Linux)

- https://git.kernel.org/stable/c/10b5e65959e955a1c8894e0a5413944b5a70204a (CNA: Linux)

- https://git.kernel.org/stable/c/e94eaef11142b01f77bf8ba4d0b59720b7858109 (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-43445; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-43445; retrieved 2026-11-06; source updated Not reported

Revision: 413981875b7c7e5dec48178d2fad99f454c62eb41aff9b755a7027557fb70add

Canonical: https://y2.dev/cve/CVE-2026-43445

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.