CVE-2026-93125

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max

check_kfunc_args() detects a kfunc argument named rdonly_buf_size or rdwr_buf_size and stores reg->var_off.value into meta->r0_size, a u64, and does not bound it. check_kfunc_call() later copies that value into the returned register's mem_size field:

meta->r0_size = reg->var_off.value; ... regs[BPF_REG_0].mem_size = meta.r0_size;

regs[BPF_REG_0].mem_size is u32. A constant whose upper 32 bits are set gets truncated instead of causing a load-time rejection, so the verifier records a PTR_TO_MEM register with an approximately 4 GiB mem_size for whatever allocation the kfunc returned. A later access check against that register uses the truncated, wrong bound.

Reject rdonly_buf_size/rdwr_buf_size values that exceed U32_MAX at the point meta->r0_size is set.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

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

bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56a3846830ac95a472297d0cbba75cbff29540bb
generic

bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2aaf67f0516fde29620d0edfc29c01b9ea7ad430

Vendor Advisories for CVE-2026-93125(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 39× in last 7d / 100× 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.

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

Frequently asked(5)

What is CVE-2026-93125?
CVE-2026-93125 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Reject rdonly/rdwrbufsize kfunc arguments that exceed u32 max checkkfuncargs() detects a kfunc argument named rdonlybufsize or rdwrbufsize and stores reg->varoff.value into meta->r0size, a u64, and does not bound it.…
When was CVE-2026-93125 disclosed?
CVE-2026-93125 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93125 actively exploited?
CVE-2026-93125 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93125?
CVE-2026-93125 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93125?
No fix for CVE-2026-93125 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93125 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-2026-93125

Explore →

Is Your Infrastructure Affected by CVE-2026-93125?

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

Book a Demo →Browse All CVEs