In the Linux kernel, the following vulnerability has been resolved:
nvmet: fix freeing unallocated p2pmem
In case p2p device was found but the p2p pool is empty, the nvme target
is still trying to free the sgl from the p2p pool instead of the
regular sgl pool and causing a crash (BUG() is called). Instead, assign
the p2p_dev for the request only if it was allocated from p2p pool.
This is the crash that was caused:
[Sun May 30 19:13:53 2021] ------------[ cut here ]------------
[Sun May 30 19:13:53 2021] kernel BUG at lib/genalloc.c:518!
[Sun May 30 19:13:53 2021] invalid opcode: 0000 [#1] SMP PTI
...
[Sun May 30 19:13:53 2021] kernel BUG at lib/genalloc.c:518!
...
[Sun May 30 19:13:53 2021] RIP: 0010:gen_pool_free_owner+0xa8/0xb0
...
[Sun May 30 19:13:53 2021] Call Trace:
[Sun May 30 19:13:53 2021] ------------[ cut here ]------------
[Sun May 30 19:13:53 2021] pci_free_p2pmem+0x2b/0x70
[Sun May 30 19:13:53 2021] pci_p2pmem_free_sgl+0x4f/0x80
[Sun May 30 19:13:53 2021] nvmet_req_free_sgls+0x1e/0x80 [nvmet]
[Sun May 30 19:13:53 2021] kernel BUG at lib/genalloc.c:518!
[Sun May 30 19:13:53 2021] nvmet_rdma_release_rsp+0x4e/0x1f0 [nvmet_rdma]
[Sun May 30 19:13:53 2021] nvmet_rdma_send_done+0x1c/0x60 [nvmet_rdma]
Security readout for executives and security teams
Plain-English summary
CVE-2021-47130 is a Linux kernel crash bug in the NVMe target path. Under a specific peer-to-peer memory condition, the kernel can try to free memory from the wrong pool and hit a BUG(), causing loss of availability. The CVSS vector requires local access with high privileges, reducing broad internet risk.
Executive priority
Schedule remediation through normal kernel patch cycles, with faster handling for storage infrastructure where NVMe target availability matters. This is not supported by the sources as remotely exploitable or actively exploited, but a kernel crash on storage hosts can still create meaningful operational disruption.
Technical view
The bug is in nvmet p2pmem handling. If a P2P device is found but the P2P pool is empty, nvmet can free an SGL through the P2P allocator even though it came from the regular pool. The reported failure path reaches gen_pool_free_owner via pci_p2pmem_free_sgl and nvmet_rdma_release_rsp, causing a kernel BUG crash.
Likely exposure
Exposure is most relevant to Linux systems using the NVMe target stack, especially nvmet RDMA with PCI peer-to-peer memory support. The source lists Linux kernel versions including 5.8, 5.10.43, 5.12.10, and 5.13 as affected context, with stable kernel commits referenced as fixes.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. CVSS indicates local attack vector, low complexity, high privileges, no user interaction, and availability impact only. Treat this mainly as a privileged local denial-of-service risk on specific NVMe target configurations.
Researcher notes
Evidence is strongest for availability impact from the included crash trace and CVSS vector. The source bundle does not provide a standalone workaround, exploit details, or distribution-specific fixed versions. Validation should rely on vendor kernel advisories and whether the referenced stable commits are present.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced nvmet p2pmem fix.
Prioritize NVMe target hosts using RDMA or PCI peer-to-peer memory.
If patching is delayed, check vendor guidance for avoiding the affected configuration.
Plan any required reboot or live patching through normal kernel maintenance procedures.
Validation and detection
Inventory Linux hosts running NVMe target services, especially nvmet_rdma.
Check kernel package advisories for CVE-2021-47130 or the referenced stable commits.
Review kernel logs for gen_pool_free_owner, pci_p2pmem_free_sgl, or nvmet_rdma crash traces.
Confirm patched hosts run a kernel build that includes the stable fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.