Kernel crash via NULL receive-buffer dereference
Published Dec 16, 2025 · Updated Dec 16, 2025
NULL-pointer dereference in the Linux SXGBE network driver allows remote attackers to crash affected kernels via network traffic. In sxgbe_rx(), a failed receive-buffer allocation leaves skb NULL, but the error path logs the failure and immediately dereferences skb instead of transferring control to sxgbe_rx_refill(). An active SXGBE interface and sustained unauthenticated traffic that exhausts GFP_ATOMIC receive-buffer allocation are required; the resulting oops or panic interrupts the host.
Summary
What happened
NULL-pointer dereference in the Linux SXGBE network driver allows remote attackers to crash affected kernels via network traffic. In sxgbe_rx(), a failed receive-buffer allocation leaves skb NULL, but the error path logs the failure and immediately dereferences skb instead of transferring control to sxgbe_rx_refill(). An active SXGBE interface and sustained unauthenticated traffic that exhausts GFP_ATOMIC receive-buffer allocation are required; the resulting oops or panic interrupts the host.
The record
- CVE
- CVE-2025-68302
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1498
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record 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=1edb9ca69e8a7988900fc0283e10550b5592164d <18ef3ad1bb57dcf1a9ee61736039aedccf670b21
- Affected versionversion=1edb9ca69e8a7988900fc0283e10550b5592164d <45b5b4ddb8d6bea5fc1625ff6f163bbb125d49cc
- Affected versionversion=1edb9ca69e8a7988900fc0283e10550b5592164d <46e5332126596a2ca791140feab18ce1fc1a3c86
- Affected versionversion=1edb9ca69e8a7988900fc0283e10550b5592164d <7fd789d6ea4915034eb6bcb72f6883c8151083e5
- Affected versionversion=1edb9ca69e8a7988900fc0283e10550b5592164d <88f46c0be77bfe45830ac33102c75be7c34ac3f3
- Affected versionversion=1edb9ca69e8a7988900fc0283e10550b5592164d <ac171c3c755499c9f87fe30b920602255f8b5648
- Affected versionversion=1edb9ca69e8a7988900fc0283e10550b5592164d <f5bce28f6b9125502abec4a67d68eabcd24b3b17
- Affected versionversion=3.15
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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