CVE-2026-46012: Linux kernel · rxrpc: Fix memory leaks in rxkad_verify_response()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c14433e967cff95bebc77c9c4a2a0ed4e0e22783 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 12:36 UTC
Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in c14433e967cff95bebc77c9c4a2a0ed4e0e22783, c91f33fb8356dedc82bc56ce210f1a5dbee62a52, c4b8f32e73eafd4a5076be890c7c8506ec04567c +3
Exploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available in the Linux kernel source code as indicated by the listed fixed commit versions. Users and administrators should update their Linux kernel to a version that includes these fixes to remediate the memory leak. No additional mitigation steps are indicated or necessary beyond applying the official patch.
Description
A memory leak vulnerability in the Linux kernel's rxrpc component was fixed in the rxkad_verify_response() function. The issue was due to improper freeing of allocated memory for the ticket and server key under all code paths. The fix ensures that all allocated resources are released properly by initializing pointers to NULL and consolidating cleanup into a single common epilogue.
References
- git.kernel.org/stable/c/c14433e967cff95bebc77c9c4a2a0ed4e0e22783 (opens in a new tab)
- git.kernel.org/stable/c/c4b8f32e73eafd4a5076be890c7c8506ec04567c (opens in a new tab)
- git.kernel.org/stable/c/852b9d64cea421336579b2de3d1338dfa677e2dd (opens in a new tab)
- git.kernel.org/stable/c/861b9a0a1823bf064a7b810d29502a9ef043f40f (opens in a new tab)
- git.kernel.org/stable/c/c91f33fb8356dedc82bc56ce210f1a5dbee62a52 (opens in a new tab)
- git.kernel.org/stable/c/34f61a07e0cdefaecd3ec03bb5fb22215643678f (opens in a new tab)