CVE-2026-63823

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

keys: Pin request_key_auth payload in instantiate paths

A: request_key() B: KEYCTL_INSTANTIATE_IOV ================ =========================

create auth key store rka in auth key wait for helper get auth key load rka from auth key copy user payload sleep on #PF

helper completed detach and free rka destroy auth key wake up use rka->target_key USE-AFTER-FREE

Give request_key_auth payloads a refcount. Take a payload reference while authkey->sem stabilizes the payload and revocation state. Hold that reference across the instantiate and reject paths. Drop the auth key owning reference from revoke and destroy.

[jarkko: Replaced the first two paragraphs of text with an actual concurrency scenario.]

CVSS v3
7.8
EG Score
7.8(high)
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
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

Advisory Details (8)

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

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7216ce8cb12fee44e309503955bb83806b106129
generic

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/708709c65a1832a99b0eef8ae46e343ddaca3d06
generic

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4982bfabce6b33b3c9eddb4fb900fe5568b7cf91
generic

keys: Pin request_key_auth payload in instantiate paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35ab4db86774d82389e4b9559e26ab7f68d8e395

Vendor Advisories for CVE-2026-63823(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-63823?
CVE-2026-63823 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: keys: Pin requestkeyauth payload in instantiate paths A: requestkey() B: KEYCTLINSTANTIATE_IOV ================ ========================= create auth key store rka in auth key wait for helper get auth key load rka from auth key…
When was CVE-2026-63823 disclosed?
CVE-2026-63823 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63823 actively exploited?
CVE-2026-63823 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-63823?
CVE-2026-63823 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-63823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63823, 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

Explore the affected products and dependency analysis for CVE-2026-63823

Explore →

Is Your Infrastructure Affected by CVE-2026-63823?

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