SECUFOCUSNOW
Home›CVE index›CVE-2025-68301
Review reviewCritical

CVE-2025-68301

Linux

In the Linux kernel, the following vulnerability has been resolved: net: atlantic: fix fragment overflow handling in RX path The atlantic driver can receive packets with more than MAX_SKB_FRAGS (17) fragments when handling large multi-descriptor packets. This causes an out-of-bounds write in skb_add_rx_frag_netmem() leading to kernel panic. The issue occurs because the driver doesn't check the total number of fragments before calling skb_add_rx_frag(). When a packet requires more than MAX_SKB_FRAGS fragments, the fragment index exceeds the array bounds. Fix by assuming there will be an extr...

CVSS
9.8
EPSS
0.41%
34.1% percentile
CISA KEV
Not listed
Published
2025.12.17
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.41%
Technical severityCVSS 9.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: net: atlantic: fix fragment overflow handling in RX path The atlantic driver can receive packets with more than MAX_SKB_FRAGS (17) fragments when handling large multi-descriptor packets. This causes an out-of-bounds write in skb_add_rx_frag_netmem() leading to kernel panic. The issue occurs because the driver doesn't check the total number of fragments before calling skb_add_rx_frag(). When a packet requires more than MAX_SKB_FRAGS fragments, the fragment index exceeds the array bounds. Fix by assuming there will be an extr...

Affected product and versions

Product
Linux
Affected versions
>= cd66ab20a8f84474564a68fffffd37d998f6c340 < 34147477eeab24077fcfe9649e282849347d760c, >= 948ddbdc56636773401f2cb9c7a932eb9c43ccfd < b0c4d5135b04ea100988e2458c98f2d8564cda16, >= 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f < 5d6051ea1b0417ae2f06a8440d22e48fbc8f8997, >= 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f < 3be37c3c96b16462394fcb8e15e757c691377038, >= 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f < 3fd2105e1b7e041cc24be151c9a31a14d5fc50ab, >= 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f < 64e47cd1fd631a21bf5a630cebefec6c8fc381cd, >= 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f < 5ffcb7b890f61541201461580bb6622ace405aec, >= dd4fb02847e737cc38ca75e708b1a836fba45faf, >= 5.10.118 < 5.10.247, >= 5.15.42 < 5.15.197, >= 5.17.10 < 5.18, >= 5.18
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available