Kernel memory corruption via incorrect DMA handle
Published May 6, 2026 · Updated May 6, 2026
Memory corruption in the ec_bhf Ethernet driver in the Linux Kernel allows local users to corrupt kernel memory through a failed open. The ec_bhf_open() cleanup path supplies rx_buf.alloc_len as the DMA handle to dma_free_coherent() instead of the allocation's rx_buf.alloc_phys handle. The path is reached only after receive-buffer initialization fails; public sources do not identify a reliable trigger or a more specific post-corruption outcome.
Summary
What happened
Memory corruption in the ec_bhf Ethernet driver in the Linux Kernel allows local users to corrupt kernel memory through a failed open. The ec_bhf_open() cleanup path supplies rx_buf.alloc_len as the DMA handle to dma_free_coherent() instead of the allocation's rx_buf.alloc_phys handle. The path is reached only after receive-buffer initialization fails; public sources do not identify a reliable trigger or a more specific post-corruption outcome.
The record
- CVE
- CVE-2026-43283
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.15
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <0f589ee54fd6d76d3f75e745f7f12c64cbd749e5
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <1b1371cd4032ae859838ebc74215f569987bb197
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <1b1d3c5d58a80a19d017a409aa2308162bab5bbf
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <1e300c33ef3cc544c2b9c693778fe9490cfe9184
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <7e54ff938bebb173822b4c38b33fc164c1cabf92
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <8320727be7ff704e07c87624efc2a4a75f54b3ce
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <accd0599bc8e73b962247c6c6c70ca7aa1f8e8d0
- Affected versionversion=6af55ff52b02d492d45db88df3e461fa51a6f753 <ffe68c3766997d82e9ccaf1cdbd47eba269c4aa2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo