CVE-2022-48648
published 2024-04-28CVE-2022-48648: 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…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
13.3th percentile
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]
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.2-1 (bookworm) | linux 6.0.2-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 12804793b17c0e19115a90d98f2f3df0cb79e233 < b3b41d4d95d3822b2e459ecbc80d030ea6aec5e7 | b3b41d4d95d3822b2e459ecbc80d030ea6aec5e7 |
| linux | linux | >= 12804793b17c0e19115a90d98f2f3df0cb79e233 < 8547c7bfc0617e7184e4da65b9b96681fcfe9998 | 8547c7bfc0617e7184e4da65b9b96681fcfe9998 |
| linux | linux | >= 12804793b17c0e19115a90d98f2f3df0cb79e233 < b3b952168ee1f220ba729fa100fd9d5aa752eb03 | b3b952168ee1f220ba729fa100fd9d5aa752eb03 |
| linux | linux | >= 12804793b17c0e19115a90d98f2f3df0cb79e233 < 0a242eb2913a4aa3d6fbdb86559f27628e9466f3 | 0a242eb2913a4aa3d6fbdb86559f27628e9466f3 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.148-1 | 5.10.148-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 5.10 < 5.10.146 | 5.10.146 |
| linux | linux_kernel | >= 5.11 < 5.15.71 | 5.15.71 |
| linux | linux_kernel | >= 5.16 < 5.19.12 | 5.19.12 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-48648: 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
osv·2024-04-28·CVSS 5.5
CVE-2022-48648 [MEDIUM] CVE-2022-48648: 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
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]
GHSA
GHSA-559c-j26r-95qc: In the Linux kernel, the following vulnerability has been resolved:
sfc: fix null pointer dereference in efx_hard_start_xmit
Trying to get the chann
ghsa_unreviewed·2024-04-28
CVE-2022-48648 [MEDIUM] CWE-476 GHSA-559c-j26r-95qc: In the Linux kernel, the following vulnerability has been resolved:
sfc: fix null pointer dereference in efx_hard_start_xmit
Trying to get the chann
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]
Red Hat
kernel: sfc: fix null pointer dereference in efx_hard_start_xmit
vendor_redhat·2024-04-28·CVSS 5.5
CVE-2022-48648 [MEDIUM] CWE-476 kernel: sfc: fix null pointer dereference in efx_hard_start_xmit
kernel: sfc: fix null pointer dereference in efx_hard_start_xmit
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]
A potential NULL pointer dereference was found in efx_hard_start_xmit in the Linux
Debian
CVE-2022-48648: linux - In the Linux kernel, the following vulnerability has been resolved: sfc: fix nu...
vendor_debian·2022·CVSS 5.5
CVE-2022-48648 [MEDIUM] CVE-2022-48648: linux - In the Linux kernel, the following vulnerability has been resolved: sfc: fix nu...
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]
Scope: local
bookworm: resolved (fixed in 6.0.2-1)
bullseye: resolved (fixed in 5.10.148-1)
forky: resolved (fixed in 6.0.2-1)
sid: resolved (fixed in
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0a242eb2913a4aa3d6fbdb86559f27628e9466f3https://git.kernel.org/stable/c/8547c7bfc0617e7184e4da65b9b96681fcfe9998https://git.kernel.org/stable/c/b3b41d4d95d3822b2e459ecbc80d030ea6aec5e7https://git.kernel.org/stable/c/b3b952168ee1f220ba729fa100fd9d5aa752eb03https://git.kernel.org/stable/c/0a242eb2913a4aa3d6fbdb86559f27628e9466f3https://git.kernel.org/stable/c/8547c7bfc0617e7184e4da65b9b96681fcfe9998https://git.kernel.org/stable/c/b3b41d4d95d3822b2e459ecbc80d030ea6aec5e7https://git.kernel.org/stable/c/b3b952168ee1f220ba729fa100fd9d5aa752eb03
2024-04-28
Published