# CVE-2022-48648: linux: In the Linux kernel, the following vulnerability has been resolved:  sfc: fix null pointer dereference in efx_hard_st...

CVE-2022-48648 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-48648, released April 28, 2024. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2022-48648
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0023
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Apr 28, 2024

## 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]

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 6.0.2-1 | [DEBIAN-CVE-2022-48648](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48648.md) | Apr 28, 2024 |
| Linux | linux Debian 13.5 (trixie) | 6.0.2-1 | [DEBIAN-CVE-2022-48648](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48648.md) | Apr 28, 2024 |
| Linux | linux Debian 14 | 6.0.2-1 | [DEBIAN-CVE-2022-48648](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48648.md) | Apr 28, 2024 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.