CVE-2025-68301

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-16. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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:

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

December 16, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Sep 2, 2026
No patch confirmed yet.
generic

net: atlantic: fix fragment overflow handling in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ffcb7b890f61541201461580bb6622ace405aec
generic

net: atlantic: fix fragment overflow handling in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64e47cd1fd631a21bf5a630cebefec6c8fc381cd
generic

net: atlantic: fix fragment overflow handling in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fd2105e1b7e041cc24be151c9a31a14d5fc50ab
generic

net: atlantic: fix fragment overflow handling in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3be37c3c96b16462394fcb8e15e757c691377038
generic

net: atlantic: fix fragment overflow handling in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d6051ea1b0417ae2f06a8440d22e48fbc8f8997
generic

net: atlantic: fix fragment overflow handling in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b0c4d5135b04ea100988e2458c98f2d8564cda16
generic

net: atlantic: fix fragment overflow handling in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34147477eeab24077fcfe9649e282849347d760c

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-07-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-07-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-07-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-07-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-07-30ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-07-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-07-30ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-07-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-07-30ubuntu
redhatkernel-0:4.18.0-193.185.1.el8_22026-02-12redhat
redhatkernel-0:4.18.0-477.128.1.el8_82026-02-11redhat
redhatkernel-0:4.18.0-372.179.1.el8_62026-02-11redhat
redhatkernel-0:5.14.0-70.165.1.el9_02026-02-11redhat
redhatkernel-rt-0:5.14.0-70.165.1.rt21.237.el9_02026-02-11redhat
redhatkernel-0:4.18.0-305.184.1.el8_42026-02-04redhat
redhatkernel-0:5.14.0-284.155.1.el9_22026-02-04redhat
redhatkernel-0:5.14.0-427.109.1.el9_42026-02-04redhat
redhatkernel-rt-0:5.14.0-284.155.1.rt14.440.el9_22026-02-04redhat
redhatkernel-0:6.12.0-124.31.1.el10_12026-02-02redhat
redhatkernel-0:5.14.0-570.84.1.el9_62026-02-02redhat
redhatkernel-0:6.12.0-55.58.1.el10_02026-02-02redhat
redhatkernel-0:5.14.0-611.26.1.el9_72026-01-26redhat
redhatkernel-rt-0:4.18.0-553.94.1.rt7.435.el8_102026-01-19redhat
redhatkernel-0:4.18.0-553.94.1.el8_102026-01-19redhat
linuxKernel @ 5.10.247osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)5.10.247-1
linux-6.16.1.106-3~deb11u1 ... 6.1.158-1~deb11u1 (13 versions)6.1.159-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (45 versions)6.1.159-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)6.12.63-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.9-1 (79 versions)6.17.11-1

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 4× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 177 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:11 UTCEPSS rescore
  5. 2026-09-01 13:53 UTCEPSS rescore
  6. 2026-08-30 01:21 UTCEPSS rescore
  7. 2026-08-28 21:40 UTCEPSS rescore
  8. 2026-08-27 14:24 UTCEPSS rescore
  9. 2026-08-26 14:45 UTCEPSS rescore
  10. 2026-08-26 09:13 UTCOSV refresh
  11. 2026-08-25 13:48 UTCEPSS rescore
  12. 2026-08-24 14:16 UTCEPSS rescore
  13. 2026-08-23 00:18 UTCEPSS rescore
  14. 2026-08-21 23:48 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:46 UTCEPSS rescore
  19. 2026-08-16 14:55 UTCEPSS rescore
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 13:42 UTCEPSS rescore
  25. 2026-08-10 23:59 UTCEPSS rescore
Show 75 more
  1. 2026-08-09 23:35 UTCEG score recompute
  2. 2026-08-09 23:35 UTCVendor advisory
  3. 2026-08-09 23:35 UTCGHSA enrichment
  4. 2026-08-09 13:46 UTCEPSS rescore
  5. 2026-08-08 16:36 UTCEPSS rescore
  6. 2026-08-08 06:21 UTCEG score recompute
  7. 2026-08-08 06:21 UTCVendor advisory
  8. 2026-08-08 06:21 UTCGHSA enrichment
  9. 2026-08-07 16:27 UTCEPSS rescore
  10. 2026-08-06 13:46 UTCEPSS rescore
  11. 2026-08-06 08:54 UTCEG score recompute
  12. 2026-08-06 08:54 UTCVendor advisory
  13. 2026-08-06 08:54 UTCGHSA enrichment
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 12:48 UTCEG score recompute
  16. 2026-08-05 12:48 UTCVendor advisory
  17. 2026-08-05 12:48 UTCGHSA enrichment
  18. 2026-08-04 10:37 UTCEPSS rescore
  19. 2026-08-03 10:35 UTCEPSS rescore
  20. 2026-08-02 02:26 UTCEPSS rescore
  21. 2026-08-01 04:15 UTCEPSS rescore
  22. 2026-07-30 16:27 UTCEPSS rescore
  23. 2026-07-30 06:48 UTCEG score recompute
  24. 2026-07-30 06:48 UTCVendor advisory
  25. 2026-07-30 06:47 UTCGHSA enrichment
  26. 2026-07-30 06:21 UTCEG score recompute 9.80
  27. 2026-07-30 06:21 UTCVendor advisory
  28. 2026-07-30 06:21 UTCGHSA enrichment
  29. 2026-07-30 06:18 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  30. 2026-07-30 01:30 UTCEPSS rescore
  31. 2026-07-27 14:13 UTCEPSS rescore
  32. 2026-07-27 05:09 UTCOSV refresh
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 14:54 UTCEPSS rescore
  35. 2026-07-24 14:17 UTCEPSS rescore
  36. 2026-07-23 14:18 UTCEPSS rescore
  37. 2026-07-23 14:18 UTCEPSS rescore
  38. 2026-07-23 03:02 UTCEG score recompute
  39. 2026-07-22 14:08 UTCEPSS rescore
  40. 2026-07-21 15:24 UTCEPSS rescore
  41. 2026-07-20 17:08 UTCEPSS rescore
  42. 2026-07-19 14:30 UTCEPSS rescore
  43. 2026-07-19 14:30 UTCEPSS rescore
  44. 2026-07-19 02:28 UTCEPSS rescore
  45. 2026-07-19 02:28 UTCEPSS rescore
  46. 2026-07-18 10:04 UTCEPSS rescore
  47. 2026-07-18 10:04 UTCEPSS rescore
  48. 2026-07-16 17:02 UTCEPSS rescore
  49. 2026-07-16 17:02 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 16:57 UTCEPSS rescore
  52. 2026-07-13 06:12 UTCEPSS rescore
  53. 2026-07-12 05:46 UTCEPSS rescore
  54. 2026-07-12 05:46 UTCEPSS rescore
  55. 2026-07-11 08:27 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-09 23:17 UTCOSV refresh
  58. 2026-07-09 19:10 UTCEPSS rescore
  59. 2026-07-08 15:15 UTCEPSS rescore
  60. 2026-07-07 13:46 UTCEPSS rescore
  61. 2026-07-06 16:27 UTCEPSS rescore
  62. 2026-07-06 02:23 UTCEPSS rescore
  63. 2026-07-05 02:30 UTCEPSS rescore
  64. 2026-07-05 02:30 UTCEPSS rescore
  65. 2026-07-04 06:31 UTCEPSS rescore
  66. 2026-07-04 06:31 UTCEPSS rescore
  67. 2026-07-01 15:06 UTCEPSS rescore
  68. 2026-06-30 23:22 UTCEPSS rescore
  69. 2026-06-30 23:22 UTCEPSS rescore
  70. 2026-06-29 14:06 UTCEPSS rescore
  71. 2026-06-29 14:06 UTCEPSS rescore
  72. 2026-06-28 14:07 UTCEPSS rescore
  73. 2026-06-28 14:07 UTCEPSS rescore
  74. 2026-06-28 04:56 UTCEPSS rescore
  75. 2026-06-28 04:56 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-68301?
CVE-2025-68301 is a critical vulnerability published on December 16, 2025. 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 MAXSKBFRAGS (17) fragments when handling large multi-descriptor packets. This causes an out-of-bounds write in…
When was CVE-2025-68301 disclosed?
CVE-2025-68301 was first published in the National Vulnerability Database on December 16, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68301 actively exploited?
CVE-2025-68301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.9% of all scored CVEs.
What is the CVSS score of CVE-2025-68301?
CVE-2025-68301 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-68301?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68301, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68301

Explore →

Is Your Infrastructure Affected by CVE-2025-68301?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.