PatchSiren cyber security CVE debrief
CVE-2026-64123 Linux CVE debrief
The Linux kernel was vulnerable to a use-after-free issue in the HSR node table. When HSR node-list and node-status generic-netlink operations ran under rcu_read_lock(), they could hold a struct hsr_node pointer across hsr_dellink(), leading to a slab-use-after-free when the reader copied node->macaddress_A. The issue was resolved by deferring the node table free until after RCU readers using list_del_rcu() and hsr_free_node_rcu(). This vulnerability affects Linux kernel users and administrators, who should take steps to ensure their systems are updated with the patched kernel.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-19
- Original CVE updated
- 2026-07-19
- Advisory published
- 2026-07-19
- Advisory updated
- 2026-07-19
Who should care
Linux kernel users and administrators should be aware of this vulnerability and take steps to ensure their systems are updated with the patched kernel. This includes reviewing system configurations, monitoring system logs for potential exploitation attempts, and ensuring that HSR is properly configured.
Technical summary
The vulnerability was caused by the HSR node-list and node-status generic-netlink operations running under rcu_read_lock() and holding a struct hsr_node pointer across hsr_dellink(). This led to a slab-use-after-free when the reader copied node->macaddress_A. The issue was resolved by changing the node deletion to use list_del_rcu() and deferring the free through the existing hsr_free_node_rcu() callback. This change ensures that the node table is not freed until after RCU readers have completed, preventing the use-after-free vulnerability.
Defensive priority
High
Recommended defensive actions
- Update the Linux kernel to the patched version
- Review system configurations and ensure HSR is properly configured
- Monitor system logs for potential exploitation attempts
- 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 record was published on 2026-07-19T16:17:53.907Z and has not been modified since then. The NVD entry is currently Received. There is no additional information available about the vulnerability beyond what is provided in the CVE record and NVD entry.
Official resources
-
CVE-2026-64123 CVE record
CVE.org
-
CVE-2026-64123 NVD detail
NVD
-
Source item URL
nvd_modified
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-19T16:17:53.907Z and has not been modified since then.