Skip to main content
VulnerabilityPublished Updated

CVE-2026-31642: Linux kernel · rxrpc: Fix call removal to use RCU safe deletion

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c63abf25203b50243fe228090526f9dbf37727bd : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in c63abf25203b50243fe228090526f9dbf37727bd, b15b1ce96777b88989a6a4de8d01efbcd81ad2d7, ac5f54691be06a32246179d41be2d73598036deb +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2baec2c3f854d1f79c7bb28386484e144e864a14, < c63abf25203b50243fe228090526f9dbf37727bd
Fixed in
  • c63abf25203b50243fe228090526f9dbf37727bd
LinuxLinuxAffected
  • ≥ 2baec2c3f854d1f79c7bb28386484e144e864a14, < b15b1ce96777b88989a6a4de8d01efbcd81ad2d7
Fixed in
  • b15b1ce96777b88989a6a4de8d01efbcd81ad2d7
LinuxLinuxAffected
  • ≥ 2baec2c3f854d1f79c7bb28386484e144e864a14, < ac5f54691be06a32246179d41be2d73598036deb
Fixed in
  • ac5f54691be06a32246179d41be2d73598036deb
LinuxLinuxAffected
  • ≥ 2baec2c3f854d1f79c7bb28386484e144e864a14, < 280efb85e9759881a9d31d0874baa04583cb6c09
Fixed in
  • 280efb85e9759881a9d31d0874baa04583cb6c09
LinuxLinuxAffected
  • ≥ 2baec2c3f854d1f79c7bb28386484e144e864a14, < 146d4ab94cf129ee06cd467cb5c71368a6b5bad6
Fixed in
  • 146d4ab94cf129ee06cd467cb5c71368a6b5bad6
LinuxLinuxAffected
  • ≥ 2baec2c3f854d1f79c7bb28386484e144e864a14, < 93fc15be44a35b8e3c58d0238ac0d9b7c53465ff
Fixed in
  • 93fc15be44a35b8e3c58d0238ac0d9b7c53465ff

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call removal to use RCU safe deletion Fix rxrpc call removal from the rxnet->calls list to use list_del_rcu() rather than list_del_init() to prevent stuffing up reading /proc/net/rxrpc/calls from potentially getting into an infinite loop. This, however, means that list_empty() no longer works on an entry that's been deleted from the list, making it harder to detect prior deletion. Fix this by: Firstly, make rxrpc_destroy_all_calls() only dump the first ten calls that are unexpectedly still on the list. Limiting the number of steps means there's no need to call cond_resched() or to remove calls from the list here, thereby eliminating the need for rxrpc_put_call() to check for that. rxrpc_put_call() can then be fixed to unconditionally delete the call from the list as it is the only place that the deletion occurs.

References

Community reviews

Loading reviews…