SECUFOCUSNOW
Home›CVE index›CVE-2026-64005
Review reviewHigh

CVE-2026-64005

Linux

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.

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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.

Affected product and versions

Product
Linux
Affected versions
>= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < cdc79c05cc375f68ae87b0c74fdaac1a5c93155a, >= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < 2006605006e5a4a11d93e1ebdbbe95764d24276f, >= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc, >= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < ed7a758313011885347b854e97cb95903ef3c3f7, >= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d, >= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < 55cba6b883b41e5922c00ba9d4e3262131f46f1b, >= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < 5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1, >= f16a7dd5cf27eeda187425c9c7d96802a549f9c4 < 9e4389b0038781f19f97895186ed941ff8ac1678, >= 4.11
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available