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-31676rxrpc: only handle RESPONSE during service challenge

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: only handle RESPONSE during service challenge Only process RESPONSE packets while the service connection is still in RXRPC_CONN_SERVICE_CHALLENGING. Check that state under state_lock before running response verification and security initialization, then use a local secured flag to decide whether to queue the secured-connection work after the state transition. This keeps duplicate or late RESPONSE packets from re-running the setup path and removes the unlocked post-transition state test.

Timeline

  1. ID reserved

    By Linux

  2. · 47 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-31676, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.47% · top 59% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · 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.5.

Affected products

  • Linux · Linux

    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < a1a8efde03a40b6c658d580e96644d9b9a2a0d3a
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 6c3a0fbdafef8316e34ae22333e317a341e737cd
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 0afdfd4941c1b60a1f5c361760daa970edca60cd
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < a6bcf8010af093fe04f7100562e9542ab7882585
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 29b44d904dceb832be880def08b8cb17a0aba91c
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < d0035e634dae83237ab7f5681eb52b2f65d0ceb8
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < 03fd2ef73cb4ffd0af100a95b634af54f474414e
    • affected 17926a79320afa9b95df6b977b40cca6d8713cea – < c43ffdcfdbb5567b1f143556df8a04b4eeea041c
  • 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.136 – ≤ 6.6.*
    • unaffected 6.12.84 – ≤ 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-31676 badge
[![CVE-2026-31676](https://cveledger.app/badge/CVE-2026-31676.svg)](https://cveledger.app/cve/CVE-2026-31676)

Record last updated .