7.8
HIGH CVSS 3.1
CVE-2026-64005
net/smc: Do not re-initialize smc hashtables
Description

In the Linux kernel, the following vulnerability has been resolved: net/smc: Do not re-initialize smc hashtables INIT_HLIST_HEAD(&smc_v*_hashinfo.ht) are called after smc_nl_init(), proto_register() and sock_register(). This can lead to smc_v*_hashinfo.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 smc_v*_hashinfo.ht in smc_init(); it is implicitly initialised to zero anyhow. Add HLIST_HEAD_INIT to the definitions for clarity.

INFO

Published Date :

July 19, 2026, 4:17 p.m.

Last Modified :

July 30, 2026, 2:51 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-64005 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
Remove unnecessary re-initialization of smc hashtables in smc_init.
  • Remove re-initialization of smc_v*_hashinfo.ht in smc_init.
  • Add HLIST_HEAD_INIT to definitions for clarity.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-64005 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-64005 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-64005 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-64005 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 20, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 19, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': 'cdc79c05cc375f68ae87b0c74fdaac1a5c93155a', 'versionType': 'git'}, {'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': '2006605006e5a4a11d93e1ebdbbe95764d24276f', 'versionType': 'git'}, {'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': '64c96e497d5ada0b90e99bf58f893aa2b73dcfbc', 'versionType': 'git'}, {'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': 'ed7a758313011885347b854e97cb95903ef3c3f7', 'versionType': 'git'}, {'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': '0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d', 'versionType': 'git'}, {'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': '55cba6b883b41e5922c00ba9d4e3262131f46f1b', 'versionType': 'git'}, {'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': '5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1', 'versionType': 'git'}, {'status': 'affected', 'version': 'f16a7dd5cf27eeda187425c9c7d96802a549f9c4', 'lessThan': '9e4389b0038781f19f97895186ed941ff8ac1678', 'versionType': 'git'}], 'programFiles': ['net/smc/af_smc.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.11'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.11', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/smc/af_smc.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: net/smc: Do not re-initialize smc hashtables INIT_HLIST_HEAD(&smc_v*_hashinfo.ht) are called after smc_nl_init(), proto_register() and sock_register(). This can lead to smc_v*_hashinfo.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 smc_v*_hashinfo.ht in smc_init(); it is implicitly initialised to zero anyhow. Add HLIST_HEAD_INIT to the definitions for clarity.
    Added Reference https://git.kernel.org/stable/c/0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d
    Added Reference https://git.kernel.org/stable/c/2006605006e5a4a11d93e1ebdbbe95764d24276f
    Added Reference https://git.kernel.org/stable/c/55cba6b883b41e5922c00ba9d4e3262131f46f1b
    Added Reference https://git.kernel.org/stable/c/5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
    Added Reference https://git.kernel.org/stable/c/64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
    Added Reference https://git.kernel.org/stable/c/9e4389b0038781f19f97895186ed941ff8ac1678
    Added Reference https://git.kernel.org/stable/c/cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
    Added Reference https://git.kernel.org/stable/c/ed7a758313011885347b854e97cb95903ef3c3f7
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.