Linux
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a, < beee051f259acd286fed64c32c2b31e6f5097eb5
- >= 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a, < e2f1a80d8b1ed6a5ae585a399c2b46500bdcc305
- >= 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a, < a2567217ade970ecc458144b6be469bc015b23e5
Fixed in beee051f259acd286fed64c32c2b31e6f5097eb5, e2f1a80d8b1ed6a5ae585a399c2b46500bdcc305, a2567217ade970ecc458144b6be469bc015b23e5
- 6.16
Fixed in 0, 6.18.23, 6.19.13, 7.0
Mitigation
Upgrade Linux to beee051f259acd286fed64c32c2b31e6f5097eb5 or e2f1a80d8b1ed6a5ae585a399c2b46500bdcc305 or a2567217ade970ecc458144b6be469bc015b23e5 or later.
Upgrade Linux to 0 or 6.18.23 or 6.19.13 or 7.0 or later.
Timeline
Days relative to CVE publicationFirst public PoC 25 days after publication; not in CISA KEV. First PoC: 0xBlackash/CVE-2026-31635 (created 19 May 2026, found by us: backfilled).
PoC repositories
Found on GitHub.5 PoCs
PoCs 5
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 0xBlackash/CVE-2026-31635 | 19 May 2026 +25 d | 8 | PoC |
| 0xredash/CVE-2026-31635 | 19 May 2026 +25 d | 8 | PoC |
| ashrafzaryouh/CVE-2026-31635 | 19 May 2026 +25 d | 8 | PoC |
| 0xFuffM3/CVE-2026-31635-DirtyDecrypt | 21 May 2026 +27 d | 3 | PoC |
| Koshmare-Blossom/DirtyDecrypt-go | 21 May 2026 +27 d | 0 | PoC via PoC Index
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| CVE record (tagged exploit) | https://github.com/v12-security/pocs/tree/main/dirtydecrypt | unknown | 14 Nov 2026 |