Kernel panic via unchecked RX fragment count
Published Dec 16, 2025 · Updated Dec 16, 2025
Out-of-bounds write in the Linux atlantic RX path allows attackers to trigger a kernel panic via large multi-descriptor packets. The driver calls skb_add_rx_frag without first accounting for every fragment, allowing an index above MAX_SKB_FRAGS to write beyond the fragment array. Exposure requires the atlantic driver and relevant Aquantia network hardware; the documented consequence is a host-level service interruption.
Summary
What happened
Out-of-bounds write in the Linux atlantic RX path allows attackers to trigger a kernel panic via large multi-descriptor packets. The driver calls skb_add_rx_frag without first accounting for every fragment, allowing an index above MAX_SKB_FRAGS to write beyond the fragment array. Exposure requires the atlantic driver and relevant Aquantia network hardware; the documented consequence is a host-level service interruption.
The record
- CVE
- CVE-2025-68301
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
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=5.18
- Affected versionversion=6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f <3be37c3c96b16462394fcb8e15e757c691377038
- Affected versionversion=6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f <3fd2105e1b7e041cc24be151c9a31a14d5fc50ab
- Affected versionversion=6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f <5d6051ea1b0417ae2f06a8440d22e48fbc8f8997
- Affected versionversion=6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f <5ffcb7b890f61541201461580bb6622ace405aec
- Affected versionversion=6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f <64e47cd1fd631a21bf5a630cebefec6c8fc381cd
- Affected versionversion=948ddbdc56636773401f2cb9c7a932eb9c43ccfd <b0c4d5135b04ea100988e2458c98f2d8564cda16
- Affected versionversion=cd66ab20a8f84474564a68fffffd37d998f6c340 <34147477eeab24077fcfe9649e282849347d760c
- Affected versionversion=dd4fb02847e737cc38ca75e708b1a836fba45faf
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.
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