cve.bz

CVE-2026-31635 (DirtyCBC) linux linux kernel

7.5 highEPSS 1.1%Fix available

Known as DirtyCBC, DirtyDecrypt

High (7.5) in linux linux kernel. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
1.1% (unchanged from 1.1% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 68th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-05-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-130 Improper Handling of Length Parameter Inconsistency
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-31635 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-31635?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-31635?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-31635 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.23
Linux6.196.19.13
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux6.19.13-1DEBIAN-CVE-2026-31635
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-31635
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-31635
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-31635
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-31635
Ubuntu24.04:LTSlinux-aws-6.176.17.0-1019.19~24.04.1UBUNTU-CVE-2026-31635 USN-8490-1
Ubuntu24.04:LTSlinux-azure-6.176.17.0-1021.21~24.04.1UBUNTU-CVE-2026-31635 USN-8604-1
Ubuntu24.04:LTSlinux-azure-fde-6.176.17.0-1018.18~24.04.1USN-8605-1
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1020.22~24.04.1UBUNTU-CVE-2026-31635 USN-8490-1
Ubuntu24.04:LTSlinux-hwe-6.176.17.0-40.40~24.04.1UBUNTU-CVE-2026-31635 USN-8545-1
Ubuntu24.04:LTSlinux-nvidia-6.176.17.0-1026.26UBUNTU-CVE-2026-31635 USN-8508-1
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1028.28UBUNTU-CVE-2026-31635 USN-8491-1
Ubuntu24.04:LTSlinux-oracle-6.176.17.0-1018.18~24.04.1UBUNTU-CVE-2026-31635 USN-8490-1
12 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:10.2rv, perf, rtla and 87 more0:6.12.0-211.40.1.el10_2RHSA-2026:47017
AlmaLinux10kernel-doc, kernel-abi-stablelists6.12.0-211.40.1.el10_2ALSA-2026:47017
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-31635

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-211.40.1.el10_2Fixed 2026-07-28RHSA-2026:47017
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-31635.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-47 Buffer Overflow via Parameter Expansion Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON