← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-43083

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-43083

Key Details

CVECVE-2026-43083
CVSS Score / Version
9.1 (Critical) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is none; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-125 (Out-of-bounds Read)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

In the Linux kernel, the following vulnerability has been resolved:

net: ioam6: fix OOB and missing lock

When trace->type.bit6 is set:

if (trace->type.bit6) {

...

queue = skb_get_tx_queue(dev, skb);

qdisc = rcu_dereference(queue->qdisc);

This code can lead to an out-of-bounds access of the dev->_tx[] array

when is_input is true. In such a case, the packet is on the RX path and

skb->queue_mapping contains the RX queue index of the ingress device. If

the ingress device has more RX queues than the egress device (dev) has

TX queues, skb_get_queue_mapping(skb) will exceed dev->num_tx_queues.

Add a check to avoid this situation since skb_get_tx_queue() does not

clamp the index. This issue has also revealed that per queue visibility

cannot be accurate and will be replaced later as a new feature.

While at it, add missing lock around qdisc_qstats_qlen_backlog(). The

function __ioam6_fill_trace_data() is called from both softirq and

process contexts, hence the use of spin_lock_bh() here. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-43083
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-43083
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.