Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
Permalink CVE-2026-64005
7.8 HIGH
  • CVSS version (CVSS): 3.1
  • Attack Vector (AV): Local (L)
  • Attack Complexity (AC): Low (L)
  • Privileges Required (PR): Low (L)
  • User Interaction (UI): None (N)
  • Scope (S): Unchanged (U)
  • Confidentiality (C): High (H)
  • Integrity (I): High (H)
  • Availability (A): High (H)
  • Modified Attack Vector (MAV): Local (L)
  • Modified Attack Complexity (MAC): Low (L)
  • Modified Privileges Required (MPR): Low (L)
  • Modified User Interaction (MUI): None (N)
  • Modified Confidentiality (MC): High (H)
  • Modified Scope (MS): Unchanged (U)
  • Modified Integrity (MI): High (H)
  • Modified Availability (MA): High (H)
created 6 days, 9 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
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.

Affected products

Linux
  • <4.11
  • <cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
  • <5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
  • <9e4389b0038781f19f97895186ed941ff8ac1678
  • =<6.18.*
  • <ed7a758313011885347b854e97cb95903ef3c3f7
  • =<7.0.*
  • ==4.11
  • =<6.12.*
  • <64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
  • =<6.1.*
  • =<6.6.*
  • <55cba6b883b41e5922c00ba9d4e3262131f46f1b
  • =<*
  • =<5.15.*
  • <0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d
  • <2006605006e5a4a11d93e1ebdbbe95764d24276f
  • =<5.10.*