CVE-2026-46012 json
rxrpc: Fix memory leaks in rxkad_verify_response()
published 2026-05-27 5 mo ago modified 2026-11-06 2 d ago also EUVD-2026-32309
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix memory leaks in rxkad_verify_response()
Fix rxkad_verify_response() to free the ticket and the server key under all circumstances by initialising the ticket pointer to NULL and then making all paths through the function after the first allocation has been done go through a single common epilogue that just releases everything - where all the releases skip on a NULL pointer.
Patch / fix
- Linux Linux 6.1.191, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1
- linux Debian 13 6.12.86-1
- linux Debian 14 7.0.4-1
debian advisories DEBIAN-CVE-2026-46012
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-27.27
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-aws Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1007.7
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1061.62
ubuntu advisories UBUNTU-CVE-2026-46012
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.0.11-1.1
opensuse advisories openSUSE-SU-2026:10954-1
- git.kernel.org/stable/c/c14433e967cff95bebc77c9c4a2a0ed4e0e22783 commit
- git.kernel.org/stable/c/c4b8f32e73eafd4a5076be890c7c8506ec04567c commit
- git.kernel.org/stable/c/852b9d64cea421336579b2de3d1338dfa677e2dd commit
- git.kernel.org/stable/c/861b9a0a1823bf064a7b810d29502a9ef043f40f commit
- git.kernel.org/stable/c/c91f33fb8356dedc82bc56ce210f1a5dbee62a52 commit
- git.kernel.org/stable/c/34f61a07e0cdefaecd3ec03bb5fb22215643678f commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-46012 updated cvss 6.5
kernel: rxrpc: Fix memory leaks in rxkad_verify_response()
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
- git.kernel.org /stable/c/c14433e967cff95bebc77c9c4a2a0ed4e0e22783
-
git.kernel.org
/stable/c/c4b8f32e73eafd4a5076be890c7c8506ec04567c
patch
-
git.kernel.org
/stable/c/852b9d64cea421336579b2de3d1338dfa677e2dd
patch
-
git.kernel.org
/stable/c/861b9a0a1823bf064a7b810d29502a9ef043f40f
patch
-
git.kernel.org
/stable/c/c91f33fb8356dedc82bc56ce210f1a5dbee62a52
patch
-
git.kernel.org
/stable/c/34f61a07e0cdefaecd3ec03bb5fb22215643678f
patch
Sources
- CVE List CVE-2026-46012
- NVD CVE-2026-46012
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.