CVE-2026-63984
Linux kernel vulnerability
- Published19 Jul 2026
Description
In the Linux kernel, the following vulnerability has been resolved: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() ipv6_rpl_srh_decompress() computes: outhdr->hdrlen = (((n + 1) * sizeof(struct in6_addr)) >> 3); hdrlen is __u8. For n >= 127 the result exceeds 255 and silently truncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16): (128 * 16) >> 3 = 256, truncated to 0 as __u8 The caller in ipv6_rpl_srh_rcv() then places the compressed header at buf + ((ohdr->hdrlen + 1) << 3). With hdrlen=0 this is buf + 8, but the decompressed region occupies buf[0..2055] (8-byte header plus 128 full addresses). The compressed header overlaps the decompressed data, and ipv6_rpl_srh_compress() writes into this overlap, corrupting the routing header of the forwarded packet. The existing guard at exthdrs.c:546 checks (n + 1) > 255, which prevents n+1 from overflowing unsigned char (the segments_left field), but does not prevent the computed hdrlen from overflowing __u8. n=127 passes because 128 <= 255, yet hdrlen=256 does not fit. Tighten the bound to (n + 1) > 127. This caps n at 126, giving hdrlen = (127 * 16) >> 3 = 254, which fits in __u8. The compressed header then lands at buf + ((254 + 1) << 3) = buf + 2040, exactly past the decompressed region (buf[0..2039]). No overlap. 127 segments is well beyond any realistic RPL deployment.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/3618b34942b76471d044369bfd30d58c39068bf1
- https://git.kernel.org/stable/c/6fe1cb312038516cb4d9fa089d700af7059f1a64
- https://git.kernel.org/stable/c/75b3680047bf09af8e7e471a7a6ddf2ce5847f56
- https://git.kernel.org/stable/c/97e06791368c01f0ad2a4b3269c2abe19485ca32
- https://git.kernel.org/stable/c/9d5e7a46a9f6d8f503b41bfefef70659845f1679
- https://git.kernel.org/stable/c/c0487a9c1e116cf349e2d1f302d9019670460858
- https://git.kernel.org/stable/c/de02fc049352af5a9595f015511222d0a85c326b
- https://git.kernel.org/stable/c/fd238c51b0fa5390cceca9f1ac5a9ffda8063eed
Frequently asked
Is CVE-2026-63984 being actively exploited?
CVE-2026-63984 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.51%.
How severe is CVE-2026-63984?
CVE-2026-63984 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.51% probability of exploitation.
How do I fix CVE-2026-63984?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-63984 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.