CVE-2026-43083
Out-of-Bounds Access in Linux Kernel ioam6
Publication date: 2026-05-06
Last updated on: 2026-05-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux_kernel | linux_kernel | * |
| linux | kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's networking code related to ioam6 tracing. Specifically, when a certain bit (trace->type.bit6) is set, the code attempts to access a transmission queue (TX queue) based on the packet's queue mapping. However, if the packet is on the receive path (RX path) and the ingress device has more RX queues than the egress device has TX queues, the code can access an out-of-bounds index in the dev->_tx[] array. This happens because the function skb_get_tx_queue() does not limit the index to the number of TX queues available, leading to an out-of-bounds access.
Additionally, the vulnerability includes a missing lock around a function that updates queue statistics, which can cause concurrency issues since the function is called from different contexts (softirq and process). The fix involves adding a check to prevent out-of-bounds access and adding the missing lock to ensure thread safety.
How can this vulnerability impact me? :
This vulnerability can lead to out-of-bounds memory access in the Linux kernel networking code. Such out-of-bounds access can cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service by corrupting kernel memory.
Furthermore, the missing lock around queue statistics updates can lead to race conditions, which may cause inaccurate statistics or further instability in the kernel's network stack.