CVE-2026-63920 — ipv6: validate extension header length before copying to cmsg
In the Linux kernel, the following vulnerability has been resolved: ipv6: validate extension header length before copying to cmsg ip6_datagram_recv_specific_ctl() builds IPV6_{HOPOPTS,DSTOPTS,RTHDR} cmsgs (and their IPV6_2292* legacy counterparts) by trusting the on-wire hdrlen byte (ptr[1]) when computing the put_cmsg() length. The length was validated only at parse time (ipv6_parse_hopopts(), etc.). An nftables payload-write expression can rewrite hdrlen after parsing and before the skb reaches recvmsg; the write itself is in-bounds but put_cmsg() then reads up to ((hdrlen+1) << 3) = 2040 bytes from an 8-byte header. nftables is reachable from an unprivileged user namespace, so this is an unprivileged slab-out-of-bounds read: BUG: KASAN: slab-out-of-bounds in put_cmsg+0x3ac/0x540 put_cmsg+0x3ac/0x540 udpv6_recvmsg+0xca0/0x1250 sock_recvmsg+0xdf/0x190 ____sys_recvmsg+0x1b1/0x620 Add ipv6_get_exthdr_len() which validates that at least two bytes are accessible before reading the hdrlen field, then checks the computed length against skb_tail_pointer(skb), returning 0 on failure. Extension headers are kept in the linear skb area by pskb_may_pull() during input, so skb_tail_pointer() is the correct bound. Use ipv6_get_exthdr_len() at all non-AH call sites: the five standalone cmsg blocks (HbH, 2292HbH, 2292DSTOPTS x2, 2292RTHDR) and the three standard cases in the extension-header walk loop (DSTOPTS, ROUTING, default). AH retains an inline bounds check because its length formula differs ((ptr[1]+2)<<2). The walk loop also gets a pre-read bounds check at the top to validate ptr before any case accesses ptr[0] or ptr[1]. When the walk loop detects a corrupted header, return from the function instead of continuing to process later socket options.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 81394827dfb72772c50d0ae3bdfa094428a5d76d≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 931b4a1f13408c2507719890f78f7227c34a0282≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 08464413e628803bd10cb1df68d0138665f2f885≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a29768d56eb3798c052ad3281b05596e695a17af≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 0d330eff318c0f44d4fb0ad2c2aef38f87f24c90≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a35daeabb433686234b010ebf7b53778dbd6c9b8≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < eb18a1b1644e4cad978df2131e2bb9a2e6886992≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < dd433671fef381fdaf7b530c631e6b782d66e224 and 1 moreversion 2.6.12 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.1 | High | 1.8 | 5.2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.1
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/0d330eff318c0f44d4fb0ad2c2aef38f87f24c90
- git.kernel.org/stable/c/931b4a1f13408c2507719890f78f7227c34a0282
- git.kernel.org/stable/c/dd433671fef381fdaf7b530c631e6b782d66e224
- git.kernel.org/stable/c/eb18a1b1644e4cad978df2131e2bb9a2e6886992
- git.kernel.org/stable/c/81394827dfb72772c50d0ae3bdfa094428a5d76d
- git.kernel.org/stable/c/a29768d56eb3798c052ad3281b05596e695a17af
- git.kernel.org/stable/c/08464413e628803bd10cb1df68d0138665f2f885
- git.kernel.org/stable/c/a35daeabb433686234b010ebf7b53778dbd6c9b8
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-63920 is "ipv6: validate extension header length before copying to cmsg", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.