CVE-2026-64123
Last modified
CVE-2026-64123 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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(). EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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().
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.2.12, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.93 | — |
| Linux | Linux Kernel | >= 6.13, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64123?
How severe is CVE-2026-64123?
How do I fix CVE-2026-64123?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64118In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-64119In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6412Certificate policy and RFC 8446 compliance concerns regardin…4.3
- CVE-2026-64120In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64121In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64122In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64124In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64125In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64126In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-64127In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64129In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64123?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
