CVE-2022-48648
sfc: fix null pointer dereference in efx_hard_start_xmit
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: sfc: fix null pointer dereference in efx_hard_start_xmit Trying to get the channel from the tx_queue variable here is wrong because we can only be here if tx_queue is NULL, so we shouldn't dereference it. As the above comment in the code says, this is very unlikely to happen, but it's wrong anyway so let's fix it. I hit this issue because of a different bug that caused tx_queue to be NULL. If that happens, this is the error message that we get here: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [...] RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc]
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 12804793b17c0e19115a90d98f2f3df0cb79e233 – < b3b41d4d95d3822b2e459ecbc80d030ea6aec5e7
- affected 12804793b17c0e19115a90d98f2f3df0cb79e233 – < 8547c7bfc0617e7184e4da65b9b96681fcfe9998
- affected 12804793b17c0e19115a90d98f2f3df0cb79e233 – < b3b952168ee1f220ba729fa100fd9d5aa752eb03
- affected 12804793b17c0e19115a90d98f2f3df0cb79e233 – < 0a242eb2913a4aa3d6fbdb86559f27628e9466f3
- affected 5.10
- unaffected < 5.10
- 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/b3b41d4d95d3822b2e459ecbc80d030ea6aec5e7 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/8547c7bfc0617e7184e4da65b9b96681fcfe9998 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/b3b952168ee1f220ba729fa100fd9d5aa752eb03 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/0a242eb2913a4aa3d6fbdb86559f27628e9466f3 (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-48648)Record last updated .