PatchSiren cyber security CVE debrief
CVE-2026-64580 Linux CVE debrief
The Linux kernel's xfrm6_fill_dst function has a vulnerability that can lead to a double netdev_put issue. This occurs when the in6_dev_get(dev) function returns NULL, causing xfrm6_fill_dst() to release the device reference with netdev_put() but leave xdst->u.dst.dev set. Later, dst_destroy() calls netdev_put(dst->dev) again, resulting in the same net_device reference being released twice and underflowing its refcount. The fix involves clearing xdst->u.dst.dev after the netdev_put(), similar to how the XFRM device-offload paths xfrm_dev_state_add() and xfrm_dev_policy_add() in net/xfrm/xfrm_device.c handle it. Linux kernel maintainers, users, and administrators should be aware of this vulnerability and take steps to verify and apply the fix. They should review Linux kernel configurations to prevent similar issues and monitor Linux kernel updates for related patches. Additionally, they should consider implementing compensating controls for exposed systems and tracking exceptions and retesting remediated assets.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-05
- Original CVE updated
- 2026-08-19
- Advisory published
- 2026-08-05
- Advisory updated
- 2026-08-19
Who should care
Linux kernel maintainers, users, and administrators should be aware of this vulnerability and take steps to verify and apply the fix. They should review Linux kernel configurations to prevent similar issues and monitor Linux kernel updates for related patches. Additionally, they should consider implementing compensating controls for exposed systems and tracking exceptions and retesting remediated assets.
Technical summary
The Linux kernel's xfrm6_fill_dst function has a vulnerability that can lead to a double netdev_put issue. The fix involves clearing xdst->u.dst.dev after the netdev_put(). This vulnerability affects Linux kernel maintainers and users, who should prioritize verifying and applying the fix to prevent potential double netdev_put issues. The vulnerability is related to the xfrm6_fill_dst function, which is part of the Linux kernel's IPsec implementation.
Defensive priority
Linux kernel maintainers and users should prioritize verifying and applying the fix to prevent potential double netdev_put issues.
Recommended defensive actions
- Verify and apply the fix to the Linux kernel
- Review and update Linux kernel configurations to prevent similar issues
- Monitor Linux kernel updates for related patches
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE description indicates a vulnerability in the Linux kernel's xfrm6_fill_dst function, which can lead to a double netdev_put issue. The fix involves clearing xdst->u.dst.dev after the netdev_put(). To verify, defenders should review the Linux kernel's xfrm6_fill_dst function implementation and check for the presence of the fix. Additionally, they should monitor Linux kernel updates for related patches and review compensating controls for exposed systems.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-64580 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-64580
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-64580 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64580
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/136992de9bb91871084ae52d172610541c76e4d2
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/43de8a49335e611adb271bbd52e84dfbc11fc185
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/df6856c2dda9187601d29b5fbd7a81b3b178cedf
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e078da1b4e11390cff3201c19a9a1fe70c5b934f
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ff636d7b7cba6dea82ecf580415ea57f2c1a11b6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.