Skip to main content
VulnerabilityPublished Updated

CVE-2026-31639: Linux kernel · rxrpc: Fix key reference count leak from call->key

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f1a7a3ab0f35f83cf11bba906b9e948cf3788c28 : 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 f1a7a3ab0f35f83cf11bba906b9e948cf3788c28, e6b7943c5dc875647499da09bf4d50a8557ab0c3, d666540d217e8d420544ebdfbadeedd623562733 +2

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
  • ≥ f3441d4125fc98995858550a5521b8d7daf0504a, < f1a7a3ab0f35f83cf11bba906b9e948cf3788c28
Fixed in
  • f1a7a3ab0f35f83cf11bba906b9e948cf3788c28
LinuxLinuxAffected
  • ≥ f3441d4125fc98995858550a5521b8d7daf0504a, < e6b7943c5dc875647499da09bf4d50a8557ab0c3
Fixed in
  • e6b7943c5dc875647499da09bf4d50a8557ab0c3
LinuxLinuxAffected
  • ≥ f3441d4125fc98995858550a5521b8d7daf0504a, < d666540d217e8d420544ebdfbadeedd623562733
Fixed in
  • d666540d217e8d420544ebdfbadeedd623562733
LinuxLinuxAffected
  • ≥ f3441d4125fc98995858550a5521b8d7daf0504a, < 978108902ee4ef2b348ff7ec36ad014dc5bc6dc6
Fixed in
  • 978108902ee4ef2b348ff7ec36ad014dc5bc6dc6
LinuxLinuxAffected
  • ≥ f3441d4125fc98995858550a5521b8d7daf0504a, < 2e6ef713b1598f6acd7f302fa6b12b6731c89914
Fixed in
  • 2e6ef713b1598f6acd7f302fa6b12b6731c89914
LinuxLinuxAffected
  • =6.2
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix key reference count leak from call->key When creating a client call in rxrpc_alloc_client_call(), the code obtains a reference to the key. This is never cleaned up and gets leaked when the call is destroyed. Fix this by freeing call->key in rxrpc_destroy_call(). Before the patch, it shows the key reference counter elevated: $ cat /proc/keys | grep afs@54321 1bffe9cd I--Q--i 8053480 4169w 3b010000 1000 1000 rxrpc afs@54321: ka $ After the patch, the invalidated key is removed when the code exits: $ cat /proc/keys | grep afs@54321 $

References

Community reviews

Loading reviews…