Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.5%top 62%

In the Linux kernel, the following vulnerability has been resolved: net: atlantic: fix fragment overflow handling in RX path The atlantic driver can… (CVE-2025-68301)

0
Critical
Published: 12/16/2025 (12/16/2025, 18:31:33 UTC)
Source: GCVE Database

Description

A critical vulnerability in the Linux kernel's atlantic network driver allows an out-of-bounds write due to improper handling of packet fragments exceeding the maximum allowed. This can cause a kernel panic when processing large multi-descriptor packets. The issue arises because the driver does not check the total number of fragments before adding them, leading to an overflow in skb_add_rx_frag_netmem(). The vulnerability has been fixed by improving fragment accounting and adding earlier overflow checks.

CVSS v3.1

Score 9.8critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/30/2026, 18:40:59 UTC

Technical Analysis

The Linux kernel atlantic driver mishandles packets with more than MAX_SKB_FRAGS (17) fragments, causing an out-of-bounds write in skb_add_rx_frag_netmem(). This occurs because the driver fails to verify the total fragment count before calling skb_add_rx_frag(), allowing the fragment index to exceed array bounds. The flaw leads to kernel panic and was observed in production with an Aquantia AQC113 10G NIC. The fix involves assuming an extra fragment if the buffer length exceeds AQ_CFG_RX_HDR_SIZE and reusing existing checks to prevent overflow earlier in the RX path.

Potential Impact

Successful exploitation results in an out-of-bounds write in kernel memory, causing a kernel panic and denial of service. The vulnerability affects system stability and could potentially be leveraged for further kernel-level compromise, given the high severity of the memory corruption.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates a fix has been developed and merged into the Linux kernel source, but no explicit patch link or version is provided. Users should monitor official Linux kernel releases and update to a version that includes the fix for CVE-2025-68301 once available.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-xx64-5wwx-9g36
Osv Schema Version
1.4.0
Aliases
["CVE-2025-68301"]
Ecosystems
[]
Database Specific Severity
CRITICAL
Cvss Version
3.1

Threat ID: 6a6b72d39c2644c7f8477fdb

Added to database: 07/30/2026, 15:50:43 UTC

Last enriched: 07/30/2026, 18:40:59 UTC

Last updated: 08/24/2026, 10:52:06 UTC

Views: 13

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses