CVE-2026-43083
Last modified
CVE-2026-43083 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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. EPSS estimates a 0.44% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.17, < 6.18.24 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.14 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-43083?
How severe is CVE-2026-43083?
How do I fix CVE-2026-43083?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-43078In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43079In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4308A weakness has been identified in frdel/agent0ai agent-zero …6.3
- CVE-2026-43080In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43081In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43082In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43084In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43085In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43086In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43087In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43088In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43089In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-43083?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
