CVE-2026-31633·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix integer overflow in rxgk_verify_response() In rxgk_verify_response(), there's a potential integer overflow due to rounding up token_len before checking it, thereby allowing the length check to be bypassed. Fix this by checking the unrounded value against len too (len is limited as the response must fit in a single UDP packet).
- Severity
- critical
- Software
- Kernel
- Fixed in
- 6.19.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.47% — higher than 40% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-31633 scores 9.8 on CVSS, so a successful attack would be serious — but at 0.47%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.13
Fixed in: 6.19.13
How to fix this CVE
Update your Linux kernel to version 6.19.13 or later to patch an integer overflow vulnerability in the rxrpc subsystem's token verification logic. This vulnerability could allow an attacker to bypass length validation checks on network packets. Apply the kernel update through your distribution's package manager and reboot the system to complete remediation.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Run 'uname -r' to check your current kernel version—if it shows 6.19.0 through 6.19.12, you are vulnerable
- Verify rxrpc module is loaded by running 'lsmod | grep rxrpc'—if present, the vulnerable code path may be active
- Search kernel logs for rxrpc-related errors with 'dmesg | grep -i rxrpc' or 'journalctl -u kernel | grep -i rxrpc'
- Confirm the patch is applied by checking kernel version with 'uname -r'—should be 6.19.13 or later after update
FAQ
What is CVE-2026-31633?
This vulnerability exists in the Linux kernel's rxrpc (RX Remote Procedure Call) protocol handler, where an integer overflow in token length validation allows malicious packets to bypass security checks and potentially crash the system or cause unexpected behavior.
Is CVE-2026-31633 being actively exploited?
No, there are currently no public exploits or active exploitation reports for this vulnerability. However, the critical CVSS score (9.8) warrants prompt patching regardless of exploitation status.
What versions of Kernel are affected by CVE-2026-31633?
Linux kernel versions 6.19.0 through 6.19.12 are vulnerable. Version 6.19.13 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-31633?
Run 'uname -r' and compare your kernel version against the 6.19.0–6.19.12 range. If your version falls within this range, your system is vulnerable until updated.
Does Defensia detect CVE-2026-31633?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-31633 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-31633. Free for 1 server.
Get started free