CVE-2026-43083

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-06. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Sep 7, 2026
No patch confirmed yet.
generic

net: ioam6: fix OOB and missing lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b30b1675aa2bcf0491fd3830b051df4e08a7c8ca
generic

net: ioam6: fix OOB and missing lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95a1334748c95dd15546056280ade0c4b8dd7b78
generic

net: ioam6: fix OOB and missing lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d1d9ed9b409e0662241e3d245d574a18f643494

Vendor Advisories for CVE-2026-43083(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (129 versions)6.19.14-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 7× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 330 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 16:53 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-23 20:26 UTCEG score recompute
  20. 2026-08-23 20:26 UTCVendor advisory
  21. 2026-08-23 20:26 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 12:59 UTCEG score recompute
  4. 2026-08-17 12:59 UTCVendor advisory
  5. 2026-08-17 12:59 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 09:13 UTCVendor advisory
  8. 2026-08-16 09:13 UTCGHSA enrichment
  9. 2026-08-16 04:56 UTCEG score recompute
  10. 2026-08-16 04:56 UTCVendor advisory
  11. 2026-08-16 04:56 UTCGHSA enrichment
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 22:51 UTCVendor advisory
  15. 2026-08-14 22:51 UTCGHSA enrichment
  16. 2026-08-14 18:59 UTCVendor advisory
  17. 2026-08-14 18:59 UTCGHSA enrichment
  18. 2026-08-14 15:06 UTCVendor advisory
  19. 2026-08-14 15:06 UTCGHSA enrichment
  20. 2026-08-14 11:14 UTCVendor advisory
  21. 2026-08-14 11:14 UTCGHSA enrichment
  22. 2026-08-14 07:22 UTCVendor advisory
  23. 2026-08-14 07:22 UTCGHSA enrichment
  24. 2026-08-14 03:31 UTCEG score recompute
  25. 2026-08-14 03:31 UTCVendor advisory
  26. 2026-08-14 03:31 UTCGHSA enrichment
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 09:59 UTCVendor advisory
  29. 2026-08-13 09:59 UTCGHSA enrichment
  30. 2026-08-13 06:08 UTCVendor advisory
  31. 2026-08-13 06:08 UTCGHSA enrichment
  32. 2026-08-13 01:10 UTCVendor advisory
  33. 2026-08-13 01:10 UTCGHSA enrichment
  34. 2026-08-12 21:19 UTCVendor advisory
  35. 2026-08-12 21:19 UTCGHSA enrichment
  36. 2026-08-12 17:10 UTCEG score recompute
  37. 2026-08-12 17:10 UTCVendor advisory
  38. 2026-08-12 17:10 UTCGHSA enrichment
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-11 23:45 UTCVendor advisory
  41. 2026-08-11 23:45 UTCGHSA enrichment
  42. 2026-08-11 19:53 UTCVendor advisory
  43. 2026-08-11 19:52 UTCGHSA enrichment
  44. 2026-08-11 16:01 UTCEG score recompute
  45. 2026-08-11 16:01 UTCVendor advisory
  46. 2026-08-11 16:01 UTCGHSA enrichment
  47. 2026-08-11 13:43 UTCEPSS rescore
  48. 2026-08-11 09:17 UTCVendor advisory
  49. 2026-08-11 09:17 UTCGHSA enrichment
  50. 2026-08-11 05:25 UTCVendor advisory
  51. 2026-08-11 05:25 UTCGHSA enrichment
  52. 2026-08-11 01:34 UTCEG score recompute
  53. 2026-08-11 01:34 UTCVendor advisory
  54. 2026-08-11 01:34 UTCGHSA enrichment
  55. 2026-08-11 00:00 UTCEPSS rescore
  56. 2026-08-10 13:40 UTCVendor advisory
  57. 2026-08-10 13:40 UTCGHSA enrichment
  58. 2026-08-10 09:39 UTCVendor advisory
  59. 2026-08-10 09:39 UTCGHSA enrichment
  60. 2026-08-10 05:48 UTCVendor advisory
  61. 2026-08-10 05:48 UTCGHSA enrichment
  62. 2026-08-10 01:56 UTCVendor advisory
  63. 2026-08-10 01:56 UTCGHSA enrichment
  64. 2026-08-09 22:05 UTCVendor advisory
  65. 2026-08-09 22:05 UTCGHSA enrichment
  66. 2026-08-09 18:13 UTCVendor advisory
  67. 2026-08-09 18:13 UTCGHSA enrichment
  68. 2026-08-09 14:22 UTCEG score recompute
  69. 2026-08-09 14:22 UTCVendor advisory
  70. 2026-08-09 14:22 UTCGHSA enrichment
  71. 2026-08-09 13:46 UTCEPSS rescore
  72. 2026-08-09 10:30 UTCVendor advisory
  73. 2026-08-09 10:30 UTCGHSA enrichment
  74. 2026-08-09 06:30 UTCVendor advisory
  75. 2026-08-09 06:30 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-43083?
CVE-2026-43083 is a critical vulnerability published on May 6, 2026. 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 = skbgettx_queue(dev, skb); qdisc = rcu_dereference(queue->qdisc); This code can lead to an out-of-bounds access of the dev->_tx[]…
When was CVE-2026-43083 disclosed?
CVE-2026-43083 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43083 actively exploited?
CVE-2026-43083 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.6% of all scored CVEs.
What is the CVSS score of CVE-2026-43083?
CVE-2026-43083 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-43083?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43083, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43083

Explore →

Is Your Infrastructure Affected by CVE-2026-43083?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.