CVE-2026-31636

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-24. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

rxrpc: fix RESPONSE authenticator parser OOB read

rxgk_verify_authenticator() copies auth_len bytes into a temporary buffer and then passes p + auth_len as the parser limit to rxgk_do_verify_authenticator(). Since p is a __be32 *, that inflates the parser end pointer by a factor of four and lets malformed RESPONSE authenticators read past the kmalloc() buffer.

Decoded from the original latest-net reproduction logs with scripts/decode_stacktrace.sh:

BUG: KASAN: slab-out-of-bounds in rxgk_verify_response() Call Trace: dump_stack_lvl() [lib/dump_stack.c:123] print_report() [mm/kasan/report.c:379 mm/kasan/report.c:482] kasan_report() [mm/kasan/report.c:597] rxgk_verify_response() [net/rxrpc/rxgk.c:1103 net/rxrpc/rxgk.c:1167 net/rxrpc/rxgk.c:1274] rxrpc_process_connection() [net/rxrpc/conn_event.c:266 net/rxrpc/conn_event.c:364 net/rxrpc/conn_event.c:386] process_one_work() [kernel/workqueue.c:3281] worker_thread() [kernel/workqueue.c:3353 kernel/workqueue.c:3440] kthread() [kernel/kthread.c:436] ret_from_fork() [arch/x86/kernel/process.c:164]

Allocated by task 54: rxgk_verify_response() [include/linux/slab.h:954 net/rxrpc/rxgk.c:1155 net/rxrpc/rxgk.c:1274] rxrpc_process_connection() [net/rxrpc/conn_event.c:266 net/rxrpc/conn_event.c:364 net/rxrpc/conn_event.c:386]

Convert the byte count to __be32 units before constructing the parser limit.

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

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

rxrpc: fix RESPONSE authenticator parser OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e3138007887504ee9206d0bfb5acb062c600025
generic

rxrpc: fix RESPONSE authenticator parser OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20a188775a9a9982d1987e12660d9b44b40a6c99
generic

rxrpc: fix RESPONSE authenticator parser OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7875f3d9777bd4e9892c4db830571ab8ac2044c0

Vendor Advisories for CVE-2026-31636(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.28.1.el10_22026-06-25redhat
linuxKernel @ 6.18.23osv

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (127 versions)6.19.13-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

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 5× in last 7d / 34× 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 335 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31636?
CVE-2026-31636 is a critical vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix RESPONSE authenticator parser OOB read rxgkverifyauthenticator() copies auth_len bytes into a temporary buffer and then passes p + auth_len as the parser limit to rxgkdoverifyauthenticator(). Since p is a _be32 *, that…
When was CVE-2026-31636 disclosed?
CVE-2026-31636 was first published in the National Vulnerability Database on April 24, 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-31636 actively exploited?
CVE-2026-31636 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 62.6% of all scored CVEs.
What is the CVSS score of CVE-2026-31636?
CVE-2026-31636 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-31636?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31636, 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-31636

Explore →

Is Your Infrastructure Affected by CVE-2026-31636?

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