LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31635: rxrpc: fix oversized RESPONSE authenticator length check

In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix oversized RESPONSE authenticator length check rxgk_verify_response() decodes auth_len from the packet and is supposed to verify that it fits in the remaining bytes. The existing check is inverted, so oversized RESPONSE authenticators are accepted and passed to rxgk_decrypt_skb(), which can later reach skb_to_sgvec() with an impossible length and hit BUG_ON(len). Decoded from the original latest-net reproduction logs with scripts/decode_stacktrace.sh: RIP: __skb_to_sgvec() [net/core/skbuff.c:5285 (discriminator 1)] Call Trace: skb_to_sgvec() [net/core/skbuff.c:5305] rxgk_decrypt_skb() [net/rxrpc/rxgk_common.h:81] rxgk_verify_response() [net/rxrpc/rxgk.c:1268] rxrpc_process_connection() [net/rxrpc/conn_event.c:266 net/rxrpc/conn_event.c:364 net/rxrpc/conn_event.c:386] process_one_work() [kernel/workqueue.c:3281] worker_thread() [kernel/workqueue.c:3353 kernel/workqueue.c:3440] kthread() [kernel/kthread.c:436] ret_from_fork() [arch/x86/kernel/process.c:164] Reject authenticator lengths that exceed the remaining packet payload.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malformed network RESPONSE can exploit a Linux kernel length-check error and trigger a kernel assertion, potentially crashing the system. The documented impact is loss of availability, not data theft or modification. Risk is highest where the affected RxRPC/RXGK processing path is network-reachable.

Executive priority

Treat as a prompt availability-risk update for exposed or critical Linux systems. Prioritize internet-facing and high-availability workloads, while validating actual RxRPC/RXGK exposure and vendor package status before declaring broad impact.

Technical view

rxgk_verify_response() reverses the intended bounds check for the decoded authenticator length. An oversized value can reach rxgk_decrypt_skb() and then skb_to_sgvec() with an impossible length, triggering BUG_ON(len). The kernel fix rejects authenticator lengths exceeding the packet’s remaining payload.

Likely exposure

Potentially exposed systems run an affected Linux kernel and have the RxRPC/RXGK path present and network-reachable. The supplied version data does not clearly express exact ranges or distribution backports, so kernel package status must be confirmed through the applicable vendor.

Exploitation context

The CVSS vector describes network-accessible, low-complexity, unauthenticated denial of service without user interaction. A public repository is tagged as an exploit reference, but the supplied evidence does not establish its reliability or active exploitation. This CVE is not listed as KEV in the bundle.

Researcher notes

The root cause is CWE-130-style improper length interpretation: an inverted remaining-payload comparison admits an oversized authenticator. The demonstrated failure reaches a kernel BUG_ON through workqueue-based connection processing. Source data supports denial of service; it does not support confidentiality, integrity, code-execution, or in-the-wild exploitation claims.

Mitigation direction

  • Install a vendor kernel containing the applicable upstream or stable fix.
  • Check Linux distribution guidance for fixed package versions and backports.
  • Prioritize network-reachable systems using the RxRPC/RXGK processing path.
  • Reboot into the corrected kernel after installation, where required.

Validation and detection

  • Inventory running kernel versions on potentially exposed Linux systems.
  • Confirm the installed package includes the fix or an equivalent vendor backport.
  • Verify systems are running the corrected kernel after remediation.
  • Review kernel logs for skb_to_sgvec assertions or related RxRPC crashes.
Prepared
Confidence
high
Sources
6

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.

cwe · low confidence lookup

CWE-130: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-31635 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-31635Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a, 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a, 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54aunaffected
LinuxLinux6.16, 0, 6.18.23, 6.19.13, 7.0affected
Weakness

CWE details

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

CWE-130 · source CWE mapping

Improper Handling of Length Parameter Inconsistency

Improper Handling of Length Parameter Inconsistency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.