CVE-2026-64005: net/smc: Do not re-initialize smc hashtables
In the Linux kernel, the following vulnerability has been resolved:
net/smc: Do not re-initialize smc hashtables
INITHLISTHEAD(&smcvhashinfo.ht) are called after smcnlinit(), protoregister() and sockregister(). This can lead to smcvhashinfo.ht being reset even though hash entries already exist and are being used, possibly resulting in a corrupted list.
Remove unnecessary and dangerous re-initialisation of smcvhashinfo.ht in smcinit(); it is implicitly initialised to zero anyhow. Add HLISTHEADINIT to the definitions for clarity.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Remove the unnecessary re-initialization of smc_v*_hashinfo.ht; define the hash-table heads with HLIST_HEAD_INIT so existing hash entries are not reset or corrupted.
Linux kernel net/smc smc_v*_hashinfo.ht initialization = Initialize with HLIST_HEAD_INIT and do not call INIT_HLIST_HEAD(&smc_v*_hashinfo.ht) after smc_nl_init()
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64005?
CVE-2026-64005 has a risk score of 34, indicating a moderate level of severity.
How do I fix CVE-2026-64005?
To fix CVE-2026-64005, update the Linux kernel to a version that has addressed the vulnerability.
What systems are affected by CVE-2026-64005?
CVE-2026-64005 affects the Linux kernel due to improper handling of smc hashtables.
What are the potential impacts of CVE-2026-64005?
CVE-2026-64005 can lead to the resetting of hash entries in the smc_v*_hashinfo.ht, causing performance issues.
When was CVE-2026-64005 published?
CVE-2026-64005 was published on July 19, 2026.