Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0606c24a745bafd1be5d66c48361638cd9cad74b, 0a1fc25deabab4efce64610e3c449485c4fa8f5f, 10b5e65959e955a1c8894e0a5413944b5a70204a.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0606c24a745bafd1be5d66c48361638cd9cad74b, 0a1fc25deabab4efce64610e3c449485c4fa8f5f, 10b5e65959e955a1c8894e0a5413944b5a70204a or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 8, 2026
Updated
Nov 6, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43445

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.33.1 and later · before 5.10.253
  • linux linux kernel5.11 and later · before 5.15.203
  • linux linux kernel5.16 and later · before 6.1.167
  • linux linux kernel6.2 and later · before 6.6.130
  • linux linux kernel6.7 and later · before 6.12.78
  • linux linux kernel6.13 and later · before 6.18.19
  • linux linux kernel6.19 and later · before 6.19.9
  • linux linux kernel2.6.33
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.33affected
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before 7eaeb778bfaa3b2a804f89321c234d59c74569dbaffected · git
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before 0606c24a745bafd1be5d66c48361638cd9cad74baffected · git
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before 519051c711dfd239ef6e4b28878efee400a035f9affected · git
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before 0a1fc25deabab4efce64610e3c449485c4fa8f5faffected · git
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before fa5ba9867a55e640df0dc79bf0199770fb043f03affected · git
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before 30e87ade8d678c25a8546cf38c0b498fa5cb27d3affected · git
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before 10b5e65959e955a1c8894e0a5413944b5a70204aaffected · git
    • c1fa347f20f17f14a4a1575727fa24340e8a9117 and later · before e94eaef11142b01f77bf8ba4d0b59720b7858109affected · git
    • before 2.6.33not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.10-16.19.10-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43443May 8, 2026 · ASoC: amd: acp-mach-common: Add missing error check for clock acquisition
    22Monitor
  • ← EarlierCVE-2026-43444May 8, 2026 · drm/amdkfd: Unreserve bo if queue update failed
    22Monitor
  • Later →CVE-2026-43446May 8, 2026 · accel/amdxdna: Fix runtime suspend deadlock when there is pending job
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0606c24a745bafd1be5d66c48361638cd9cad74bVendor (CNA)
Linux Linux0a1fc25deabab4efce64610e3c449485c4fa8f5fVendor (CNA)
Linux Linux10b5e65959e955a1c8894e0a5413944b5a70204aVendor (CNA)
Linux Linux30e87ade8d678c25a8546cf38c0b498fa5cb27d3Vendor (CNA)
Linux Linux519051c711dfd239ef6e4b28878efee400a035f9Vendor (CNA)
Linux Linux7eaeb778bfaa3b2a804f89321c234d59c74569dbVendor (CNA)
Linux Linuxe94eaef11142b01f77bf8ba4d0b59720b7858109Vendor (CNA)
Linux Linuxfa5ba9867a55e640df0dc79bf0199770fb043f03Vendor (CNA)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records