CVE-2026-31638
What it is
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Only put the call ref if one was acquired rxrpc_input_packet_on_conn() can process a to-client packet after the current client call on the channel has already been torn down. In that case chan->call is NULL, rxrpc_try_get_call() returns NULL and there is no reference to drop. The client-side implicit-end error path does not account for that and unconditionally calls rxrpc_put_call(). This turns a protocol error path into a kernel crash instead of rejecting the packet. Only drop the call reference if one was actually acquired. Keep the existing protocol error handling unchanged.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Linux Kernel < 6.6.135
- Linux Kernel < 6.12.82
- Linux Kernel < 6.18.23
- Linux Kernel < 6.19.13
- Linux Kernel 6.2
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31638.md and follow it. Check whether this project is affected by CVE-2026-31638. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0c156aff8a2d4fa0d61db7837641975cf0e5452d
- https://git.kernel.org/stable/c/6331f1b24a3e85465f6454e003a3e6c22005a5c5
- https://git.kernel.org/stable/c/8299ca146489664e3c0c90a3b8900d8335b1ede4
- https://git.kernel.org/stable/c/9fb09861e2b8d1abfe2efaf260c9f1d30080ea38
- https://git.kernel.org/stable/c/b8f66447448d6c305a51413a67ec8ed26aa7d1dd
References
- https://git.kernel.org/stable/c/0c156aff8a2d4fa0d61db7837641975cf0e5452d
- https://git.kernel.org/stable/c/6331f1b24a3e85465f6454e003a3e6c22005a5c5
- https://git.kernel.org/stable/c/8299ca146489664e3c0c90a3b8900d8335b1ede4
- https://git.kernel.org/stable/c/9fb09861e2b8d1abfe2efaf260c9f1d30080ea38
- https://git.kernel.org/stable/c/b8f66447448d6c305a51413a67ec8ed26aa7d1dd