CVE-2026-31696

HIGHCVSS · not yet scored7.8
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
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 v2: —Exploit: 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:

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing

In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While the XDR path (rxrpc_preparse_xdr_rxkad()) correctly validates the ticket length against AFSTOKEN_RK_TIX_MAX, the non-XDR path fails to do so.

This allows an unprivileged user to provide a very large ticket length. When this key is later read via rxrpc_read(), the total token size (toksize) calculation results in a value that exceeds AFSTOKEN_LENGTH_MAX, triggering a WARN_ON().

[ 2001.302904] WARNING: CPU: 2 PID: 2108 at net/rxrpc/key.c:778 rxrpc_read+0x109/0x5c0 [rxrpc]

Fix this by adding a check in the non-XDR parsing path of rxrpc_preparse() to ensure the ticket length does not exceed AFSTOKEN_RK_TIX_MAX, bringing it into parity with the XDR parsing logic.

CVSS v3
—
EG Score
7.8(low)
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

May 1, 2026

Last Modified

June 14, 2026

Advisory Details (5)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4458757c020592a3094366e0fb20457383b42f92
generic

rxrpc: Fix missing validation of ticket length in non-XDR key preparsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fa36cf495b0023e8475d038535c05e4063211e1

Vendor Advisories for CVE-2026-31696(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258—osv

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 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.1-1~exp1 (129 versions)7.0.3-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 7× in last 7d / 71× 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 252 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-31696?
CVE-2026-31696 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing validation of ticket length in non-XDR key preparsing In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While…
When was CVE-2026-31696 disclosed?
CVE-2026-31696 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31696 actively exploited?
CVE-2026-31696 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.
How do I remediate CVE-2026-31696?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31696, 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-31696

Explore →

Is Your Infrastructure Affected by CVE-2026-31696?

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

Start Free Scan →Browse All CVEs