Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 34147477eeab24077fcfe9649e282849347d760c, 3be37c3c96b16462394fcb8e15e757c691377038, 3fd2105e1b7e041cc24be151c9a31a14d5fc50ab; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1.

Low priority for now. Upgrade to Linux Linux 34147477eeab24077fcfe9649e282849347d760c, 3be37c3c96b16462394fcb8e15e757c691377038, 3fd2105e1b7e041cc24be151c9a31a14d5fc50ab; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 extra frag if buff->len > AQ_CFG_RX_HDR_SIZE, then all fragments are accounted for. And reusing the existing check to prevent the overflow earlier in the code path. This crash occurred in production with an Aquantia AQC113 10G NIC. Stack trace from production environment: ``` RIP: 0010:skb_add_rx_frag_netmem+0x29/0xd0 Code: 90 f3 0f 1e fa 0f 1f 44 00 00 48 89 f8 41 89 ca 48 89 d7 48 63 ce 8b 90 c0 00 00 00 48 c1 e1 04 48 01 ca 48 03 90 c8 00 00 00 <48> 89 7a 30 44 89 52 3c 44 89 42 38 40 f6 c7 01 75 74 48 89 fa 83 RSP: 0018:ffffa9bec02a8d50 EFLAGS: 00010287 RAX: ffff925b22e80a00 RBX: ffff925ad38d2700 RCX: fffffffe0a0c8000 RDX: ffff9258ea95bac0 RSI: ffff925ae0a0c800 RDI: 0000000000037a40 RBP: 0000000000000024 R08: 0000000000000000 R09: 0000000000000021 R10: 0000000000000848 R11: 0000000000000000 R12: ffffa9bec02a8e24 R13: ffff925ad8615570 R14: 0000000000000000 R15: ffff925b22e80a00 FS: 0000000000000000(0000) GS:ffff925e47880000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff9258ea95baf0 CR3: 0000000166022004 CR4: 0000000000f72ef0 PKRU: 55555554 Call Trace: <IRQ> aq_ring_rx_clean+0x175/0xe60 [atlantic] ? aq_ring_rx_clean+0x14d/0xe60 [atlantic] ? aq_ring_tx_clean+0xdf/0x190 [atlantic] ? kmem_cache_free+0x348/0x450 ? aq_vec_poll+0x81/0x1d0 [atlantic] ? __napi_poll+0x28/0x1c0 ? net_rx_action+0x337/0x420 ``` Changes in v4: - Add Fixes: tag to satisfy patch validation requirements. Changes in v3: - Fix by assuming there will be an extra frag if buff->len > AQ_CFG_RX_HDR_SIZE, then all fragments are accounted for.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Dec 16, 2025
Updated
Oct 14, 2026
EPSS
0.4% · 40th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68301

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • dd4fb02847e737cc38ca75e708b1a836fba45faf, 5.18affected
    • cd66ab20a8f84474564a68fffffd37d998f6c340 and later · before 34147477eeab24077fcfe9649e282849347d760caffected · git
    • 948ddbdc56636773401f2cb9c7a932eb9c43ccfd and later · before b0c4d5135b04ea100988e2458c98f2d8564cda16affected · git
    • 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f and later · before 5d6051ea1b0417ae2f06a8440d22e48fbc8f8997affected · git
    • 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f and later · before 3be37c3c96b16462394fcb8e15e757c691377038affected · git
    • 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f and later · before 3fd2105e1b7e041cc24be151c9a31a14d5fc50abaffected · git
    • 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f and later · before 64e47cd1fd631a21bf5a630cebefec6c8fc381cdaffected · git
    • 6aecbba12b5c90b26dc062af3b9de8c4b3a2f19f and later · before 5ffcb7b890f61541201461580bb6622ace405aecaffected · git
    • 5.10.118 and later · before 5.10.247affected · semver
    • 5.15.42 and later · before 5.15.197affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.94.1.el8_104.18.0-553.94.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.94.1.rt7.435.el8_104.18.0-553.94.1.rt7.435.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68299Dec 16, 2025 · afs: Fix delayed allocation of a cell's anonymous key
    0Monitor
  • ← EarlierCVE-2025-68300Dec 16, 2025 · fs/namespace: fix reference leak in grab_requested_mnt_ns
    0Monitor
  • Later →CVE-2025-68302Dec 16, 2025 · net: sxgbe: fix potential NULL dereference in sxgbe_rx()
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux34147477eeab24077fcfe9649e282849347d760cVendor (CNA)
Linux Linux3be37c3c96b16462394fcb8e15e757c691377038Vendor (CNA)
Linux Linux3fd2105e1b7e041cc24be151c9a31a14d5fc50abVendor (CNA)
Linux Linux5.10.247Vendor (CNA)
Linux Linux5.15.197Vendor (CNA)
Linux Linux5.18Vendor (CNA)
Linux Linux5d6051ea1b0417ae2f06a8440d22e48fbc8f8997Vendor (CNA)
Linux Linux5ffcb7b890f61541201461580bb6622ace405aecVendor (CNA)
Linux Linux64e47cd1fd631a21bf5a630cebefec6c8fc381cdVendor (CNA)
Linux Linuxb0c4d5135b04ea100988e2458c98f2d8564cda16Vendor (CNA)
azl3 kernel 6.6.117.1-1 on Azure Linux 3.06.6.119.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.94.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.94.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+8

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records