# rxrpc: Fix memory leaks in rxkad_verify_response()

CVE record · `CVE-2026-46012`

- **Identifiers:** `CVE-2026-46012`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 May 2026, 12:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `ec832bd06d6fdf08b0455ab7c2a7a9104e029638 to before c14433e967cff95bebc77c9c4a2a0ed4e0e22783` (git)
  - affected: `ec832bd06d6fdf08b0455ab7c2a7a9104e029638 to before c4b8f32e73eafd4a5076be890c7c8506ec04567c` (git)
  - affected: `ec832bd06d6fdf08b0455ab7c2a7a9104e029638 to before 852b9d64cea421336579b2de3d1338dfa677e2dd` (git)
  - affected: `ec832bd06d6fdf08b0455ab7c2a7a9104e029638 to before 861b9a0a1823bf064a7b810d29502a9ef043f40f` (git)
  - affected: `ec832bd06d6fdf08b0455ab7c2a7a9104e029638 to before c91f33fb8356dedc82bc56ce210f1a5dbee62a52` (git)
  - affected: `ec832bd06d6fdf08b0455ab7c2a7a9104e029638 to before 34f61a07e0cdefaecd3ec03bb5fb22215643678f` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.11`
  - unaffected: `before 5.11` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.140 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.86 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.27 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.4 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel's rxrpc networking code (the rxkad_verify_response() function) is affected in the listed version ranges, which begin at commit ec832bd06d6fdf08b0455ab7c2a7a9104e029638 and end before the fixed commits for each branch, and also cover kernel 5.11 onward until fixed in 6.1.191, 6.6.140, 6.12.86, or 6.18.27. The source gives few details about how an attacker reaches the code path. The flaw causes memory leaks, where a ticket and server key are not freed on some paths. Upgrade to a fixed kernel version from the stable branch that includes the fix.

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 May 2026, 12:56 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-46012)
- 27 May 2026, 14:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-46012)

## Sources

- [CVE List: CVE-2026-46012](https://www.cve.org/CVERecord?id=CVE-2026-46012)
- [NVD: CVE-2026-46012](https://nvd.nist.gov/vuln/detail/CVE-2026-46012)

### References from the CNA

- <https://git.kernel.org/stable/c/c14433e967cff95bebc77c9c4a2a0ed4e0e22783>
- <https://git.kernel.org/stable/c/c4b8f32e73eafd4a5076be890c7c8506ec04567c>
- <https://git.kernel.org/stable/c/852b9d64cea421336579b2de3d1338dfa677e2dd>
- <https://git.kernel.org/stable/c/861b9a0a1823bf064a7b810d29502a9ef043f40f>
- <https://git.kernel.org/stable/c/c91f33fb8356dedc82bc56ce210f1a5dbee62a52>
- <https://git.kernel.org/stable/c/34f61a07e0cdefaecd3ec03bb5fb22215643678f>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-46012>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-46012/>. Everything for agents: <https://agentprime.io/llms.txt>.
