Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-31676 is a high-severity Race Condition (CWE-362) vulnerability in Linux Kernel. Its CVSS base score is 7.5 (High).
Operationally, ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-31676 is a vulnerability in the Linux kernel's RxRPC implementation. It stems from improper handling of RESPONSE packets during the service connection challenging phase, where packets were processed even after the connection transitioned out of the RXRPC_CONN_SERVICE_CHALLENGING state. This allowed duplicate or late RESPONSE packets to re-run the response verification, security initialization, and secured-connection setup path without proper state locking, potentially leading to resource exhaustion or disruption.
A remote, unauthenticated attacker can exploit this vulnerability over the network with low attack complexity and no user interaction required. Successful exploitation results in a denial-of-service condition due to high availability impact, as indicated by the CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), with no confidentiality or integrity impacts.
Mitigation requires updating to a patched Linux kernel version that includes the upstream fixes. The referenced stable kernel commits address the issue by enforcing state checks under state_lock before processing RESPONSE packets and using a local secured flag to control post-transition queuing: https://git.kernel.org/stable/c/03fd2ef73cb4ffd0af100a95b634af54f474414e, https://git.kernel.org/stable/c/29b44d904dceb832be880def08b8cb17a0aba91c, https://git.kernel.org/stable/c/a6bcf8010af093fe04f7100562e9542ab7882585, https://git.kernel.org/stable/c/c43ffdcfdbb5567b1f143556df8a04b4eeea041c, and https://git.kernel.org/stable/c/d0035e634dae83237ab7f5681eb52b2f65d0ceb8.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25643
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.
Coordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect race conditions, but does not prevent them at design or coding time.
Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-362, a class-level weakness, and none of its children carries one either.