CVE-2026-31493: Linux kernel · RDMA/efa: Fix use of completion ctx after free
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ef3b06742c8a201d0e83edc9a33a89a4fe3009f8 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ef3b06742c8a201d0e83edc9a33a89a4fe3009f8, 8c24b5179af260a5f36571c992d29aab1f448544, 7ba09d85f177e9f5f64b881f33dbcb57b2cf23d5 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/efa: Fix use of completion ctx after free On admin queue completion handling, if the admin command completed with error we print data from the completion context. The issue is that we already freed the completion context in polling/interrupts handler which means we print data from context in an unknown state (it might be already used again). Change the admin submission flow so alloc/dealloc of the context will be symmetric and dealloc will be called after any potential use of the context.
References
- git.kernel.org/stable/c/8c24b5179af260a5f36571c992d29aab1f448544 (opens in a new tab)
- git.kernel.org/stable/c/7ba09d85f177e9f5f64b881f33dbcb57b2cf23d5 (opens in a new tab)
- git.kernel.org/stable/c/0dd98aea1c0c45987fa2dd92f988b0eb1a72c125 (opens in a new tab)
- git.kernel.org/stable/c/1cf95fe5dc5471efea947b4c6f8913da6bc7976e (opens in a new tab)
- git.kernel.org/stable/c/ef3b06742c8a201d0e83edc9a33a89a4fe3009f8 (opens in a new tab)