VYPR
Medium severity5.5NVD Advisory· Published Apr 24, 2026· Updated Apr 27, 2026

CVE-2026-31634

CVE-2026-31634

Description

In the Linux kernel, the following vulnerability has been resolved:

rxrpc: fix reference count leak in rxrpc_server_keyring()

This patch fixes a reference count leak in rxrpc_server_keyring() by checking if rx->securities is already set.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A reference count leak in rxrpc_server_keyring() in the Linux kernel could lead to resource exhaustion, fixed by checking if rx->securities is already set.

Vulnerability

CVE-2026-31634 describes a reference count leak in the rxrpc_server_keyring() function of the Linux kernel's RxRPC network protocol implementation. The function did not properly check if rx->securities was already initialized before setting it, leading to an increment of the reference count without a corresponding decrement under certain conditions.

Exploitation

An attacker would need to trigger the vulnerable code path to cause the reference count to be incremented multiple times. This could be achieved by repeatedly calling keyring-related operations that invoke rxrpc_server_keyring(). The vulnerability is local, requiring the ability to execute code or influence keyring operations on the system.

Impact

A reference count leak can eventually lead to resource exhaustion of kernel objects, potentially causing memory pressure or system instability. If the leak is severe, it might allow a local attacker to perform a denial-of-service (DoS) attack by exhausting memory. The CVSS score of 5.5 (Medium) reflects the local attack vector and confidentiality impact.

Mitigation

The Linux kernel community has addressed this issue by adding a check to ensure rx->securities is not already set before assigning it [1]. The fix has been backported to multiple stable kernels as indicated by the commit references [1][2][3][4]. Users are advised to update their kernels to include the patch.

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

9
  • Linux/Kernel9 versions
    cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*+ 8 more
    • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*range: >=2.6.22.1,<5.15.203
    • cpe:2.3:o:linux:linux_kernel:2.6.22:-:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

7

News mentions

0

No linked articles in our index yet.