CVE-2026-31676: rxrpc: only handle RESPONSE during service challenge
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.
Security readout for executives and security teams
Plain-English summary
A Linux RxRPC flaw allows duplicate or delayed response packets to repeat part of secure connection setup after the connection state has advanced. It carries a CVSS 7.5 rating for remotely triggerable availability impact. The supplied sources do not document practical attack prerequisites, successful exploitation, or data compromise.
Executive priority
Treat this as a high-priority availability risk for externally reachable or operationally important Linux systems using RxRPC. Accelerate vendor-supported kernel updates after confirming exposure. Broad emergency action is not supported by the current evidence because active exploitation and deployment prerequisites are undocumented.
Technical view
RESPONSE packets were processed outside the intended RXRPC_CONN_SERVICE_CHALLENGING state, permitting late or duplicate packets to rerun response verification and security initialization. The fix checks connection state under state_lock, records secured status locally, and avoids an unlocked post-transition state check.
Likely exposure
Potential exposure exists on affected Linux kernels where RxRPC service functionality is present and network-reachable. The CVSS vector indicates network access, low complexity, no privileges, and no user interaction. The bundle does not establish whether RxRPC is enabled by default or provide an unambiguous affected-to-fixed version mapping.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. The documented consequence is availability loss; confidentiality and integrity impacts are scored as none.
Researcher notes
The security boundary is connection-state synchronization during service challenge handling. Review should focus on RESPONSE processing, locking around state validation, repeated initialization, and secured-work queuing. The source bundle identifies multiple stable commits but does not map them clearly to affected distributions or demonstrate a reproducible denial-of-service condition.
Mitigation direction
Obtain the appropriate supported kernel update containing the vendor-provided RxRPC fix.
Prioritize systems that use RxRPC or expose related services to untrusted networks.
Consult the operating-system vendor for exact affected and fixed package versions.
Apply network exposure reduction where RxRPC is unnecessary or cannot yet be updated.
Validation and detection
Inventory running kernel versions across Linux hosts.
Determine whether RxRPC functionality is present, used, and reachable from untrusted networks.
Compare deployed kernels with vendor advisories and the referenced stable-branch commits.
After updating, verify the running kernel includes the applicable fix.
Monitor affected hosts for unexplained crashes, hangs, or RxRPC-related availability events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31676 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.