Riskcovery

CVE-2022-48647

sfc: fix TX channel offset when using legacy interrupts

State
Published
Severity
Not scored
Published
Apr 28, 2024
Updated
May 23, 2026
Reserved
Feb 25, 2024

Read the record on cve.org

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 [...]

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • bf2af9b24313553f3f0b30443220ab0ac8595d2d to before b4afd3878f961d3517f27b3213730fceef77945cAffected
  • 06cb7e134f8f4a11b66f1dbeb5f237412a0aeedc to before 360910b88d1466a90644a4e0533803b594344a2bAffected
  • c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 to before 5f623a77cfc2d501d72bcb4f9ee71721e6c766ffAffected
  • c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 to before f232af4295653afa4ade3230462b3be15ad16419Affected
  • 1a7c0b3ef93d1d1dae7b0a85dab3ac6e3ad0ef61Affected
  • b2d60329a0b88c4e35017436ee29c43be59d46a5Affected
  • 5.10.122 to before 5.10.146Affected
  • 5.15.47 to before 5.15.71Affected
  • 5.17.15 to before 5.18Affected
  • 5.18.4 to before 5.19Affected
LinuxLinux
  • 5.19Affected
  • before 5.19Not affected
  • 5.10.146 through 5.10.*Not affected
  • 5.15.71 through 5.15.*Not affected
  • 5.19.12 through 5.19.*Not affected
  • 6.0 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.