CVE-2025-21868

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2025-03-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-8434 (ENISA EUVD) · GHSA-3w57-3p47-w8ch (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: allow small head cache usage with large MAX_SKB_FRAGS values

Sabrina reported the following splat:

WARNING: CPU: 0 PID: 1 at net/core/dev.c:6935 netif_napi_add_weight_locked+0x8f2/0xba0 Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.0-rc1-net-00092-g011b03359038 #996 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:netif_napi_add_weight_locked+0x8f2/0xba0 Code: e8 c3 e6 6a fe 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc c7 44 24 10 ff ff ff ff e9 8f fb ff ff e8 9e e6 6a fe <0f> 0b e9 d3 fe ff ff e8 92 e6 6a fe 48 8b 04 24 be ff ff ff ff 48 RSP: 0000:ffffc9000001fc60 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88806ce48128 RCX: 1ffff11001664b9e RDX: ffff888008f00040 RSI: ffffffff8317ca42 RDI: ffff88800b325cb6 RBP: ffff88800b325c40 R08: 0000000000000001 R09: ffffed100167502c R10: ffff88800b3a8163 R11: 0000000000000000 R12: ffff88800ac1c168 R13: ffff88800ac1c168 R14: ffff88800ac1c168 R15: 0000000000000007 FS: 0000000000000000(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff888008201000 CR3: 0000000004c94001 CR4: 0000000000370ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: gro_cells_init+0x1ba/0x270 xfrm_input_init+0x4b/0x2a0 xfrm_init+0x38/0x50 ip_rt_init+0x2d7/0x350 ip_init+0xf/0x20 inet_init+0x406/0x590 do_one_initcall+0x9d/0x2e0 do_initcalls+0x23b/0x280 kernel_init_freeable+0x445/0x490 kernel_init+0x20/0x1d0 ret_from_fork+0x46/0x80 ret_from_fork_asm+0x1a/0x30 irq event stamp: 584330 hardirqs last enabled at (584338): [] __up_console_sem+0x77/0xb0 hardirqs last disabled at (584345): [] __up_console_sem+0x5c/0xb0 softirqs last enabled at (583242): [] netlink_insert+0x14d/0x470 softirqs last disabled at (583754): [] netif_napi_add_weight_locked+0x77d/0xba0

on kernel built with MAX_SKB_FRAGS=45, where SKB_WITH_OVERHEAD(1024) is smaller than GRO_MAX_HEAD.

Such built additionally contains the revert of the single page frag cache so that napi_get_frags() ends up using the page frag allocator, triggering the splat.

Note that the underlying issue is independent from the mentioned revert; address it ensuring that the small head cache will fit either TCP and GRO allocation and updating napi_alloc_skb() and __netdev_alloc_skb() to select kmalloc() usage for any allocation fitting such cache.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 27, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
Patch available.
Web page

net: allow small head cache usage with large MAX_SKB_FRAGS values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed8a77fee4618facd2a539cad7b7366697b5a575
Web page

net: allow small head cache usage with large MAX_SKB_FRAGS values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed0ca7d2127c63991cfaf1932b827e3f4f8ee480
Web page

net: allow small head cache usage with large MAX_SKB_FRAGS values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/648e440c98e260dec835e48a5d7a9993477b1f9d
Web page

net: allow small head cache usage with large MAX_SKB_FRAGS values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14ad6ed30a10afbe91b0749d6378285f4225d482

Vendor Advisories for CVE-2025-21868(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-64k (6.11.0-1016.17) @ oracular2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-10-24ubuntu
ubuntulinux-virtual-6.8 (6.8.0-78.78) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1035.39) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-10-24ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1033.33) @ noble2026-10-24ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1032.33) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2028.29) @ noble2026-10-24ubuntu
linuxKernel @ 6.6.117 (fixes >=6.4.0)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.17-1: fixed in 6.12.17-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.17-1: fixed in 6.12.17-1
—

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 6× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 227 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-20 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-19 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-11-18 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-11-17 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-11-16 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-11-15 16:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-11-14 16:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-11-13 16:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-11-11 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-11-10 16:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-11-08 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-11-07 20:29 UTCGHSA enrichmentGHSA-3w57-3p47-w8ch · GitHub severity MODERATE · GitHub CVSS 5.5
  16. 2026-11-07 20:29 UTCEchelonGraph re-scored
  17. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-11-06 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 72 more
  1. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-25 16:42 UTCEchelonGraph re-scored
  6. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-24 01:13 UTCEchelonGraph re-scored
  9. 2026-10-24 01:13 UTCVendor advisory
  10. 2026-10-24 01:13 UTCGHSA enrichmentGHSA-3w57-3p47-w8ch · GitHub CVSS 5.5
  11. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-19 23:25 UTCOSV refresh
  16. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-18 05:46 UTCEchelonGraph re-scored
  19. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-12 17:19 UTCEchelonGraph re-scored
  25. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-10-11 20:51 UTCEchelonGraph re-scored
  27. 2026-10-11 19:01 UTCEchelonGraph re-scored
  28. 2026-10-11 15:41 UTCEchelonGraph re-scored
  29. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  31. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  32. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  35. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-10-02 16:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  40. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  41. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  42. 2026-09-27 03:45 UTCOSV refresh
  43. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  44. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  45. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  46. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  48. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  49. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  50. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  51. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  52. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  53. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  54. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  55. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  56. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  57. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  58. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  59. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  60. 2026-09-07 13:17 UTCOSV refresh
  61. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  62. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  63. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  64. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  65. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  67. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  68. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  69. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  70. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  71. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  72. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile

Frequently asked(5)

What is CVE-2025-21868?
CVE-2025-21868 is a medium-severity vulnerability; its CVE record was published on March 27, 2025. In the Linux kernel, the following vulnerability has been resolved: net: allow small head cache usage with large MAX_SKB_FRAGS values Sabrina reported the following splat: WARNING: CPU: 0 PID: 1 at net/core/dev.c:6935 netif_napi_add_weight_locked+0x8f2/0xba0 Modules linked in: CPU: 0 UID: 0 PID: 1…
When was the CVE record for CVE-2025-21868 published?
The CVE record for CVE-2025-21868 was published on March 27, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-21868 actively exploited?
CVE-2025-21868 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21868?
CVE-2025-21868 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21868?
A fix for CVE-2025-21868 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21868 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-21868?

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