CVE-2026-64375

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. 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 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

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

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

proc: protect ptrace_may_access() with exec_update_lock (FD links)

proc_pid_get_link() and proc_pid_readlink() currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second time to do the actual access. That's racy in several ways.

To fix it, pass the task to the ->proc_get_link() handler, and instead of proc_fd_access_allowed(), introduce a new helper call_proc_get_link() that looks up and locks the task, does the access check, and calls ->proc_get_link().

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 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

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

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

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

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83b17872e3166c295c599279fc9562ac3840c638
generic

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65bf0d2b6e914f1448d6a2fde193dcf60936a651
generic

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6255da28d4bb5349fe18e84cb043ccd394eba75d
generic

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6253dfee5afba536bb54fc6fe6c091c3758fafe1
generic

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/497c6bae5167428596575f20af6613ff5671f383
generic

proc: protect ptrace_may_access() with exec_update_lock (FD links) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2

Vendor Advisories for CVE-2026-64375(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Data Freshness Timeline

(refreshed 31× in last 7d / 152× 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 182 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64375?
CVE-2026-64375 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess() with execupdatelock (FD links) procpidgetlink() and procpid_readlink() currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a…
When was CVE-2026-64375 disclosed?
CVE-2026-64375 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64375 actively exploited?
CVE-2026-64375 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64375?
CVE-2026-64375 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64375, 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-64375

Explore →

Is Your Infrastructure Affected by CVE-2026-64375?

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