Skip to main content

CVE-2022-48751: Vulnerability in Linux Linux

High
VulnerabilityCVE-2022-48751cvecve-2022-48751
Published: Thu Jun 20 2024 (06/20/2024, 11:13:32 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

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.

AI-Powered Analysis

AILast updated: 06/27/2025, 23:56:30 UTC

Technical Analysis

CVE-2022-48751 is a vulnerability found in the Linux kernel's SMC (Shared Memory Communications) subsystem, specifically within the net/smc module. The issue arises due to a race condition related to the handling of the clcsock (Connection Layer Control socket) object. The vulnerability manifests as a NULL pointer dereference in the smc_setsockopt() function when it attempts to access the clcsock after it has already been released. This leads to a kernel crash (BUG: kernel NULL pointer dereference) and a resulting denial of service (DoS) condition. The kernel oops trace indicates that the fault occurs during socket option setting system calls, such as setsockopt, which are common in networked applications like nginx. The patch introduced to fix this vulnerability involves acquiring a lock (clcsock_release_lock) before accessing the clcsock pointer and verifying whether the clcsock has been released to prevent use-after-free conditions. Additional checks were added in related functions smc_getsockopt() and smc_switch_to_fallback() to ensure robustness against similar race conditions. The vulnerability affects specific Linux kernel versions identified by commit hashes, and no known exploits are currently reported in the wild. The vulnerability does not have an assigned CVSS score yet.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions with the SMC module enabled and in use. The impact is a potential kernel crash leading to denial of service, which can disrupt critical services, especially those relying on networked applications like web servers (e.g., nginx) or other infrastructure components using SMC for high-performance communication. While this vulnerability does not appear to allow privilege escalation or remote code execution directly, the resulting DoS can affect availability of services, potentially impacting business operations, especially in sectors such as finance, healthcare, and critical infrastructure where Linux servers are prevalent. Additionally, if exploited in a targeted manner, it could be used to disrupt services during cyberattacks or ransomware campaigns. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially in environments where kernel updates are delayed.

Mitigation Recommendations

European organizations should prioritize updating their Linux kernels to versions that include the patch for CVE-2022-48751. Specifically, they should track kernel updates from their Linux distribution vendors and apply security patches promptly. For environments where immediate patching is not feasible, administrators should consider disabling the SMC module if it is not required, as this will eliminate the attack surface related to this vulnerability. Monitoring kernel logs for oops or crash reports related to smc_setsockopt or smc_getsockopt can help detect attempts to trigger this vulnerability. Additionally, implementing strict access controls and limiting the ability of unprivileged users or processes to invoke setsockopt calls on SMC sockets can reduce exploitation risk. Network segmentation and application-level protections should be employed to minimize exposure of vulnerable systems. Finally, organizations should maintain robust incident response plans to quickly address any service disruptions caused by kernel crashes.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-06-20T11:09:39.057Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9820c4522896dcbdd4ed

Added to database: 5/21/2025, 9:08:48 AM

Last enriched: 6/27/2025, 11:56:30 PM

Last updated: 8/15/2025, 12:47:23 PM

Views: 14

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats