CVE-2022-48647

Summary

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

Affected Software

VendorProductVersion RangeStatus
LinuxLinuxbf2af9b24313553f3f0b30443220ab0ac8595d2d < b4afd3878f961d3517f27b3213730fceef77945caffected
LinuxLinux06cb7e134f8f4a11b66f1dbeb5f237412a0aeedc < 360910b88d1466a90644a4e0533803b594344a2baffected
LinuxLinuxc308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 < 5f623a77cfc2d501d72bcb4f9ee71721e6c766ffaffected
LinuxLinuxc308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 < f232af4295653afa4ade3230462b3be15ad16419affected
LinuxLinux1a7c0b3ef93d1d1dae7b0a85dab3ac6e3ad0ef61affected
LinuxLinuxb2d60329a0b88c4e35017436ee29c43be59d46a5affected
LinuxLinux5.10.122 < 5.10.146affected
LinuxLinux5.15.47 < 5.15.71affected
LinuxLinux5.17.15 < 5.18affected
LinuxLinux5.18.4 < 5.19affected
LinuxLinux5.19affected
LinuxLinux0 < 5.19unaffected
LinuxLinux5.10.146 <= 5.10.*unaffected
LinuxLinux5.15.71 <= 5.15.*unaffected
LinuxLinux5.19.12 <= 5.19.*unaffected
LinuxLinux6.0 <= *unaffected

Weaknesses

ADP Enrichment

CISA ADP Vulnrichment

  • SSVC:
  • Exploitation: none
    • Automatable: no
    • Technical Impact: partial

CVE Program Container

Additional References

References