Kernel memory corruption via IOAM6 length wraparound
Published May 8, 2026 · Updated May 8, 2026
Out-of-bounds write in affected Linux Kernel releases allows remote attackers to corrupt kernel memory through crafted IPv6 IOAM trace data. ioam6_fill_trace_data() stores a 256-unit schema contribution in a u8, wrapping it to zero so __ioam6_fill_trace_data() skips space reservation but copies the header and payload. The vulnerable ingress path requires IOAM6 acceptance to be enabled, which Linux disables by default; a successful overwrite can crash the host or alter kernel memory.
Summary
What happened
Out-of-bounds write in affected Linux Kernel releases allows remote attackers to corrupt kernel memory through crafted IPv6 IOAM trace data. ioam6_fill_trace_data() stores a 256-unit schema contribution in a u8, wrapping it to zero so __ioam6_fill_trace_data() skips space reservation but copies the header and payload. The vulnerable ingress path requires IOAM6 acceptance to be enabled, which Linux disables by default; a successful overwrite can crash the host or alter kernel memory.
The record
- CVE
- CVE-2026-43341
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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=5.15
- Affected versionversion=8c6f6fa6772696be0c047a711858084b38763728 <184d2e9db27c0f76226b5cad16fe29510a5d2280
- Affected versionversion=8c6f6fa6772696be0c047a711858084b38763728 <5e67ba9bb531e1ec6599a82a065dea9040b9ce50
- Affected versionversion=8c6f6fa6772696be0c047a711858084b38763728 <77695a69baca9b99d95fad09fc78c2318736604f
- Affected versionversion=8c6f6fa6772696be0c047a711858084b38763728 <d1b041080086e91d3733a5438a8c51ad5d3d8e09
- Affected versionversion=8c6f6fa6772696be0c047a711858084b38763728 <d6e1c9b02d85a4f1f4ba6d68e916d9b610a3ed7d
- Affected versionversion=8c6f6fa6772696be0c047a711858084b38763728 <e96d48b37708d53cbdc47f6f60b0714fc4a5f596
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