nvmet: pci-epf: put CQ ref on create_cq mapping failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.47, 7.1.11, 7.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: nvmet: pci-epf: put CQ ref on create_cq mapping failure nvmet_pci_epf_create_cq() calls nvmet_cq_create(), which takes a reference on the controller and installs the completion queue. If the subsequent PCI address-space mapping fails or returns a too-small partial mapping, the function jumps to err_internal / err_unmap_queue without calling nvmet_cq_put(). The matching put in nvmet_pci_epf_delete_cq() is gated on NVMET_PCI_EPF_Q_LIVE, which is only set after the mapping succeeds, so teardown never releases these references. A remote PCI host that drives Create IO CQ commands with a failing PRP1/pci_addr therefore leaks the CQ and a controller reference on each attempt. Drop the CQ reference on the mapping-failure paths. The err_internal and err_unmap_queue labels are only reachable after nvmet_cq_create() has succeeded, so this pairs the create/put correctly.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 · fixed in f31650243c1ab32394077f234685e89ed8dece84; From 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 · fixed in b5f97fae2503a763fa0f953abf5f121b0fef7d0d; From 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 · fixed in 56a7b6a6880dbabe28214ff88df8d229ca3a944a; From 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 · fixed in 659ae9d02cb5d72c76f74fff7441eb8fb64d8f5c
- Linux Linux
6.14
- KernelLinux
From 6.14.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1