CVE-2022-48751: net/smc: Transitional solution for clcsock race issue
In the Linux kernel, the following vulnerability has been resolved:
net/smc: Transitional solution for clcsock race issue
We encountered a crash in smc_setsockopt() and it is caused by
accessing smc->clcsock after clcsock was released.
BUG: kernel NULL pointer dereference, address: 0000000000000020
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP PTI
CPU: 1 PID: 50309 Comm: nginx Kdump: loaded Tainted: G E 5.16.0-rc4+ #53
RIP: 0010:smc_setsockopt+0x59/0x280 [smc]
Call Trace:
<TASK>
__sys_setsockopt+0xfc/0x190
__x64_sys_setsockopt+0x20/0x30
do_syscall_64+0x34/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f16ba83918e
</TASK>
This patch tries to fix it by holding clcsock_release_lock and
checking whether clcsock has already been released before access.
In case that a crash of the same reason happens in smc_getsockopt()
or smc_switch_to_fallback(), this patch also checkes smc->clcsock
in them too. And the caller of smc_switch_to_fallback() will identify
whether fallback succeeds according to the return value.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability and security issue in the SMC networking code. A race can leave the kernel using a released socket pointer, causing a kernel NULL pointer crash. The source does not show data theft, privilege escalation, or active exploitation, but affected production Linux systems could face availability risk.
Executive priority
Handle through normal kernel security maintenance, with faster scheduling for high-availability Linux workloads or environments using SMC. There is no source-backed evidence of active exploitation, but kernel crashes can still create business disruption.
Technical view
CVE-2022-48751 addresses a race in net/smc where smc_setsockopt(), and defensively smc_getsockopt() and smc_switch_to_fallback(), may access smc->clcsock after release. The upstream fix adds locking and release checks before dereferencing clcsock, changing fallback handling to report success or failure through return values.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the SMC subsystem available or used. The bundle lists Linux as affected and references stable kernel fixes, but does not provide distribution package mappings or CPEs.
Exploitation context
The CVE source describes a kernel crash observed during setsockopt handling. It does not identify public exploit code, active exploitation, KEV listing, remote reachability, or attacker prerequisites. Treat exploitation details as incomplete.
Researcher notes
The source evidence supports an availability-oriented kernel race in net/smc, not broader impact claims. Affected-version metadata is sparse and lacks CPEs, so distribution-specific validation is necessary before concluding exposure or remediation status.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check Linux distribution advisories for package-specific fixed versions.
Prioritize critical systems using SMC or affected kernel branches.
If patch timing is constrained, review vendor guidance for safe SMC risk reduction.
Validation and detection
Inventory Linux kernel versions across production and edge systems.
Check whether the SMC kernel module or subsystem is present or loaded.
Map installed kernels to distribution advisories or the referenced stable commits.
Review crash logs for NULL dereferences in smc_setsockopt or related SMC paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48751 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.