CVE-2026-43186Critical· 9.8▾ MidnightIn 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 f…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.9%
Last analysed / modified upstream
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:
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).
Linux >= 9ee11f0fff205b4b3df9750bff5e94f97c71b6a0 < f4d9d4b8fd839719d564651671e24c62c545c23bLinux >= 9ee11f0fff205b4b3df9750bff5e94f97c71b6a0 < fb3c662fafebc5b9d74417ed1de8759f6bb72143Linux >= 9ee11f0fff205b4b3df9750bff5e94f97c71b6a0 < 632d233cf2e64a46865ae2c064ae3c9df7c8864fLinux >= 9ee11f0fff205b4b3df9750bff5e94f97c71b6a0 < 0591d6509c2ff13f09ea2998434aba0c0472e978Linux >= 9ee11f0fff205b4b3df9750bff5e94f97c71b6a0 < e90346a2f1e8917d5760a44a1f61c44e3b36d96bLinux >= 9ee11f0fff205b4b3df9750bff5e94f97c71b6a0 < ea3632aefc04205436868541638e26f4a74d5637Linux >= 9ee11f0fff205b4b3df9750bff5e94f97c71b6a0 < 6db8b56eed62baacaf37486e83378a72635c04ccLinux 5.15Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets