CVE-2022-48647
published 2024-04-28CVE-2022-48647: In the Linux kernel, the following vulnerability has been resolved: sfc: fix TX channel offset when using legacy interrupts In legacy interrupt mode the…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
13.3th percentile
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:
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:
dev_hard_start_xmit+0xd7/0x230
sch_direct_xmit+0x9f/0x360
__dev_queue_xmit+0x890/0xa40
[...]
Affected
21 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 | — | — |
| linux | linux | — | — |
| linux | linux | >= 06cb7e134f8f4a11b66f1dbeb5f237412a0aeedc < 360910b88d1466a90644a4e0533803b594344a2b | 360910b88d1466a90644a4e0533803b594344a2b |
| linux | linux | >= 5.10.122 < 5.10.146 | 5.10.146 |
| linux | linux | >= 5.15.47 < 5.15.71 | 5.15.71 |
| linux | linux | >= 5.17.15 < 5.18 | 5.18 |
| linux | linux | >= 5.18.4 < 5.19 | 5.19 |
| linux | linux | >= bf2af9b24313553f3f0b30443220ab0ac8595d2d < b4afd3878f961d3517f27b3213730fceef77945c | b4afd3878f961d3517f27b3213730fceef77945c |
| linux | linux | >= c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 < 5f623a77cfc2d501d72bcb4f9ee71721e6c766ff | 5f623a77cfc2d501d72bcb4f9ee71721e6c766ff |
| linux | linux | >= c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 < f232af4295653afa4ade3230462b3be15ad16419 | f232af4295653afa4ade3230462b3be15ad16419 |
| 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.122 < 5.10.146 | 5.10.146 |
| linux | linux_kernel | >= 5.15.47 < 5.15.71 | 5.15.71 |
| linux | linux_kernel | >= 5.17.15 < 5.18 | 5.18 |
| linux | linux_kernel | >= 5.18.4 < 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.
Red Hat
kernel: sfc: fix TX channel offset when using legacy interrupts
vendor_redhat·2024-04-28·CVSS 5.5
CVE-2022-48647 [MEDIUM] CWE-476 kernel: sfc: fix TX channel offset when using legacy interrupts
kernel: sfc: fix TX channel offset when using legacy interrupts
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:
dev_hard_start_xmit+0xd7/0x230
sch_direct_xm
Debian
CVE-2022-48647: linux - In the Linux kernel, the following vulnerability has been resolved: sfc: fix TX...
vendor_debian·2022·CVSS 5.5
CVE-2022-48647 [MEDIUM] CVE-2022-48647: linux - In the Linux kernel, the following vulnerability has been resolved: sfc: fix TX...
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: dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...] BUG: unable to ha
GHSA
GHSA-xxhf-v2m2-422x: In the Linux kernel, the following vulnerability has been resolved:
sfc: fix TX channel offset when using legacy interrupts
In legacy interrupt mode
ghsa_unreviewed·2024-04-28
CVE-2022-48647 GHSA-xxhf-v2m2-422x: In the Linux kernel, the following vulnerability has been resolved:
sfc: fix TX channel offset when using legacy interrupts
In legacy interrupt mode
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:
dev_hard_start_xmit+0xd7/0x230
sch_direct_xmit+0x9f/0x360
__dev_queue_xmit+0x890/0xa40
[...]
BUG: unable t
OSV
CVE-2022-48647: In the Linux kernel, the following vulnerability has been resolved: sfc: fix TX channel offset when using legacy interrupts In legacy interrupt mode t
osv·2024-04-28·CVSS 5.5
CVE-2022-48647 [MEDIUM] CVE-2022-48647: In the Linux kernel, the following vulnerability has been resolved: sfc: fix TX channel offset when using legacy interrupts In legacy interrupt mode t
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: dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...] BUG: unable to ha
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/360910b88d1466a90644a4e0533803b594344a2bhttps://git.kernel.org/stable/c/5f623a77cfc2d501d72bcb4f9ee71721e6c766ffhttps://git.kernel.org/stable/c/b4afd3878f961d3517f27b3213730fceef77945chttps://git.kernel.org/stable/c/f232af4295653afa4ade3230462b3be15ad16419https://git.kernel.org/stable/c/360910b88d1466a90644a4e0533803b594344a2bhttps://git.kernel.org/stable/c/5f623a77cfc2d501d72bcb4f9ee71721e6c766ffhttps://git.kernel.org/stable/c/b4afd3878f961d3517f27b3213730fceef77945chttps://git.kernel.org/stable/c/f232af4295653afa4ade3230462b3be15ad16419
2024-04-28
Published