Home/CVE/In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: destroy cm id before destroy qp to avoid
CVE

CVE-2021-47378

In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: destroy cm id before destroy qp to avoid

In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: destroy cm id before destroy qp to avoid use after free We should always destroy cm_id before destroy qp to avoid to get cma event after qp was destroyed, which may lead to use after free. In RDMA connection establishment error flow, don't destroy qp in cm event handler.Just report cm_error to upper level, qp will be destroy in nvme_rdma_alloc_queue() after destroy cm id.

CRITICAL · CVSS 9.8 EPSS 0.00087
Schedule remediation
  • SSVC automatable: yes - attacks can be scripted at scale
  • CVSS base score ≥ 7.0
Sigma rules0 YARA rules0
Look this up elsewhere - one-click external pivots
NVDCVE.orgCISAVulnersExploit-DBGitHub PoCVulnCheck KEVGreyNoise
▸ How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2021-47378, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆

ATT&CK techniques

1

Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.

T1190 · Exploit Public-Facing Application
▤ Build a SIEM detection for these techniques
⬡

Weakness Classification

CWE-416Use After Free
▤

Affected Products & Versions

3
linux kernel< 5.10.70
linux kernel>= 5.11 and < 5.14.9
linux kernelall versions
▤

Affected Packages

40
Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Ubuntu:20.04:LTS linux
Ubuntu:20.04:LTS linux-aws
Ubuntu:20.04:LTS linux-aws-5.11
Ubuntu:20.04:LTS linux-aws-5.13
Ubuntu:20.04:LTS linux-aws-5.15 fixed in 5.15.0-1014.18~20.04.1
Ubuntu:20.04:LTS linux-aws-5.8
Ubuntu:20.04:LTS linux-azure
Ubuntu:20.04:LTS linux-azure-5.11
Ubuntu:20.04:LTS linux-azure-5.13
Ubuntu:20.04:LTS linux-azure-5.15 fixed in 5.15.0-1007.8~20.04.1
Ubuntu:20.04:LTS linux-azure-5.8
Ubuntu:20.04:LTS linux-azure-fde
Ubuntu:20.04:LTS linux-azure-fde-5.15 fixed in 5.15.0-1019.24~20.04.1.1
Ubuntu:20.04:LTS linux-bluefield
Ubuntu:20.04:LTS linux-gcp
Ubuntu:20.04:LTS linux-gcp-5.11
Ubuntu:20.04:LTS linux-gcp-5.13
Ubuntu:20.04:LTS linux-gcp-5.15 fixed in 5.15.0-1006.9~20.04.1
Ubuntu:20.04:LTS linux-gcp-5.8
Ubuntu:20.04:LTS linux-gke
Ubuntu:20.04:LTS linux-gke-5.15
Ubuntu:20.04:LTS linux-gkeop
Ubuntu:20.04:LTS linux-gkeop-5.15 fixed in 5.15.0-1003.5~20.04.2
Ubuntu:20.04:LTS linux-hwe-5.11
Ubuntu:20.04:LTS linux-hwe-5.13
Ubuntu:20.04:LTS linux-hwe-5.15 fixed in 5.15.0-33.34~20.04.1
Ubuntu:20.04:LTS linux-hwe-5.8
Ubuntu:20.04:LTS linux-ibm
Ubuntu:20.04:LTS linux-ibm-5.15 fixed in 5.15.0-1033.36~20.04.1
Ubuntu:20.04:LTS linux-intel-5.13
Ubuntu:20.04:LTS linux-intel-iotg-5.15 fixed in 5.15.0-1003.5~20.04.1
Ubuntu:20.04:LTS linux-iot
Ubuntu:20.04:LTS linux-kvm
Ubuntu:20.04:LTS linux-lowlatency-hwe-5.15 fixed in 5.15.0-33.34~20.04.1
Ubuntu:20.04:LTS linux-oem-5.10
Ubuntu:20.04:LTS linux-oem-5.13
Ubuntu:20.04:LTS linux-oem-5.14
Ubuntu:20.04:LTS linux-oem-5.6
Ubuntu:20.04:LTS linux-oracle
Ubuntu:20.04:LTS linux-oracle-5.11
📦

Fixed versions by distribution

80
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
rhel 8bpftool open
rhel 8kernel open
rhel 8kernel-abi-stablelists fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-core fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-debug open
rhel 8kernel-debug-core fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-debug-devel fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-debug-modules open
rhel 8kernel-debug-modules-extra open
rhel 8kernel-devel fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-modules fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-modules-extra open
rhel 8kernel-tools open
rhel 8kernel-tools-libs fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-tools-libs-devel open
rhel 8kernel-zfcpdump open
rhel 8kernel-zfcpdump-core open
rhel 8kernel-zfcpdump-devel fixed in 0:4.18.0-425.3.1.el8
rhel 8kernel-zfcpdump-modules open
rhel 8kernel-zfcpdump-modules-extra open
rhel 8perf open
rhel 8python3-perf fixed in 0:4.18.0-425.3.1.el8
rhel 9bpftool open
rhel 9kernel fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-abi-stablelists open
rhel 9kernel-core fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-debug open
rhel 9kernel-debug-core fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-debug-devel fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-debug-devel-matched open
rhel 9kernel-debug-modules fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-debug-modules-extra fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-devel open
rhel 9kernel-devel-matched fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-modules open
rhel 9kernel-modules-extra fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-tools open
rhel 9kernel-tools-libs fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-tools-libs-devel open
rhel 9kernel-zfcpdump open
rhel 9kernel-zfcpdump-core open
rhel 9kernel-zfcpdump-devel open
rhel 9kernel-zfcpdump-devel-matched fixed in 0:5.14.0-162.6.1.el9_1
rhel 9kernel-zfcpdump-modules open
rhel 9kernel-zfcpdump-modules-extra fixed in 0:5.14.0-162.6.1.el9_1
rhel 9perf open
rhel 9python3-perf fixed in 0:5.14.0-162.6.1.el9_1
suse sle15cluster-md-kmp-rt fixed in 0:5.14.21-150500.13.58.1
suse sle15dlm-kmp-rt fixed in 0:5.14.21-150500.13.58.1
suse sle15gfs2-kmp-rt fixed in 0:5.14.21-150500.13.58.1
suse sle15kernel-64kb fixed in 0:5.14.21-150400.24.122.2
suse sle15kernel-azure fixed in 0:5.14.21-150500.33.57.1
suse sle15kernel-default fixed in 0:5.3.18-150200.24.175.1
suse sle15kernel-default-base fixed in 0:5.3.18-150300.59.164.1.150300.18.96.1
suse sle15kernel-default-extra fixed in 0:5.14.21-150500.55.68.1
suse sle15kernel-default-livepatch fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-docs fixed in 0:5.3.18-150200.24.194.1
suse sle15kernel-livepatch-5_14_21-150400_24_122-default fixed in 0:1-150400.9.3.2
suse sle15kernel-livepatch-5_14_21-150500_13_58-rt fixed in 0:1-150500.11.3.1
suse sle15kernel-livepatch-5_14_21-150500_55_68-default fixed in 0:1-150500.11.3.1
suse sle15kernel-livepatch-5_3_18-150200_24_160-default fixed in 0:14-150200.2.1-0
suse sle15kernel-livepatch-5_3_18-150200_24_163-default fixed in 0:13-150200.2.1-0
suse sle15kernel-livepatch-5_3_18-150200_24_166-default fixed in 0:13-150200.2.1
suse sle15kernel-livepatch-5_3_18-150200_24_169-default fixed in 0:13-150200.2.1-0
suse sle15kernel-livepatch-5_3_18-150200_24_172-default fixed in 0:11-150200.2.1
suse sle15kernel-livepatch-5_3_18-150200_24_175-default fixed in 0:12-150200.2.1
suse sle15kernel-livepatch-5_3_18-150200_24_178-default fixed in 0:9-150200.2.1
suse sle15kernel-livepatch-5_3_18-150200_24_183-default fixed in 0:10-150200.5.6.1
suse sle15kernel-livepatch-5_3_18-150200_24_188-default fixed in 0:9-150200.5.6.1
suse sle15kernel-livepatch-5_3_18-150200_24_191-default fixed in 0:8-150200.5.6.1-0
suse sle15kernel-livepatch-5_3_18-150200_24_194-default fixed in 0:1-150200.5.3.1
suse sle15kernel-livepatch-5_3_18-150300_59_130-default fixed in 0:14-150300.2.1-0
suse sle15kernel-livepatch-5_3_18-150300_59_133-default fixed in 0:13-150300.2.1
suse sle15kernel-livepatch-5_3_18-150300_59_138-default fixed in 0:13-150300.2.1
suse sle15kernel-livepatch-5_3_18-150300_59_141-default fixed in 0:12-150300.2.1-0
suse sle15kernel-livepatch-5_3_18-150300_59_144-default fixed in 0:11-150300.2.1-0
suse sle15kernel-livepatch-5_3_18-150300_59_147-default fixed in 0:11-150300.2.1-0
suse sle15kernel-livepatch-5_3_18-150300_59_150-default fixed in 0:10-150300.2.1-0
suse sle15kernel-livepatch-5_3_18-150300_59_153-default fixed in 0:12-150300.7.6.1
suse sle15kernel-livepatch-5_3_18-150300_59_158-default fixed in 0:11-150300.7.6.1-0
▣

Scoring & Timeline

9.8
CRITICAL · CVSS v3.1 · 416baaa9-dc9f-4396-8d5f-8c081fb06d67
View on NVD
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
Published to NVD21 May 2024 · 03:15 PM
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑

Vendor Advisories

30
rhsaRHSA-2022:8267Low
rhsaRHSA-2022:7683Moderate
suse-csafSUSE-SU-2025:0244-1
suse-csafSUSE-SU-2025:0238-1
suse-csafSUSE-SU-2025:0240-1
🔗

References & Sources

3
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://git.kernel.org/stable/c/9817d763dbe15327b9b3ff4404fa6f27f927e744Patch
https://git.kernel.org/stable/c/d268a182c56e8361e19fb781137411643312b994Patch
https://git.kernel.org/stable/c/ecf0dc5a904830c926a64feffd8e01141f89822fPatch
SOC and Response
CVE triage
Stack monitoring
Am I affected
IOC triage
KEV catalog
Recently exploited
Daily brief
Change tracking
Detection Engineering
Coverage workspace
Detection coverage
Coverage check
Telemetry ceiling
SIEM query builder
Sigma rules
SIEM rules
YARA rules
Network rules
D3FEND
Threat Hunting
Threat actors
ATT&CK techniques
Attack paths
Indicators
Atomic tests
Red Team and Pentest
Exploitability triage
Recon pack
Attack paths
CAPEC patterns
Adversary emulation
Compliance and GRC
Framework mapping
Control assessment
Audit view
Atlas Search Threat actors Techniques Tools & malware CWE CAPEC KEV catalog Package vulns
About All capabilities Pricing API docs Live status Privacy policy Terms of service
threatengine.sh