CVE-2022-48647

In legacy interrupt mode the txchanneloffset was hardcoded to 1, but that's not correct if efxsepparatetx_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 efxhardstartxmit+0x12e/0x170 [sfc] [...] RIP: 0010:efxhardstartxmit+0x12e/0x170 [sfc] [...] Call Trace: <IRQ> devhardstartxmit+0xd7/0x230 schdirect_xmit+0x9f/0x360 __devqueuexmit+0x890/0xa40 [...] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [...] RIP: 0010:efxhardstartxmit+0x153/0x170 [sfc] [...] Call Trace: <IRQ> devhardstartxmit+0xd7/0x230 schdirectxmit+0x9f/0x360 __devqueuexmit+0x890/0xa40 [...]

Database specific

{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48647.json",
    "cna_assigner": "Linux"
}

References

Affected packages

Linux / Kernel

Package

Name: Kernel

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

5.10.146

Type: ECOSYSTEM
Events: Introduced

5.11.0

Fixed

5.15.71

Type: ECOSYSTEM
Events: Introduced

5.16.0

Fixed

5.19.12

Database specific

source

"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-48647.json"