CVE-2022-48647: sfc: fix TX channel offset when using legacy interrupts
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
[...]
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel network-driver flaw that can crash or disrupt systems using the sfc Ethernet driver under a specific legacy interrupt configuration. The source describes failure during outbound traffic, leading to warnings and a NULL pointer dereference. Evidence points to availability risk, not data theft or remote code execution.
Executive priority
Treat this as a targeted availability issue. It is most urgent for production Linux servers that rely on affected sfc network interfaces, especially where a kernel crash would interrupt revenue, operations, or security monitoring.
Technical view
The sfc driver used an incorrect TX channel offset in legacy interrupt mode when separate TX channels were disabled. Transmit traffic could access an uninitialized channel and hit efx_hard_start_xmit warnings followed by a kernel NULL pointer dereference. The issue is resolved by referenced Linux stable commits.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the sfc Ethernet driver and the described legacy interrupt configuration. General Linux hosts without this driver or configuration are not clearly exposed based on the supplied sources.
Exploitation context
CISA KEV is false in the bundle, and no cited source claims active exploitation. The described trigger is sending traffic through the affected driver path; the available evidence supports denial-of-service style impact rather than compromise.
Researcher notes
The public record lacks CVSS, CWE, and detailed distribution matrices. Analysis should stay tied to the driver path, affected kernel branches, and stable commits. Do not generalize this to all Linux networking or claim exploitation without new evidence.
Mitigation direction
Apply a vendor kernel update containing the referenced Linux stable sfc fix.
Prioritize systems using the sfc Ethernet driver or Solarflare-class NICs.
Check distribution advisories for backported fixes matching your kernel branch.
If patching is delayed, seek vendor guidance for configuration-specific workarounds.
Validation and detection
Inventory hosts loading the sfc driver and compare kernel versions to vendor advisories.
Review logs for efx_hard_start_xmit warnings or NULL pointer dereference traces.
Confirm patched kernels include one of the referenced stable commits or vendor backport.
Test outbound network traffic after patching on representative affected hardware.
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-48647 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.