CVE-2022-48647
sfc: fix TX channel offset when using legacy interrupts
- Published
- Updated
- Reserved
- Assigned by
- 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 [...]
Timeline
ID reserved
By Linux
- 2 months later
· 2 months later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.23% · top 87% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected bf2af9b24313553f3f0b30443220ab0ac8595d2d – < b4afd3878f961d3517f27b3213730fceef77945c
- affected 06cb7e134f8f4a11b66f1dbeb5f237412a0aeedc – < 360910b88d1466a90644a4e0533803b594344a2b
- affected c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 – < 5f623a77cfc2d501d72bcb4f9ee71721e6c766ff
- affected c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 – < f232af4295653afa4ade3230462b3be15ad16419
- affected 1a7c0b3ef93d1d1dae7b0a85dab3ac6e3ad0ef61
- affected b2d60329a0b88c4e35017436ee29c43be59d46a5
- affected 5.10.122 – < 5.10.146
- affected 5.15.47 – < 5.15.71
- affected 5.17.15 – < 5.18
- affected 5.18.4 – < 5.19
- affected 5.19
- unaffected < 5.19
- unaffected 5.10.146 – ≤ 5.10.*
- unaffected 5.15.71 – ≤ 5.15.*
- unaffected 5.19.12 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References (4)
- https://git.kernel.org/stable/c/b4afd3878f961d3517f27b3213730fceef77945c (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/360910b88d1466a90644a4e0533803b594344a2b (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/5f623a77cfc2d501d72bcb4f9ee71721e6c766ff (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/f232af4295653afa4ade3230462b3be15ad16419 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-48647)Record last updated .