rxrpc: Fix key reference count leak from call->key (Linux Linux)

CVE-2026-31639
MEDIUM 5.5

At a glance

Source
NVD
EPSS
EPSS 0.12 % · percentile 2 ()
State
PUBLISHED
Published
Updated
Assigner
Linux
NVD status
Analyzed

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

Scores

VersionScoreVectorScored by
CVSS 3.1MEDIUM 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HNVD · nvd@nist.gov (Primary)

European references

CERT-FR advisories

Affected configurations (NVD CPE)

Affected products

ProductVersions
Linux · Linuxaffected f3441d4125fc98995858550a5521b8d7daf0504a < f1a7a3ab0f35f83cf11bba906b9e948cf3788c28 ; affected f3441d4125fc98995858550a5521b8d7daf0504a < e6b7943c5dc875647499da09bf4d50a8557ab0c3 ; affected f3441d4125fc98995858550a5521b8d7daf0504a < 2e6ef713b1598f6acd7f302fa6b12b6731c89914 ; affected f3441d4125fc98995858550a5521b8d7daf0504a < 978108902ee4ef2b348ff7ec36ad014dc5bc6dc6 ; affected f3441d4125fc98995858550a5521b8d7daf0504a < d666540d217e8d420544ebdfbadeedd623562733
Linux · Linuxaffected 6.2 ; unaffected 0 < 6.2 ; unaffected 6.6.135 ≤ 6.6.* ; unaffected 6.12.82 ≤ 6.12.* ; unaffected 6.18.23 ≤ 6.18.* ; unaffected 6.19.13 ≤ 6.19.*

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD