dbcve.org
Linux KernelOperating system · Linux

CVE-2026-31643

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 6.18.23 / 6.19.13 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix key parsing memleak In rxrpc_preparse_xdr_yfs_rxgk(), the memory attached to token->rxgk can be leaked in a few error paths after it's allocated. Fix this by freeing it in the "reject_token:" case.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-401

Allocated memory is never released on some path, so a long-running service or a repeatedly triggered request steadily consumes memory until performance degrades or the process crashes. Attackers exploit it by simply driving the leaking path. Remediation is pairing every allocation with a release and using ownership patterns or tooling to catch what leaks.

General guidance for the memory leak class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.16.1, < 6.18.23>= 6.19, < 6.19.13= 6.16= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.18.23 / 6.19.13 or later
Fixed in 6.18.236.19.13
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 6.18.23 or later (6.18.y stable), or 6.19.13 or later (6.19.y stable), or corresponding fix in 7.0.y stable branch

  1. 1. Identify the current running Linux kernel version using `uname -r`
  2. 2. Check if the running version falls within the affected range: 6.16, 6.16.1-6.18.22, 6.19-6.19.12, or 7.0
  3. 3. Plan for a system reboot after kernel upgrade
  4. 4. Upgrade the Linux kernel package to version 6.18.23 or later for the 6.18.y branch
  5. 5. Alternatively, upgrade to version 6.19.13 or later for the 6.19.y branch
  6. 6. For systems running 7.0, upgrade to the corresponding fixed release in the 7.0.y stable branch
  7. 7. After upgrade, reboot the system to load the patched kernel
  8. 8. Verify the fix by checking the kernel version with `uname -r` and confirming the memory leak in rxrpc is resolved
Caveat Kernel upgrades may require matching kernel modules; ensure all proprietary drivers (e.g., NVIDIA, AMD) are compatible with the target kernel version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31643 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data