Kernel memory corruption via undersized AF_XDP frames
Published May 6, 2026 · Updated May 6, 2026
Memory corruption in the Linux Kernel AF_XDP subsystem allows local users to corrupt kernel memory through crafted UMEM registration settings. xdp_umem_reg() validates headroom without reserving the 128-byte minimum frame space and prospective multi-buffer tailroom, so received data can overwrite skb_shared_info at the end of an XSK frame. Low-privileged local access is required; a reachable AF_XDP configuration exposes kernel memory corruption that can compromise confidentiality, integrity, and availability.
Summary
What happened
Memory corruption in the Linux Kernel AF_XDP subsystem allows local users to corrupt kernel memory through crafted UMEM registration settings. xdp_umem_reg() validates headroom without reserving the 128-byte minimum frame space and prospective multi-buffer tailroom, so received data can overwrite skb_shared_info at the end of an XSK frame. Low-privileged local access is required; a reachable AF_XDP configuration exposes kernel memory corruption that can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-43093
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- Unavailable
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=25c9cdef57488578da21d99eb614b97ffcf6e59f
- Affected versionversion=5.7
- Affected versionversion=98d3c852e63b49129515dd18c875999efaf8530a
- Affected versionversion=99e3a236dd43d06c65af0a2ef9cb44306aef6e02 <0ec4d3f6e6934deb843b561ae048cd17218e5ad1
- Affected versionversion=99e3a236dd43d06c65af0a2ef9cb44306aef6e02 <6523bc1b40e69301f24c14338b762af4739d6d39
- Affected versionversion=99e3a236dd43d06c65af0a2ef9cb44306aef6e02 <9ea6ba4f3195dcba6e8b3e7b2e748593b7cafb12
- Affected versionversion=99e3a236dd43d06c65af0a2ef9cb44306aef6e02 <a03975beb9f6af0d8ac051e30b2abeabe618414f
- Affected versionversion=99e3a236dd43d06c65af0a2ef9cb44306aef6e02 <a315e022a72d95ef5f1d4e58e903cb492b0ad931
- Affected versionversion=ad8fb61c184fe0f8d1e0b5b954d010fb9f94a6ee
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