Skip to main content

CVE-2022-48647: Vulnerability in Linux Linux

High
VulnerabilityCVE-2022-48647cvecve-2022-48647
Published: Sun Apr 28 2024 (04/28/2024, 13:00:19 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: sfc: fix TX channel offset when using legacy interrupts In legacy interrupt mode the tx_channel_offset was hardcoded to 1, but that's not correct if efx_sepparate_tx_channels is false. In that case, the offset is 0 because the tx queues are in the single existing channel at index 0, together with the rx queue. Without this fix, as soon as you try to send any traffic, it tries to get the tx queues from an uninitialized channel getting these errors: WARNING: CPU: 1 PID: 0 at drivers/net/ethernet/sfc/tx.c:540 efx_hard_start_xmit+0x12e/0x170 [sfc] [...] RIP: 0010:efx_hard_start_xmit+0x12e/0x170 [sfc] [...] Call Trace: <IRQ> dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [...] RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc] [...] Call Trace: <IRQ> dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...]

AI-Powered Analysis

AILast updated: 06/27/2025, 23:55:01 UTC

Technical Analysis

CVE-2022-48647 is a vulnerability identified in the Linux kernel's sfc network driver, specifically related to the handling of transmit (TX) channel offsets when using legacy interrupt mode. The issue arises because the tx_channel_offset was hardcoded to 1 regardless of the configuration of the efx_sepparate_tx_channels flag. When this flag is false, the TX queues reside in a single channel at index 0 alongside the receive (RX) queue, meaning the offset should be 0. Due to the incorrect hardcoded offset, attempts to send network traffic cause the driver to reference an uninitialized TX channel. This leads to kernel warnings and ultimately a NULL pointer dereference, causing a kernel crash or system instability. The vulnerability manifests as a BUG in the kernel, with call traces indicating failure in the efx_hard_start_xmit function within the sfc driver. This flaw affects multiple Linux kernel versions identified by specific commit hashes. The root cause is a logic error in channel offset calculation under legacy interrupt mode, which can be triggered simply by sending network traffic on affected systems. There are no known exploits in the wild at the time of publication, and no CVSS score has been assigned yet. However, the vulnerability can cause denial of service (DoS) through kernel crashes, impacting system availability. The fix involves correcting the tx_channel_offset calculation to reflect the actual channel configuration, preventing the driver from accessing invalid memory.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions with the sfc network driver in legacy interrupt mode. The impact is mainly on system availability due to potential kernel crashes triggered by normal network traffic transmission. This can disrupt critical services, especially in environments relying on Linux servers for networking, cloud infrastructure, or telecommunications. Organizations operating data centers, cloud platforms, or network appliances using Solarflare network cards (which the sfc driver supports) could experience service interruptions or downtime. Although no remote code execution or privilege escalation is indicated, the denial of service can affect business continuity, incident response, and operational stability. Given the widespread use of Linux in European enterprises and public sector infrastructure, the vulnerability could have broad implications if exploited or triggered unintentionally. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to accidental crashes or targeted DoS attempts.

Mitigation Recommendations

To mitigate CVE-2022-48647, European organizations should: 1) Identify Linux systems using the sfc network driver, particularly those operating in legacy interrupt mode with efx_sepparate_tx_channels set to false. 2) Apply the official Linux kernel patches or updates that correct the tx_channel_offset calculation as soon as they become available. Monitor Linux kernel mailing lists and vendor advisories for patch releases. 3) If immediate patching is not possible, consider disabling legacy interrupt mode or reconfiguring network driver settings to avoid triggering the vulnerable code path. 4) Implement robust monitoring for kernel warnings or crashes related to the sfc driver to detect potential exploitation or accidental triggers. 5) Test patches in staging environments to ensure compatibility and stability before deployment. 6) Coordinate with hardware vendors (e.g., Solarflare) for firmware or driver updates that may complement kernel fixes. 7) Maintain up-to-date backups and incident response plans to recover quickly from potential DoS events caused by this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-02-25T13:44:28.316Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9820c4522896dcbdd4c3

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

Last enriched: 6/27/2025, 11:55:01 PM

Last updated: 7/26/2025, 4:57:03 AM

Views: 11

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