Answer in brief
CVE-2026-64005 records a High severity (CVSS 7.8) vulnerability in net/smc: Do not re-initialize smc hashtables. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <cdc79c05cc375f68ae87b0c74fdaac1a5c93155a || >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <2006605006e5a4a11d93e1ebdbbe95764d24276f || >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <64c96e497d5ada0b90e99bf58f893aa2b73dcfbc || >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <ed7a758313011885347b854e97cb95903ef3c3f7 || >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d || >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <55cba6b883b41e5922c00ba9d4e3262131f46f1b || >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1 || >=f16a7dd5cf27eeda187425c9c7d96802a549f9c4 <9e4389b0038781f19f97895186ed941ff8ac1678 | cdc79c05cc375f68ae87b0c74fdaac1a5c93155a, 2006605006e5a4a11d93e1ebdbbe95764d24276f, 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc, ed7a758313011885347b854e97cb95903ef3c3f7, 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d, 55cba6b883b41e5922c00ba9d4e3262131f46f1b, 5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1, 9e4389b0038781f19f97895186ed941ff8ac1678 |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.