Skip to main content
VulnerabilityPublished Updated

CVE-2026-64048: Linux kernel · NULL Pointer Dereference

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0, d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0, afa9036b8c9963947b487c36e332df6a42c96fcb +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a7c9c5f4af7f6098da68705fc5d86565d0728ef7, < dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0
Fixed in
  • dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0
LinuxLinuxAffected
  • ≥ a7c9c5f4af7f6098da68705fc5d86565d0728ef7, < d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0
Fixed in
  • d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0
LinuxLinuxAffected
  • ≥ a7c9c5f4af7f6098da68705fc5d86565d0728ef7, < afa9036b8c9963947b487c36e332df6a42c96fcb
Fixed in
  • afa9036b8c9963947b487c36e332df6a42c96fcb
LinuxLinuxAffected
  • ≥ a7c9c5f4af7f6098da68705fc5d86565d0728ef7, < 277740023def559a4a2ddc3e8e784ee37a0f16a9
Fixed in
  • 277740023def559a4a2ddc3e8e784ee37a0f16a9
LinuxLinuxAffected
  • ≥ a7c9c5f4af7f6098da68705fc5d86565d0728ef7, < 6927cacf2b10d4fa80c1a2d407512ef9397c59c6
Fixed in
  • 6927cacf2b10d4fa80c1a2d407512ef9397c59c6
LinuxLinuxAffected
  • ≥ a7c9c5f4af7f6098da68705fc5d86565d0728ef7, < 903f7688ffeb9b323d70652c01f554bd4ba2a3d6
Fixed in
  • 903f7688ffeb9b323d70652c01f554bd4ba2a3d6

Description

In the Linux kernel, the following vulnerability has been resolved: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot On the SMC-D client, slot 0 of ini->ism_dev[]/ini->ism_chid[] is reserved for an SMC-Dv1 device. smc_find_ism_v2_device_clnt() populates V2 entries starting at index 1, so when no V1 device is selected slot 0 is left in its kzalloc()'ed state with ism_dev[0] == NULL and ism_chid[0] == 0. smc_v2_determine_accepted_chid() then matches the peer's CHID against the array starting from index 0 using the CHID alone. A malicious peer replying to a SMC-Dv2-only proposal with d1.chid == 0 matches the empty slot, ini->ism_selected becomes 0, and the subsequent ism_dev[0]->lgr_lock dereference in smc_conn_create() faults at offsetof(struct smcd_dev, lgr_lock) == 0x68: BUG: KASAN: null-ptr-deref in _raw_spin_lock_bh+0x79/0xe0 Write of size 4 at addr 0000000000000068 by task exploit/144 Call Trace: _raw_spin_lock_bh smc_conn_create (net/smc/smc_core.c:1997) __smc_connect (net/smc/af_smc.c:1447) smc_connect (net/smc/af_smc.c:1720) __sys_connect __x64_sys_connect do_syscall_64 Require ism_dev[i] to be non-NULL before accepting a CHID match.

References

Community reviews

Loading reviews…