Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31641: rxrpc: Fix RxGK token loading to check bounds

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3e04596cba8a86cbff9c3f4bf0a524a3a488773c, 49875b360c2b83a3c226e189c502e501d83e6445, d179a868dd755b0cfcf7582e00943d702b9943b8.

Low priority for now. Upgrade to Linux Linux 3e04596cba8a86cbff9c3f4bf0a524a3a488773c, 49875b360c2b83a3c226e189c502e501d83e6445, d179a868dd755b0cfcf7582e00943d702b9943b8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix RxGK token loading to check bounds rxrpc_preparse_xdr_yfs_rxgk() reads the raw key length and ticket length from the XDR token as u32 values and passes each through round_up(x, 4) before using the rounded value for validation and allocation. When the raw length is >= 0xfffffffd, round_up() wraps to 0, so the bounds check and kzalloc both use 0 while the subsequent memcpy still copies the original ~4 GiB value, producing a heap buffer overflow reachable from an unprivileged add_key() call. Fix this by: (1) Rejecting raw key lengths above AFSTOKEN_GK_KEY_MAX and raw ticket lengths above AFSTOKEN_GK_TOKEN_MAX before rounding, consistent with the caps that the RxKAD path already enforces via AFSTOKEN_RK_TIX_MAX. (2) Sizing the flexible-array allocation from the validated raw key length via struct_size_t() instead of the rounded value. (3) Caching the raw lengths so that the later field assignments and memcpy calls do not re-read from the token, eliminating a class of TOCTOU re-parse. The control path (valid token with lengths within bounds) is unaffected.

Published
Apr 24, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31641

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.16affected
    • 0ca100ff4df64f5d0f6c1dd5080c3e096786bea6 and later · before 3e04596cba8a86cbff9c3f4bf0a524a3a488773caffected · git
    • 0ca100ff4df64f5d0f6c1dd5080c3e096786bea6 and later · before 49875b360c2b83a3c226e189c502e501d83e6445affected · git
    • 0ca100ff4df64f5d0f6c1dd5080c3e096786bea6 and later · before d179a868dd755b0cfcf7582e00943d702b9943b8affected · git
    • before 6.16not affected · semver
    • 6.18.23 and later · up to and including 6.18.*not affected · semver
    • 6.19.13 and later · up to and including 6.19.*not affected · semver
    • 7.0 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31639Apr 24, 2026 · rxrpc: Fix key reference count leak from call->key
    22Monitor
  • ← EarlierCVE-2026-31640Apr 24, 2026 · rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial
    30Monitor
  • Later →CVE-2026-31642Apr 24, 2026 · rxrpc: Fix call removal to use RCU safe deletion
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3e04596cba8a86cbff9c3f4bf0a524a3a488773cVendor (CNA)
Linux Linux49875b360c2b83a3c226e189c502e501d83e6445Vendor (CNA)
Linux Linuxd179a868dd755b0cfcf7582e00943d702b9943b8Vendor (CNA)
almalinux:kernel6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.19.13-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:kernel0:6.12.0-211.26.1.el10_2 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

All records