CVE-2026-43501: ipv6: rpl: reserve mac_len headroom when recompressed SRH grows
In the Linux kernel, the following vulnerability has been resolved:
ipv6: rpl: reserve mac_len headroom when recompressed SRH grows
ipv6_rpl_srh_rcv() decompresses an RFC 6554 Source Routing Header, swaps
the next segment into ipv6_hdr->daddr, recompresses, then pulls the old
header and pushes the new one plus the IPv6 header back. The
recompressed header can be larger than the received one when the swap
reduces the common-prefix length the segments share with daddr (CmprI=0,
CmprE>0, seg[0][0] != daddr[0] gives the maximum +8 bytes).
pskb_expand_head() was gated on segments_left == 0, so on earlier
segments the push consumed unchecked headroom. Once skb_push() leaves
fewer than skb->mac_len bytes in front of data,
skb_mac_header_rebuild()'s call to:
skb_set_mac_header(skb, -skb->mac_len);
will store (data - head) - mac_len into the u16 mac_header field, which
wraps to ~65530, and the following memmove() writes mac_len bytes ~64KiB
past skb->head.
A single AF_INET6/SOCK_RAW/IPV6_HDRINCL packet over lo with a two
segment type-3 SRH (CmprI=0, CmprE=15) reaches headroom 8 after one
pass; KASAN reports a 14-byte OOB write in ipv6_rthdr_rcv.
Fix this by expanding the head whenever the remaining room is less than
the push size plus mac_len, and request that much extra so the rebuilt
MAC header fits afterwards.
Security readout for executives and security teams
Plain-English summary
A Linux IPv6 RPL routing flaw can let a specially formed packet trigger an out-of-bounds kernel memory write. A successful attack could crash a host or potentially compromise confidentiality and integrity. The supplied record rates it CVSS 9.8, but the demonstrated path uses a raw IPv6 packet over loopback.
Executive priority
Treat as an urgent kernel-patching issue because the documented condition causes memory corruption and carries a critical score. Accelerate assessment on high-value and shared Linux systems. Balance urgency with the incomplete evidence about practical remote reachability and the absence of confirmed active exploitation.
Technical view
During RFC 6554 source-routing-header processing, recompression can enlarge the header by up to eight bytes. Insufficient headroom lets skb_push leave inadequate MAC-header space; a u16 mac_header offset then wraps, and memmove writes roughly 64 KiB beyond skb->head. The fix expands headroom whenever the recompressed header plus mac_len will not fit.
Likely exposure
Exposure applies to affected Linux kernels exercising the IPv6 RPL source-routing-header path. The bundle lists affected kernel versions and multiple stable fixes, but does not fully map every distribution build. Prioritize hosts, appliances, and shared systems where untrusted workloads or traffic can reach this kernel processing path.
Exploitation context
The supplied reproducer reaches a 14-byte out-of-bounds write using one AF_INET6/SOCK_RAW/IPV6_HDRINCL packet over loopback. However, the bundle reports KEV as false and provides no evidence of active exploitation. It also does not establish whether arbitrary remote traffic can reach the demonstrated path in typical deployments.
Researcher notes
The strongest evidence is the detailed kernel failure analysis and stable-branch fixes. The maximum growth occurs when recompression changes the common-prefix relationship, ultimately wrapping mac_header before MAC-header reconstruction. The supplied affected-version data is not sufficiently clear for universal version-range conclusions; distribution-specific advisories should control package determinations.
Mitigation direction
Install vendor-supported kernels containing the applicable upstream stable fix.
Apply the relevant Red Hat security erratum on affected Red Hat systems.
Consult your Linux distributor for exact package status and reboot requirements.
Prioritize internet-facing, multi-tenant, and untrusted-workload systems after confirming exposure.
Validation and detection
Inventory running kernel versions across Linux hosts and appliances.
Compare each distribution package against its vendor advisory or fixed build.
Verify the installed kernel incorporates the applicable stable commit.
Confirm systems booted into the updated kernel after maintenance.
Use approved defensive testing to confirm affected IPv6 RPL processing is no longer vulnerable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-131: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
1ADP providers
19Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-131 · source CWE mapping
Incorrect Calculation of Buffer Size
Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.