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 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.
- Published
- Jul 19, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.11affected
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before cdc79c05cc375f68ae87b0c74fdaac1a5c93155aaffected · git
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before 2006605006e5a4a11d93e1ebdbbe95764d24276faffected · git
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before 64c96e497d5ada0b90e99bf58f893aa2b73dcfbcaffected · git
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before ed7a758313011885347b854e97cb95903ef3c3f7affected · git
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82daffected · git
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before 55cba6b883b41e5922c00ba9d4e3262131f46f1baffected · git
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before 5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1affected · git
- f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and later · before 9e4389b0038781f19f97895186ed941ff8ac1678affected · git
- before 4.11not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d | Vendor (CNA) |
| Linux Linux | 2006605006e5a4a11d93e1ebdbbe95764d24276f | Vendor (CNA) |
| Linux Linux | 55cba6b883b41e5922c00ba9d4e3262131f46f1b | Vendor (CNA) |
| Linux Linux | 5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1 | Vendor (CNA) |
| Linux Linux | 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc | Vendor (CNA) |
| Linux Linux | 9e4389b0038781f19f97895186ed941ff8ac1678 | Vendor (CNA) |
| Linux Linux | cdc79c05cc375f68ae87b0c74fdaac1a5c93155a | Vendor (CNA) |
| Linux Linux | ed7a758313011885347b854e97cb95903ef3c3f7 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d
- git.kernel.org/stable/c/2006605006e5a4a11d93e1ebdbbe95764d24276f
- git.kernel.org/stable/c/55cba6b883b41e5922c00ba9d4e3262131f46f1b
- git.kernel.org/stable/c/5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
- git.kernel.org/stable/c/64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
- git.kernel.org/stable/c/9e4389b0038781f19f97895186ed941ff8ac1678
- git.kernel.org/stable/c/cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
- git.kernel.org/stable/c/ed7a758313011885347b854e97cb95903ef3c3f7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.