CVE-2026-64580

xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst()

HIGH
7.8
CVSS Score
Published: August 5, 2026 at 08:09 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst() On the error path where in6_dev_get(dev) returns NULL, xfrm6_fill_dst() releases the device reference with netdev_put() but leaves xdst->u.dst.dev set. dst_destroy() later calls netdev_put(dst->dev) again, so the same net_device reference is released twice, underflowing its refcount (ref_tracker WARNING + "unregister_netdevice: waiting for <dev> to become free"). Clear xdst->u.dst.dev after the netdev_put(), the same way the XFRM device-offload paths xfrm_dev_state_add() and xfrm_dev_policy_add() in net/xfrm/xfrm_device.c NULL ->dev when releasing the reference on error. ref_tracker: reference already released. ref_tracker: allocated in: xfrm6_fill_dst (net/ipv6/xfrm6_policy.c:86) ... udpv6_sendmsg (net/ipv6/udp.c:1696) ... ref_tracker: freed in: xfrm6_fill_dst (net/ipv6/xfrm6_policy.c:90) ... WARNING: lib/ref_tracker.c:322 at ref_tracker_free+0x58b/0x780 dst_destroy (net/core/dst.c:115) rcu_core handle_softirqs ...

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

01b0d887f67a388fb2a658ee2bdd74e5ba1468181b0d887f67a388fb2a658ee2bdd74e5ba1468183.0.793.103.2.463.4.463.9.384c4a9dfbf430861e7588d95ae3ff61535dca351a7e22d0c0e81dde129a51ee413644124f4b59954a98124aac0b5adc5de8ae54f11322781cb4d85c3e27b7bee743d921f037b1da6f071237345bef7c1
Vendor states this is fixed in 136992de9bb91871084ae52d172610541c76e4d2 (fixed)
Vendor states this is fixed in 43de8a49335e611adb271bbd52e84dfbc11fc185 (fixed)
Vendor states this is fixed in 97e032e5733e49471fb73de117ea2ac1ac7c479a (fixed)
Vendor states this is fixed in df6856c2dda9187601d29b5fbd7a81b3b178cedf (fixed)
Vendor states this is fixed in e078da1b4e11390cff3201c19a9a1fe70c5b934f (fixed)
Vendor states this is fixed in ff636d7b7cba6dea82ecf580415ea57f2c1a11b6 (fixed)
Affected range stops below 3.1, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.10 (unaffected)
Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-415

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card