Look up another CVE · open CVE-2026-31493 in the interactive tracker
CVE-2026-31493
RDMA/efa: Fix use of completion ctx after free
Published 2026-04-22 (6 months ago) by the Linux kernel CNA. Subsystem drivers/infiniband. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-31493 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 6.19.11-1 | Update the kernel and reboot. Fixed in 6.19.11-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.19.11-1 | Update the kernel and reboot. Fixed in 6.19.11-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/infiniband/hw/efa/efa_com.c
- What this is
- AMAZON RDMA EFA DRIVERMAINTAINERS section matched on drivers/infiniband/hw/efa/ · linux-rdma@vger.kernel.org · Supported
- Kernel module
- none to look for. The file would have gone into efa, and Debian does not compile it into that module, so finding efa in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_INFINIBAND|CONFIG_INFINIBAND_EFA' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_INFINIBAND, CONFIG_INFINIBAND_EFA
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-04-22 (6 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.17%, higher than 6.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/infiniband
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.12 | 6.18.21 | 0dd98aea1c0c |
| 5.12 | 6.19.11 | 1cf95fe5dc54 |
| 5.12 | 7.0 | ef3b06742c8a |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-31493, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.