Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl()

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0bdaf54d3aaddfe8df29371260fa8d4939b4fd6f, 2dbfb003bbf3fc0e94f07efefab0ebcf83029a2a, 4082f9984a694829153115d28c956a3534f52f29.

Low priority for now. Upgrade to Linux Linux 0bdaf54d3aaddfe8df29371260fa8d4939b4fd6f, 2dbfb003bbf3fc0e94f07efefab0ebcf83029a2a, 4082f9984a694829153115d28c956a3534f52f29 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ipv6: avoid overflows in ip6_datagram_send_ctl() Yiming Qian reported : <quote> I believe I found a locally triggerable kernel bug in the IPv6 sendmsg ancillary-data path that can panic the kernel via `skb_under_panic()` (local DoS). The core issue is a mismatch between: - a 16-bit length accumulator (`struct ipv6_txoptions::opt_flen`, type `__u16`) and - a pointer to the *last* provided destination-options header (`opt->dst1opt`) when multiple `IPV6_DSTOPTS` control messages (cmsgs) are provided. - `include/net/ipv6.h`: - `struct ipv6_txoptions::opt_flen` is `__u16` (wrap possible). (lines 291-307, especially 298) - `net/ipv6/datagram.c:ip6_datagram_send_ctl()`: - Accepts repeated `IPV6_DSTOPTS` and accumulates into `opt_flen` without rejecting duplicates. (lines 909-933) - `net/ipv6/ip6_output.c:__ip6_append_data()`: - Uses `opt->opt_flen + opt->opt_nflen` to compute header sizes/headroom decisions. (lines 1448-1466, especially 1463-1465) - `net/ipv6/ip6_output.c:__ip6_make_skb()`: - Calls `ipv6_push_frag_opts()` if `opt->opt_flen` is non-zero. (lines 1930-1934) - `net/ipv6/exthdrs.c:ipv6_push_frag_opts()` / `ipv6_push_exthdr()`: - Push size comes from `ipv6_optlen(opt->dst1opt)` (based on the pointed-to header). (lines 1179-1185 and 1206-1211) 1. `opt_flen` is a 16-bit accumulator: - `include/net/ipv6.h:298` defines `__u16 opt_flen; /* after fragment hdr */`. 2. `ip6_datagram_send_ctl()` accepts *repeated* `IPV6_DSTOPTS` cmsgs and increments `opt_flen` each time: - In `net/ipv6/datagram.c:909-933`, for `IPV6_DSTOPTS`: - It computes `len = ((hdr->hdrlen + 1) << 3);` - It checks `CAP_NET_RAW` using `ns_capable(net->user_ns, CAP_NET_RAW)`. (line 922) - Then it does: - `opt->opt_flen += len;` (line 927) - `opt->dst1opt = hdr;` (line 928) There is no duplicate rejection here (unlike the legacy `IPV6_2292DSTOPTS` path which rejects duplicates at `net/ipv6/datagram.c:901-904`). If enough large `IPV6_DSTOPTS` cmsgs are provided, `opt_flen` wraps while `dst1opt` still points to a large (2048-byte) destination-options header. In the attached PoC (`poc.c`): - 32 cmsgs with `hdrlen=255` => `len = (255+1)*8 = 2048` - 1 cmsg with `hdrlen=0` => `len = 8` - Total increment: `32*2048 + 8 = 65544`, so `(__u16)opt_flen == 8` - The last cmsg is 2048 bytes, so `dst1opt` points to a 2048-byte header. 3. The transmit path sizes headers using the wrapped `opt_flen`: - In `net/ipv6/ip6_output.c:1463-1465`: - `headersize = sizeof(struct ipv6hdr) + (opt ? opt->opt_flen + opt->opt_nflen : 0) + ...;` With wrapped `opt_flen`, `headersize`/headroom decisions underestimate what will be pushed later. 4. When building the final skb, the actual push length comes from `dst1opt` and is not limited by wrapped `opt_flen`: - In `net/ipv6/ip6_output.c:1930-1934`: - `if (opt->opt_flen) proto = ipv6_push_frag_opts(skb, opt, proto);` - In `net/ipv6/exthdrs.c:1206-1211`, `ipv6_push_frag_opts()` pushes `dst1opt` via `ipv6_push_exthdr()`. - In `net/ipv6/exthdrs.c:1179-1184`, `ipv6_push_exthdr()` does: - `skb_push(skb, ipv6_optlen(opt));` - `memcpy(h, opt, ipv6_optlen(opt));` With insufficient headroom, `skb_push()` underflows and triggers `skb_under_panic()` -> `BUG()`: - `net/core/skbuff.c:2669-2675` (`skb_push()` calls `skb_under_panic()`) - `net/core/skbuff.c:207-214` (`skb_panic()` ends in `BUG()`) - The `IPV6_DSTOPTS` cmsg path requires `CAP_NET_RAW` in the target netns user namespace (`ns_capable(net->user_ns, CAP_NET_RAW)`). - Root (or any task with `CAP_NET_RAW`) can trigger this without user namespaces. - An unprivileged `uid=1000` user can trigger this if unprivileged user namespaces are enabled and it can create a userns+netns to obtain namespaced `CAP_NET_RAW` (the attached PoC does this). - Local denial of service: kernel BUG/panic (system crash). - ---truncated---

Published
Apr 13, 2026
Updated
Nov 10, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31415

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.14affected
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 2dbfb003bbf3fc0e94f07efefab0ebcf83029a2aaffected · git
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 4082f9984a694829153115d28c956a3534f52f29affected · git
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 0bdaf54d3aaddfe8df29371260fa8d4939b4fd6faffected · git
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 5e4ee5dbea134e9257f205e31a96040bed71e83faffected · git
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 63fda74885555e6bd1623b5d811feec998740ba4affected · git
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 9ed81d692758dfb9471d7799b24bfa7a08224c31affected · git
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 872b74900d5daa37067ac676d9001bb929fc6a2aaffected · git
    • 333fad5364d6b457c8d837f7d05802d2aaf8a961 and later · before 4e453375561fc60820e6b9d8ebeb6b3ee177d42eaffected · git
    • before 2.6.14not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.12-16.19.12-1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.317.14.12.14-122.317.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_84before 1-8.7.11-8.7.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.317.14.12.14-122.317.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.317.14.12.14-122.317.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31425Apr 13, 2026 · rds: ib: reject FRMR registration before IB connection is established
    22Monitor
  • ← EarlierCVE-2026-31414Apr 13, 2026 · netfilter: nf_conntrack_expect: use expect->helper
    39Monitor
  • Later →CVE-2026-31416Apr 13, 2026 · netfilter: nfnetlink_log: account for netlink header size
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0bdaf54d3aaddfe8df29371260fa8d4939b4fd6fVendor (CNA)
Linux Linux2dbfb003bbf3fc0e94f07efefab0ebcf83029a2aVendor (CNA)
Linux Linux4082f9984a694829153115d28c956a3534f52f29Vendor (CNA)
Linux Linux4e453375561fc60820e6b9d8ebeb6b3ee177d42eVendor (CNA)
Linux Linux5e4ee5dbea134e9257f205e31a96040bed71e83fVendor (CNA)
Linux Linux63fda74885555e6bd1623b5d811feec998740ba4Vendor (CNA)
Linux Linux872b74900d5daa37067ac676d9001bb929fc6a2aVendor (CNA)
Linux Linux9ed81d692758dfb9471d7799b24bfa7a08224c31Vendor (CNA)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.317.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.317.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.317.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_841-8.7.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-3173918 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC
    35Monitor
  • CVE-2026-5295272 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
    35Monitor
  • CVE-2026-3139810 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios
    31Monitor
  • CVE-2026-4611745 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
    31Monitor
  • CVE-2025-39803210 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
    31Monitor
  • CVE-2026-4602744 days apartnet/smc: avoid early lgr access in smc_clc_wait_msg
    30Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-617 · Reachable Assertion

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records