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-31637rxrpc: reject undecryptable rxkad response tickets

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: reject undecryptable rxkad response tickets rxkad_decrypt_ticket() decrypts the RXKAD response ticket and then parses the buffer as plaintext without checking whether crypto_skcipher_decrypt() succeeded. A malformed RESPONSE can therefore use a non-block-aligned ticket length, make the decrypt operation fail, and still drive the ticket parser with attacker-controlled bytes. Check the decrypt result and abort the connection with RXKADBADTICKET when ticket decryption fails.

Timeline

  1. ID reserved

    By Linux

  2. · 46 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-31637, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.59% · top 51% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 252157d939d179b5d767cb860ff8fa7f8723b67a
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < a75b3b361dd481d942c5f259a82d59718a41092c
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < b3a808cd0790b5075aaa2bc3588edf02cd71d352
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 47073aab8a3a5a7b41c9bd37d2a3dcbeeccd6c8a
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < a149dcae23309df9de1c3b6b5d468610ef5ab7de
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 22f6258e7b31dba9bf88dce4e3ee7f0f20072e60
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 58fcd1b156152613ba00a064a129fb69507ddd7d
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < fe4447cd95623b1cfacc15f280aab73a6d7340b2
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.135 – ≤ 6.6.*
    • unaffected 6.12.82 – ≤ 6.12.*
    • unaffected 6.18.23 – ≤ 6.18.*
    • unaffected 6.19.13 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .