Skip to main content

CVE-2022-49456: Vulnerability in Linux Linux

High
VulnerabilityCVE-2022-49456cvecve-2022-49456
Published: Wed Feb 26 2025 (02/26/2025, 02:13:04 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: bonding: fix missed rcu protection When removing the rcu_read_lock in bond_ethtool_get_ts_info() as discussed [1], I didn't notice it could be called via setsockopt, which doesn't hold rcu lock, as syzbot pointed: stack backtrace: CPU: 0 PID: 3599 Comm: syz-executor317 Not tainted 5.18.0-rc5-syzkaller-01392-g01f4685797a5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 bond_option_active_slave_get_rcu include/net/bonding.h:353 [inline] bond_ethtool_get_ts_info+0x32c/0x3a0 drivers/net/bonding/bond_main.c:5595 __ethtool_get_ts_info+0x173/0x240 net/ethtool/common.c:554 ethtool_get_phc_vclocks+0x99/0x110 net/ethtool/common.c:568 sock_timestamping_bind_phc net/core/sock.c:869 [inline] sock_set_timestamping+0x3a3/0x7e0 net/core/sock.c:916 sock_setsockopt+0x543/0x2ec0 net/core/sock.c:1221 __sys_setsockopt+0x55e/0x6a0 net/socket.c:2223 __do_sys_setsockopt net/socket.c:2238 [inline] __se_sys_setsockopt net/socket.c:2235 [inline] __x64_sys_setsockopt+0xba/0x150 net/socket.c:2235 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 RIP: 0033:0x7f8902c8eb39 Fix it by adding rcu_read_lock and take a ref on the real_dev. Since dev_hold() and dev_put() can take NULL these days, we can skip checking if real_dev exist. [1] https://lore.kernel.org/netdev/27565.1642742439@famine/

AI-Powered Analysis

AILast updated: 06/30/2025, 07:28:23 UTC

Technical Analysis

CVE-2022-49456 is a vulnerability identified in the Linux kernel's bonding driver, specifically related to the function bond_ethtool_get_ts_info(). The issue arises from a missing Read-Copy-Update (RCU) protection when this function is called via the setsockopt system call, which does not hold the RCU lock. The bonding driver aggregates multiple network interfaces into a single logical interface for redundancy or increased throughput. The vulnerability was introduced when the rcu_read_lock was removed from bond_ethtool_get_ts_info(), without recognizing that this function could be invoked through setsockopt without the necessary RCU lock held. This omission can lead to unsafe concurrent access to shared data structures, potentially causing use-after-free or data corruption scenarios. The kernel stack trace provided shows the call path leading to the vulnerability, highlighting that the setsockopt syscall invokes bond_ethtool_get_ts_info() without proper synchronization. The fix involves re-adding the rcu_read_lock and taking a reference on the real_dev device structure to ensure safe access. Since dev_hold() and dev_put() can now handle NULL pointers, the fix simplifies the check for the existence of real_dev. This vulnerability affects Linux kernel versions containing the specified commit hashes and is relevant to systems using the bonding driver for network interface aggregation. No known exploits are reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, the impact of CVE-2022-49456 depends largely on their deployment of Linux systems utilizing the bonding driver for network interface aggregation. Bonding is commonly used in enterprise environments to enhance network reliability and performance. Exploitation of this vulnerability could lead to kernel memory corruption, potentially causing system instability, crashes, or privilege escalation if an attacker can manipulate the bonding interface via setsockopt calls. This could disrupt critical network services, affecting availability and potentially confidentiality and integrity if attackers gain elevated privileges. Given that Linux is widely used in European data centers, cloud infrastructures, and enterprise servers, organizations relying on bonded network interfaces may face operational risks. However, exploitation requires local or remote code execution capabilities to invoke setsockopt with crafted parameters, which may limit the attack surface. The absence of known exploits suggests the threat is currently theoretical but warrants proactive mitigation to prevent future attacks. Disruptions in network bonding could impact sectors such as finance, telecommunications, and government services, where high network availability is essential.

Mitigation Recommendations

European organizations should prioritize updating their Linux kernels to versions that include the patch fixing CVE-2022-49456. Specifically, they should apply the kernel updates that reintroduce the rcu_read_lock protection in bond_ethtool_get_ts_info() and ensure proper reference counting on real_dev. System administrators should audit their environments to identify systems using the bonding driver and verify kernel versions. For environments where immediate patching is not feasible, consider restricting access to setsockopt system calls related to network interfaces via mandatory access controls (e.g., SELinux, AppArmor) or seccomp filters to limit potential exploitation. Network segmentation and strict user privilege management can reduce the risk of unauthorized invocation of vulnerable calls. Monitoring kernel logs for unusual bonding driver activity and implementing intrusion detection systems that can flag anomalous setsockopt usage may help detect exploitation attempts. Additionally, organizations should maintain an inventory of Linux kernel versions and bonding configurations to facilitate rapid response to emerging threats.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-02-26T02:08:31.574Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d982ec4522896dcbe5aa4

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

Last enriched: 6/30/2025, 7:28:23 AM

Last updated: 8/13/2025, 1:19:41 AM

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