LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46012: rxrpc: Fix memory leaks in rxkad_verify_response()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in RxRPC rxkad response verification. The fix ensures allocated ticket and server-key memory is released on every exit path. Business urgency is unclear because the source bundle provides no CVSS score, no severity rating, and no confirmed exploitation.

Executive priority

Track as kernel maintenance with targeted priority for systems using RxRPC/rxkad. Escalate only if vendor advisories later confirm meaningful exploitability, broad exposure, or higher severity.

Technical view

CVE-2026-46012 affects Linux kernel rxrpc code in rxkad_verify_response(). The resolved defect was missing cleanup for allocated ticket and server key objects on some paths. Upstream stable commits refactor cleanup through a common epilogue with NULL-safe releases.

Likely exposure

Exposure is most relevant to Linux systems using kernels listed as affected and with RxRPC/rxkad functionality present. The bundle does not confirm which distributions, configurations, or services expose the vulnerable path.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. It also does not define attacker prerequisites, network reachability, or practical impact beyond memory leakage.

Researcher notes

The available evidence supports a memory-management flaw fixed upstream, but not exploitability conclusions. Validate affectedness through kernel source/package lineage and configuration, especially distributor backports that may not match upstream version numbers exactly.

Mitigation direction

  • Apply kernel updates that include the referenced upstream stable fixes.
  • Check Linux distribution advisories for backported packages and fixed kernel builds.
  • Prioritize systems where RxRPC/rxkad is enabled or operationally required.
  • If no vendor update is available, monitor vendor guidance and reduce unnecessary RxRPC exposure.

Validation and detection

  • Identify running Linux kernel versions across the fleet.
  • Compare installed kernels with vendor fixed versions or referenced stable commits.
  • Confirm whether RxRPC/rxkad support is built in, loaded, or unused.
  • After updating, verify systems boot cleanly and dependent services still pass regression checks.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46012 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxec832bd06d6fdf08b0455ab7c2a7a9104e029638, ec832bd06d6fdf08b0455ab7c2a7a9104e029638, ec832bd06d6fdf08b0455ab7c2a7a9104e029638, ec832bd06d6fdf08b0455ab7c2a7a9104e029638, ec832bd06d6fdf08b0455ab7c2a7a9104e029638unaffected
LinuxLinux5.11, 0, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.