CVE-2026-64581 — xfrm: fix sk_dst_cache double-free in xfrm_user_policy()
In the Linux kernel, the following vulnerability has been resolved: xfrm: fix sk_dst_cache double-free in xfrm_user_policy() xfrm_user_policy() clears the socket dst cache with __sk_dst_reset(), i.e. the non-atomic __sk_dst_set(sk, NULL): it reads sk_dst_cache with rcu_dereference_protected(), stores NULL and dst_release()s the old dst. That is only safe if no other thread modifies sk_dst_cache concurrently. For a connected UDP socket that does not hold: the transmit fast path (udp_sendmsg -> sk_dst_check -> sk_dst_reset) resets the cache locklessly with an atomic xchg(). A per-socket policy change racing a send can make both sides observe the same old dst and each dst_release() it, dropping the socket's single reference twice and freeing the xfrm_dst bundle while it is still referenced: BUG: KASAN: slab-use-after-free in dst_release Write of size 4 at addr ffff88801897b6c0 by task exploit/155 Call Trace: ... dst_release (... ./include/linux/rcuref.h:109) xfrm_user_policy (./include/net/sock.h:2239 ./include/net/sock.h:2256 net/xfrm/xfrm_state.c:3053) do_ip_setsockopt (net/ipv4/ip_sockglue.c:1347) ip_setsockopt (net/ipv4/ip_sockglue.c:1417) do_sock_setsockopt (net/socket.c:2368) __sys_setsockopt (net/socket.c:2393) __x64_sys_setsockopt (net/socket.c:2396) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Reachable by an unprivileged user via a user+network namespace. Use the atomic sk_dst_reset() so the cache is cleared and released with a single xchg(): whichever side wins releases the dst once, the other sees NULL and does nothing. Behaviour is otherwise unchanged.
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.1% (30-day exploitation probability)+0
- 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.
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 |
version adc1ec6cdc20d430aa01b86497220709b9149466version 4.14≥ 4.9.89 and < 4.10≥ 4.4.123 and < 4.5≥ 4.1.52 and < 4.2≥ 3.18.101 and < 3.19≥ 4.4.163 and < 4.5≥ 3.16.52 and < 3.17 and 13 moreversion 5eef9b51114fcc65651d671add52f267f91b9451version c9e82cb34c3c2ee895af01bc899c6ed0bc6eb04aversion b54033eb1cfd77aba471269ddd804ed8d3e35dea≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < e8686fd8d18b99f3a9038683045b2f2338a7706dversion 9e9fe58a92a46c6d154d2901735bf230d91b8507version 72f157be2f81910ae759bfe2e5c2256fc4625645≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < c283e9ada7fcb7dd4b10592623086b2e6d2f9925≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < 96b678d08268b5f5c6fc99d4289d9b7e334fc683≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < 0ea8f06454012d9e7f9c6e6253df710949bf6294≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < 8dd8929b71c4f06c614f8f54c2cc070453faae16≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < f0ab9a71167bae308e05ab13b65e2007504a603f≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < f833821e4b52ab6335d443ede5fb79c38e61d19a≥ 2b06cdf3e688b98fcc9945873b5d42792bd4eee0 and < a9340ebdc13f8bb5063c0bc0b037ee7e640d4ae9 |
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.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | 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:H/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
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- 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/8dd8929b71c4f06c614f8f54c2cc070453faae16
- git.kernel.org/stable/c/c283e9ada7fcb7dd4b10592623086b2e6d2f9925
- git.kernel.org/stable/c/a9340ebdc13f8bb5063c0bc0b037ee7e640d4ae9
- git.kernel.org/stable/c/e8686fd8d18b99f3a9038683045b2f2338a7706d
- git.kernel.org/stable/c/96b678d08268b5f5c6fc99d4289d9b7e334fc683
- git.kernel.org/stable/c/0ea8f06454012d9e7f9c6e6253df710949bf6294
- git.kernel.org/stable/c/f833821e4b52ab6335d443ede5fb79c38e61d19a
- git.kernel.org/stable/c/f0ab9a71167bae308e05ab13b65e2007504a603f
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 22h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 22h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
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 CISA SSVC assessment.
- 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-64581 is "xfrm: fix sk_dst_cache double-free in xfrm_user_policy()", 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.8 describes technical severity. EPSS 0.12% 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.