CVE-2026-43083Network attack vector

Memory disclosure via IOAM6 queue-index mismatch

Published May 6, 2026 · Updated May 6, 2026

Out-of-bounds read in the Linux Kernel IOAM6 trace path allows remote attackers to disclose kernel memory or crash hosts via IPv6 traffic. When trace type bit 6 is set on the RX path, __ioam6_fill_trace_data() passes an ingress RX queue index to skb_get_tx_queue() without checking it against the egress device's TX queue count. Exploitation requires IOAM6 tracing and an ingress device with more RX queues than the egress device has TX queues; the invalid dev->_tx[] read can enter trace output or interrupt the host.

CVSS severity9.1
Critical
EPSS probability0.44%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds read in the Linux Kernel IOAM6 trace path allows remote attackers to disclose kernel memory or crash hosts via IPv6 traffic. When trace type bit 6 is set on the RX path, __ioam6_fill_trace_data() passes an ingress RX queue index to skb_get_tx_queue() without checking it against the egress device's TX queue count. Exploitation requires IOAM6 tracing and an ingress device with more RX queues than the egress device has TX queues; the invalid dev->_tx[] read can enter trace output or interrupt the host.

The record

CVE
CVE-2026-43083
Published
May 6, 2026
Updated
May 6, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-125, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 6, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=5.17
  2. Affected versionversion=b63c5478e9cb1d1504eb02d9dac827ad24612b32 <6d1d9ed9b409e0662241e3d245d574a18f643494
  3. Affected versionversion=b63c5478e9cb1d1504eb02d9dac827ad24612b32 <95a1334748c95dd15546056280ade0c4b8dd7b78
  4. Affected versionversion=b63c5478e9cb1d1504eb02d9dac827ad24612b32 <b30b1675aa2bcf0491fd3830b051df4e08a7c8ca

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=5.17; version=b63c5478e9cb1d1504eb02d9dac827ad24612b32 <6d1d9ed9b409e0662241e3d245d574a18f643494; version=b63c5478e9cb1d1504eb02d9dac827ad24612b32 <95a1334748c95dd15546056280ade0c4b8dd7b78; version=b63c5478e9cb1d1504eb02d9dac827ad24612b32 <b30b1675aa2bcf0491fd3830b051df4e08a7c8ca

Published CVSS scores

9.1kernel.orgCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-125Out-of-bounds Read
T1499.004Application or System Exploitation

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