Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31696, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < 44714dfda386884919ba366411880b6fb3c3efd3
    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < 41a117dd80371343babc52198d1114e83eb37627
    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < 9a397aa9b5e53ca63d4d6aefb542832eca389618
    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < 1fa36cf495b0023e8475d038535c05e4063211e1
    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < 4458757c020592a3094366e0fb20457383b42f92
    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < ce383ba615339f8eaec646a166d2c2b015bb5ca0
    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < a1be1c9ece26cea69654f28b255ff9a7906b897b
    • affected 8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247 – < ac33733b10b484d666f97688561670afd5861383
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.84 – ≤ 6.12.*
    • unaffected 6.18.25 – ≤ 6.18.*
    • unaffected 7.0.2 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31696 badge
[![CVE-2026-31696](https://cveledger.app/badge/CVE-2026-31696.svg)](https://cveledger.app/cve/CVE-2026-31696)

Record last updated .