In the Linux kernel, the following vulnerability has been resolved: net: sxgbe: fix potential NULL dereference in sxgbe_rx() Currently, when skb is… (CVE-2025-68302)
A high-severity vulnerability in the Linux kernel's sxgbe network driver involves a potential NULL pointer dereference in the sxgbe_rx() function. When the skb pointer is null, the driver logs an error but then dereferences skb without proper handling, leading to a possible denial of service. The issue was identified during a code review and fixed by adding a break statement after the error message to avoid dereferencing null pointers, aligning with approaches used in similar drivers.
AI Analysis
Technical Summary
The Linux kernel's sxgbe network driver contained a vulnerability where, if the skb (socket buffer) pointer was null, the driver would print an error message but then proceed to dereference the null pointer in the sxgbe_rx() function. This could cause a kernel crash or denial of service. The fix involved adding a break statement after the error message to prevent further dereferencing and to switch to the sxgbe_rx_refill() function, similar to fixes in other drivers like calxeda's xgmac_rx(). This vulnerability was found during a code review and has been resolved.
Potential Impact
This vulnerability can lead to a denial of service condition by causing a kernel crash when the sxgbe_rx() function dereferences a null skb pointer. There is no indication of confidentiality or integrity impact. No known exploits are reported in the wild.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by adding a break statement to prevent null pointer dereference in the sxgbe_rx() function. Users should update to the fixed kernel version once available. Patch status is not yet confirmed — check the vendor advisory or Linux kernel mailing lists for the current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: net: sxgbe: fix potential NULL dereference in sxgbe_rx() Currently, when skb is… (CVE-2025-68302)
Description
A high-severity vulnerability in the Linux kernel's sxgbe network driver involves a potential NULL pointer dereference in the sxgbe_rx() function. When the skb pointer is null, the driver logs an error but then dereferences skb without proper handling, leading to a possible denial of service. The issue was identified during a code review and fixed by adding a break statement after the error message to avoid dereferencing null pointers, aligning with approaches used in similar drivers.
CVSS v3.1
Score 7.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's sxgbe network driver contained a vulnerability where, if the skb (socket buffer) pointer was null, the driver would print an error message but then proceed to dereference the null pointer in the sxgbe_rx() function. This could cause a kernel crash or denial of service. The fix involved adding a break statement after the error message to prevent further dereferencing and to switch to the sxgbe_rx_refill() function, similar to fixes in other drivers like calxeda's xgmac_rx(). This vulnerability was found during a code review and has been resolved.
Potential Impact
This vulnerability can lead to a denial of service condition by causing a kernel crash when the sxgbe_rx() function dereferences a null skb pointer. There is no indication of confidentiality or integrity impact. No known exploits are reported in the wild.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by adding a break statement to prevent null pointer dereference in the sxgbe_rx() function. Users should update to the fixed kernel version once available. Patch status is not yet confirmed — check the vendor advisory or Linux kernel mailing lists for the current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rxmp-73hh-6v66
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68302"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d29c2644c7f8477979
Added to database: 07/30/2026, 15:50:42 UTC
Last enriched: 07/30/2026, 18:56:25 UTC
Last updated: 09/10/2026, 19:38:49 UTC
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.