In the Linux kernel, the following vulnerability has been resolved: net: hsr: defer node table free until after RCU readers HSR node-list and… (CVE-2026-64123)
In the Linux kernel, the following vulnerability has been resolved: net: hsr: defer node table free until after RCU readers HSR node-list and node-status generic-netlink operations run under rcu_read_lock(). They walk hsr->node_db through hsr_get_next_node() and hsr_get_node_data(), but RTM_DELLINK teardown removes the same node table with plain list_del() and frees each node immediately. That lets a generic-netlink reader hold a struct hsr_node pointer across hsr_dellink(). In a KASAN build, widening the reader window after hsr_get_next_node() obtains the node reproduces a slab-use-after-free when the reader copies node->macaddress_A; the freeing stack is hsr_del_nodes() from hsr_dellink(). Use list_del_rcu() and defer the free through the existing hsr_free_node_rcu() callback. This matches the lifetime rule used by the HSR prune paths, which already delete nodes with list_del_rcu() and call_rcu().
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's HSR subsystem arises because generic-netlink operations that read the node list and node status run under rcu_read_lock(), traversing the node database via hsr_get_next_node() and hsr_get_node_data(). However, the RTM_DELLINK teardown path removes the node table using list_del() and immediately frees each node, which can cause a use-after-free condition if a generic-netlink reader holds a pointer to a node during hsr_dellink(). In KASAN builds, this manifests as a slab-use-after-free when the reader accesses node->macaddress_A. The fix involves replacing list_del() with list_del_rcu() and deferring node freeing through the hsr_free_node_rcu() callback, aligning with existing lifetime management in HSR prune paths that use list_del_rcu() and call_rcu().
Potential Impact
This vulnerability can lead to use-after-free memory corruption in the Linux kernel's HSR networking code, potentially causing kernel crashes or undefined behavior. There is no indication of known exploits in the wild. The issue affects kernel memory safety under specific conditions involving concurrent access to HSR node data during link teardown.
Mitigation Recommendations
A fix has been implemented that changes the node removal process to use list_del_rcu() and defers freeing nodes until after RCU readers complete via the hsr_free_node_rcu() callback. Users should update to Linux kernel versions that include this fix once available. Patch status is not yet confirmed; check the vendor advisory or Linux kernel mailing lists for the specific fixed versions and remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: net: hsr: defer node table free until after RCU readers HSR node-list and… (CVE-2026-64123)
Description
In the Linux kernel, the following vulnerability has been resolved: net: hsr: defer node table free until after RCU readers HSR node-list and node-status generic-netlink operations run under rcu_read_lock(). They walk hsr->node_db through hsr_get_next_node() and hsr_get_node_data(), but RTM_DELLINK teardown removes the same node table with plain list_del() and frees each node immediately. That lets a generic-netlink reader hold a struct hsr_node pointer across hsr_dellink(). In a KASAN build, widening the reader window after hsr_get_next_node() obtains the node reproduces a slab-use-after-free when the reader copies node->macaddress_A; the freeing stack is hsr_del_nodes() from hsr_dellink(). Use list_del_rcu() and defer the free through the existing hsr_free_node_rcu() callback. This matches the lifetime rule used by the HSR prune paths, which already delete nodes with list_del_rcu() and call_rcu().
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's HSR subsystem arises because generic-netlink operations that read the node list and node status run under rcu_read_lock(), traversing the node database via hsr_get_next_node() and hsr_get_node_data(). However, the RTM_DELLINK teardown path removes the node table using list_del() and immediately frees each node, which can cause a use-after-free condition if a generic-netlink reader holds a pointer to a node during hsr_dellink(). In KASAN builds, this manifests as a slab-use-after-free when the reader accesses node->macaddress_A. The fix involves replacing list_del() with list_del_rcu() and deferring node freeing through the hsr_free_node_rcu() callback, aligning with existing lifetime management in HSR prune paths that use list_del_rcu() and call_rcu().
Potential Impact
This vulnerability can lead to use-after-free memory corruption in the Linux kernel's HSR networking code, potentially causing kernel crashes or undefined behavior. There is no indication of known exploits in the wild. The issue affects kernel memory safety under specific conditions involving concurrent access to HSR node data during link teardown.
Mitigation Recommendations
A fix has been implemented that changes the node removal process to use list_del_rcu() and defers freeing nodes until after RCU readers complete via the hsr_free_node_rcu() callback. Users should update to Linux kernel versions that include this fix once available. Patch status is not yet confirmed; check the vendor advisory or Linux kernel mailing lists for the specific fixed versions and remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q3v2-68cr-qhrm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64123"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912abca
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:44:16 UTC
Last updated: 07/20/2026, 19:41:21 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.