CVE-2026-63823

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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

A fix is available — apply it.

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(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
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 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.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu

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

(5 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.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1—

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs