Skip to main content

CVE-2022-48726: Vulnerability in Linux Linux

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

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/ucma: Protect mc during concurrent multicast leaves Partially revert the commit mentioned in the Fixes line to make sure that allocation and erasing multicast struct are locked. BUG: KASAN: use-after-free in ucma_cleanup_multicast drivers/infiniband/core/ucma.c:491 [inline] BUG: KASAN: use-after-free in ucma_destroy_private_ctx+0x914/0xb70 drivers/infiniband/core/ucma.c:579 Read of size 8 at addr ffff88801bb74b00 by task syz-executor.1/25529 CPU: 0 PID: 25529 Comm: syz-executor.1 Not tainted 5.16.0-rc7-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0x8d/0x320 mm/kasan/report.c:247 __kasan_report mm/kasan/report.c:433 [inline] kasan_report.cold+0x83/0xdf mm/kasan/report.c:450 ucma_cleanup_multicast drivers/infiniband/core/ucma.c:491 [inline] ucma_destroy_private_ctx+0x914/0xb70 drivers/infiniband/core/ucma.c:579 ucma_destroy_id+0x1e6/0x280 drivers/infiniband/core/ucma.c:614 ucma_write+0x25c/0x350 drivers/infiniband/core/ucma.c:1732 vfs_write+0x28e/0xae0 fs/read_write.c:588 ksys_write+0x1ee/0x250 fs/read_write.c:643 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae Currently the xarray search can touch a concurrently freeing mc as the xa_for_each() is not surrounded by any lock. Rather than hold the lock for a full scan hold it only for the effected items, which is usually an empty list.

AI-Powered Analysis

AILast updated: 06/30/2025, 19:43:08 UTC

Technical Analysis

CVE-2022-48726 is a use-after-free vulnerability in the Linux kernel's RDMA (Remote Direct Memory Access) subsystem, specifically within the UCMA (Userspace Communication Management API) multicast handling code. The vulnerability arises due to improper synchronization when managing multicast group membership during concurrent leave operations. The root cause is that the xarray data structure used to track multicast groups can be accessed concurrently without proper locking, leading to a race condition where the kernel attempts to access multicast structures that have already been freed. This results in use-after-free bugs detected by Kernel Address Sanitizer (KASAN), as evidenced by the bug reports showing invalid memory reads in functions such as ucma_cleanup_multicast and ucma_destroy_private_ctx. The vulnerability was introduced by a previous commit that partially reverted a fix, removing necessary locking around allocation and erasure of multicast structures. The fix involves reintroducing locking mechanisms to protect the multicast structures during concurrent modifications, but only holding locks for the affected items to avoid performance degradation. This vulnerability affects Linux kernel versions containing the specified commit hashes, and it is relevant to systems using RDMA with UCMA multicast features, commonly found in high-performance computing and data center environments. Although no known exploits are reported in the wild, the vulnerability could potentially be triggered by local users or processes with access to RDMA interfaces, leading to kernel crashes or potential escalation of privileges due to memory corruption.

Potential Impact

For European organizations, especially those operating data centers, cloud infrastructure, or high-performance computing clusters that utilize Linux kernels with RDMA capabilities, this vulnerability poses a risk of system instability and denial of service through kernel crashes. The use-after-free condition could also be leveraged by attackers with local access to cause memory corruption, potentially leading to privilege escalation or arbitrary code execution within the kernel context. This is particularly critical for sectors relying on Linux-based infrastructure for sensitive operations, such as financial institutions, research centers, and telecommunications providers. The impact is heightened in environments where RDMA is used for low-latency, high-throughput networking, as exploitation could disrupt critical communication channels. Although exploitation requires local access and specific RDMA usage, the widespread deployment of Linux in European enterprise and cloud environments means that unpatched systems could be vulnerable to insider threats or compromised containers/VMs that gain access to RDMA interfaces.

Mitigation Recommendations

European organizations should prioritize patching Linux kernels to versions that include the fix for CVE-2022-48726. Given the complexity of RDMA environments, administrators should audit their systems to identify hosts running affected kernel versions with RDMA UCMA multicast enabled. Specific mitigation steps include: 1) Applying vendor-provided kernel updates or backported patches that restore proper locking in multicast management; 2) Restricting access to RDMA interfaces to trusted users and processes only, minimizing the attack surface; 3) Implementing strict container and VM isolation policies to prevent untrusted code from accessing RDMA devices; 4) Monitoring kernel logs and using tools like KASAN or other memory error detectors in testing environments to detect potential use-after-free conditions; 5) Reviewing and hardening system configurations related to multicast group management and RDMA usage; 6) Engaging with Linux distribution security advisories to track patch availability and deployment status. Since no known exploits exist, proactive patching and access control are the most effective defenses.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 682d982ec4522896dcbe5f95

Added to database: 5/21/2025, 9:09:02 AM

Last enriched: 6/30/2025, 7:43:08 PM

Last updated: 8/2/2025, 7:11:13 AM

Views: 13

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