cve.bz

CVE-2026-43186 linux linux kernel: Out-of-bounds Write

9.8 criticalEPSS 0.6%Fix available

Critical (9.8) in linux linux kernel. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() On the receive path, __ioam6_fill_trace_data() uses trace->nodelen to decide how much data to write for each node. It trusts this field as-is from the incoming packet, with no consistency check against trace->type (the 24-bit field that tells which data items are present). A crafted packet can set nodelen=0 while setting type bits 0-21, causing the function to write ~100 bytes past the allocated region (into skb_shared_info), which corrupts adjacent heap memory and leads to a kernel panic. Add a shared helper ioam6_trace_compute_nodelen() in ioam6.c to derive the expected nodelen from the type field, and use it: - in ioam6_iptunnel.c (send path, existing validation) to replace the open-coded computation; - in exthdrs.c (receive path, ipv6_hop_ioam) to drop packets whose nodelen is inconsistent with the type field, before any data is written. Per RFC 9197, bits 12-21 are each short (4-octet) fields, so they are included in IOAM6_MASK_SHORT_FIELDS (changed from 0xff100000 to 0xff1ffc00).

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-787 Out-of-bounds Write
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-43186 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-43186?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-43186?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-43186 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.15 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.202
Linux6.16.1.165
Linux6.66.6.128
Linux6.126.12.75
Linux6.186.18.16
Linux6.196.19.6
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.170-1DEBIAN-CVE-2026-43186
Debian13linux6.12.85-1DEBIAN-CVE-2026-43186
Debian14linux6.19.6-1DEBIAN-CVE-2026-43186
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-43186
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-43186
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-43186
Ubuntu22.04:LTSlinux5.15.0-185.195UBUNTU-CVE-2026-43186 USN-8493-1
Ubuntu22.04:LTSlinux-aws5.15.0-1111.118UBUNTU-CVE-2026-43186 USN-8493-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-43186 USN-8492-2
Ubuntu22.04:LTSlinux-azure, linux-azure-fde5.15.0-1116.125UBUNTU-CVE-2026-43186 USN-8493-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-43186 USN-8606-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-43186 USN-8609-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1111.121UBUNTU-CVE-2026-43186 USN-8493-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-43186 USN-8492-2
Ubuntu22.04:LTSlinux-gke5.15.0-1107.113UBUNTU-CVE-2026-43186 USN-8493-1
112 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:10.2rv, perf, rtla and 87 more0:6.12.0-211.44.1.el10_2RHSA-2026:51295
Red Hatenterprise_linux_eus:10.0rv, perf, rtla and 88 more0:6.12.0-55.109.1.el10_0RHSA-2026:77634
AlmaLinux10rv, perf, rtla and 72 more6.12.0-211.44.1.el10_2ALSA-2026:51295
Rocky Linux10kernel0:6.12.0-211.44.1.el10_2RLSA-2026:51295
Alpaquita23linux-lts6.1.167-r0BELL-CVE-2026-43186
Alpaquita25linux-lts6.12.80-r0BELL-CVE-2026-43186
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-43186

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A crafted IPv6 IOAM Pre-allocated Trace option can make the receive path trust an inconsistent nodelen value while type bits request more trace data than the allocated area can hold. This can cause __ioam6_fill_trace_data to write about 100 bytes past the IOAM trace area into adjacent heap memory such as skb_shared_info, leading to kernel memory corruption and panic. For the CVSS the PR:N is used because a packet sender does not need credentials on the victim when IPv6 IOAM processing and a matching namespace are configured. The issue is network reachable under IOAM deployment preconditions only. Impact is at least remote denial of service via kernel crash, and worst case may allow confidentiality or integrity impact because the primitive is a heap out-of-bounds write in a packet receive path.

However, practical attack exposure is limited because no exploit primitive beyond denial of service has been demonstrated. The bug is specific to IPv6 IOAM processing, which is not commonly deployed and is typically disabled by default on most general-purpose servers. Systems that do not enable IOAM processing on the receive path are generally not reachable through this issue.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-211.44.1.el10_2Fixed 2026-08-06RHSA-2026:51295
Red Hat Enterprise Linux 10.0 Extended Update Supportkernel-0:6.12.0-55.109.1.el10_0Fixed 2026-10-08RHSA-2026:77634
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-43186.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON