CVE-2026-64036

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

cgroup/rstat: validate cpu before css_rstat_cpu() access

css_rstat_updated() is exposed as a BPF kfunc and accepts a caller-provided cpu argument. The function uses cpu for per-cpu rstat lookups without checking whether it refers to a valid possible CPU.

A BPF iter/cgroup program with CAP_BPF and CAP_PERFMON can pass an invalid cpu value. On an unfixed UBSCAN_BOUNDS test kernel, cpu == 0x7fffffff triggers:

UBSAN: array-index-out-of-bounds in kernel/cgroup/rstat.c:31:9 index 2147483647 is out of range for type 'long unsigned int [64]' Call Trace: css_rstat_updated bpf_iter_run_prog cgroup_iter_seq_show bpf_seq_read

Add cpu validation to the BPF-facing css_rstat_updated() kfunc and move the common implementation to __css_rstat_updated() for in-kernel callers.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

cgroup/rstat: validate cpu before css_rstat_cpu() access - kernel/git/stable/linux.git - Linux kernel stable tree

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

cgroup/rstat: validate cpu before css_rstat_cpu() access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8817005efbdfdf5d4e4814cb5dc52b53d12917d7
generic

cgroup/rstat: validate cpu before css_rstat_cpu() access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6

Vendor Advisories for CVE-2026-64036(2)

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

Patch Availability(6)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 20× in last 7d / 121× 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 240 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64036?
CVE-2026-64036 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: cgroup/rstat: validate cpu before cssrstatcpu() access cssrstatupdated() is exposed as a BPF kfunc and accepts a caller-provided cpu argument. The function uses cpu for per-cpu rstat lookups without checking whether it refers to a…
When was CVE-2026-64036 disclosed?
CVE-2026-64036 was first published in the National Vulnerability Database on July 19, 2026, 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-2026-64036 actively exploited?
CVE-2026-64036 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64036?
CVE-2026-64036 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64036?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64036, 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-2026-64036

Explore →

Is Your Infrastructure Affected by CVE-2026-64036?

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