CVE-2026-43139: xfrm6: fix uninitialized saddr in xfrm6_get_saddr()
In the Linux kernel, the following vulnerability has been resolved:
xfrm6: fix uninitialized saddr in xfrm6_get_saddr()
xfrm6_get_saddr() does not check the return value of
ipv6_dev_get_saddr(). When ipv6_dev_get_saddr() fails to find a suitable
source address (returns -EADDRNOTAVAIL), saddr->in6 is left
uninitialized, but xfrm6_get_saddr() still returns 0 (success).
This causes the caller xfrm_tmpl_resolve_one() to use the uninitialized
address in xfrm_state_find(), triggering KMSAN warning:
=====================================================
BUG: KMSAN: uninit-value in xfrm_state_find+0x2424/0xa940
xfrm_state_find+0x2424/0xa940
xfrm_resolve_and_create_bundle+0x906/0x5a20
xfrm_lookup_with_ifid+0xcc0/0x3770
xfrm_lookup_route+0x63/0x2b0
ip_route_output_flow+0x1ce/0x270
udp_sendmsg+0x2ce1/0x3400
inet_sendmsg+0x1ef/0x2a0
__sock_sendmsg+0x278/0x3d0
__sys_sendto+0x593/0x720
__x64_sys_sendto+0x130/0x200
x64_sys_call+0x332b/0x3e70
do_syscall_64+0xd3/0xf80
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Local variable tmp.i.i created at:
xfrm_resolve_and_create_bundle+0x3e3/0x5a20
xfrm_lookup_with_ifid+0xcc0/0x3770
=====================================================
Fix by checking the return value of ipv6_dev_get_saddr() and propagating
the error.
Security readout for executives and security teams
Plain-English summary
A Linux IPv6 networking flaw can use an uninitialized source address when address selection fails. This may cause incorrect processing or service disruption in affected systems using the XFRM/IPsec networking path. The supplied record rates it high severity, but does not establish practical exploitation or active attacks.
Executive priority
Treat as a high-priority kernel maintenance issue, especially for internet-facing or availability-sensitive Linux systems using IPv6 IPsec. Accelerate inventory and vendor patch verification, while avoiding claims of an emergency active-exploitation event because none is supported by the supplied evidence.
Technical view
xfrm6_get_saddr() incorrectly reports success after ipv6_dev_get_saddr() returns EADDRNOTAVAIL, leaving an IPv6 address uninitialized. xfrm_tmpl_resolve_one() then passes that value into xfrm_state_find(). The observed result is a KMSAN uninitialized-value warning. The fix propagates the address-selection error instead of continuing.
Likely exposure
Potential exposure exists on affected Linux kernels where IPv6 traffic traverses XFRM processing, commonly associated with IPsec. The source lists affected kernel versions but provides no distribution package mapping, configuration prerequisites, or confirmation that every listed version is exploitable in practice.
Exploitation context
The CVE is not in the supplied KEV data, and the sources provide no evidence of active exploitation or a public exploit. Although the supplied CVSS vector indicates unauthenticated network reachability, the technical description alone does not establish a reliable remote attack path.
Researcher notes
The demonstrated condition is an uninitialized IPv6 address reaching xfrm_state_find(), detected by KMSAN during UDP send processing. Sources do not document a crash, information disclosure mechanism, successful corruption, or reproducible remote trigger. The supplied CVSS impacts therefore exceed what the technical trace alone proves.
Mitigation direction
Apply a vendor kernel update containing the referenced stable fix.
Check distribution advisories for backported fixes and corrected package versions.
Prioritize systems using IPv6 with XFRM or IPsec functionality.
Follow vendor guidance if immediate kernel replacement is operationally impractical.
Validation and detection
Inventory running kernel and distribution package versions across Linux systems.
Confirm the installed package contains the upstream error-propagation fix or an equivalent backport.
Identify hosts using IPv6 XFRM or IPsec networking paths.
Review kernel diagnostics for related uninitialized-value warnings or unexplained networking failures.
Retest affected networking workflows after updating.
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.
cve · low confidence lookup
CVE-2026-43139 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
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.