Kernel crash via incorrect TX channel offset
Published Apr 28, 2024 · Updated May 23, 2026
NULL pointer dereference in the Linux sfc driver allows local users to crash the kernel by transmitting traffic under legacy interrupts. The legacy-interrupt path hardcodes tx_channel_offset to 1 when efx_separate_tx_channels is false, so efx_hard_start_xmit reads TX queues from an uninitialized channel. Reachability requires a local low-privileged user, an sfc device using legacy interrupts, shared TX and RX channels, and transmitted traffic; the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux sfc driver allows local users to crash the kernel by transmitting traffic under legacy interrupts. The legacy-interrupt path hardcodes tx_channel_offset to 1 when efx_separate_tx_channels is false, so efx_hard_start_xmit reads TX queues from an uninitialized channel. Reachability requires a local low-privileged user, an sfc device using legacy interrupts, shared TX and RX channels, and transmitted traffic; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2022-48647
- Published
- Apr 28, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=06cb7e134f8f4a11b66f1dbeb5f237412a0aeedc <360910b88d1466a90644a4e0533803b594344a2b
- Affected versionversion=1a7c0b3ef93d1d1dae7b0a85dab3ac6e3ad0ef61
- Affected versionversion=5.10.122 <5.10.146
- Affected versionversion=5.15.47 <5.15.71
- Affected versionversion=5.17.15 <5.18
- Affected versionversion=5.18.4 <5.19
- Affected versionversion=5.19
- Affected versionversion=b2d60329a0b88c4e35017436ee29c43be59d46a5
- Affected versionversion=bf2af9b24313553f3f0b30443220ab0ac8595d2d <b4afd3878f961d3517f27b3213730fceef77945c
- Affected versionversion=c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 <5f623a77cfc2d501d72bcb4f9ee71721e6c766ff
- Affected versionversion=c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 <f232af4295653afa4ade3230462b3be15ad16419
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo