CVE-2026-64048·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.11
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.50% — higher than 41% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-64048 scores 7.5 on CVSS, so a successful attack would be serious — but at 0.50%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.11
Fixed in: 7.0.11
How to fix this CVE
Update your Linux kernel to version 7.0.11 or later to patch a null pointer dereference vulnerability in SMC-D network protocol handling. This vulnerability allows a malicious peer to trigger a kernel panic by sending a specially crafted CHID value during connection establishment. Apply the update immediately to systems using kernel versions 6.19 through 7.0.10.
sudo dnf update kernel kernel-devel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version by running `uname -r` and compare against 7.0.11 (affected versions are 6.19 to 7.0.10)
- Step 2: Verify SMC-D (Shared Memory Communications over RDMA) is enabled in your kernel configuration by checking `grep -i smc /boot/config-$(uname -r)` for CONFIG_SMC=m or CONFIG_SMC=y
- Step 3: Search system logs for KASAN null-ptr-deref errors related to smc_conn_create or _raw_spin_lock_bh using `sudo journalctl -xe | grep -i 'kasan\|smc_conn_create\|null-ptr'`
- Step 4: After patching, confirm the new kernel version is running with `uname -r` and verify it is 7.0.11 or newer
FAQ
What is CVE-2026-64048?
This is a null pointer dereference vulnerability in the Linux kernel's SMC-D (Shared Memory Communications over RDMA) implementation that occurs when validating channel IDs during connection acceptance, allowing a malicious network peer to crash the kernel.
Is CVE-2026-64048 being actively exploited?
No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available, though the vulnerability can be triggered remotely without authentication.
What versions of Kernel are affected by CVE-2026-64048?
Linux kernel versions 6.19 through 7.0.10 are vulnerable; the fix was released in kernel version 7.0.11 and backported to stable branches.
How do I check if my server is vulnerable to CVE-2026-64048?
Run `uname -r` to check your kernel version and verify it is earlier than 7.0.11, then confirm SMC support is compiled in using `grep CONFIG_SMC /boot/config-$(uname -r)`.
Does Defensia detect CVE-2026-64048?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-64048 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/277740023def559a4a2ddc3e8e784ee37a0f16a9
- https://git.kernel.org/stable/c/53eb7bd09aace72fa17510d80e0caf5ca058c231
- https://git.kernel.org/stable/c/65edb3b0822cfe5041be8fbabebd57e2e5ad9f4e
- https://git.kernel.org/stable/c/6927cacf2b10d4fa80c1a2d407512ef9397c59c6
- https://git.kernel.org/stable/c/903f7688ffeb9b323d70652c01f554bd4ba2a3d6
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-64048. Free for 1 server.
Get started free