UBUNTU-CVE-2021-47378
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.
02 / AFFECTED SOFTWARE
Affected packages
53 explicit affected versions
116 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
6 explicit affected versions
91 explicit affected versions
7 explicit affected versions
84 explicit affected versions
35 explicit affected versions
18 explicit affected versions
117 explicit affected versions
120 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
124 explicit affected versions
1 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
76 explicit affected versions
7 explicit affected versions
12 explicit affected versions
110 explicit affected versions
12 explicit affected versions
1 explicit affected versions
7 explicit affected versions
104 explicit affected versions
12 explicit affected versions
105 explicit affected versions
12 explicit affected versions
10 explicit affected versions
37 explicit affected versions
10 explicit affected versions
1 explicit affected versions
26 explicit affected versions
13 explicit affected versions
1 explicit affected versions
29 explicit affected versions
111 explicit affected versions
13 explicit affected versions
1 explicit affected versions
100 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
11 explicit affected versions
12 explicit affected versions
7 explicit affected versions
12 explicit affected versions
137 explicit affected versions
130 explicit affected versions
152 explicit affected versions
10 explicit affected versions
26 explicit affected versions
13 explicit affected versions
137 explicit affected versions
78 explicit affected versions
16 explicit affected versions
114 explicit affected versions
3 explicit affected versions
132 explicit affected versions
92 explicit affected versions
1 explicit affected versions
51 explicit affected versions
91 explicit affected versions
12 explicit affected versions
27 explicit affected versions
121 explicit affected versions
1 explicit affected versions
1 explicit affected versions
96 explicit affected versions
8 explicit affected versions
5 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
110 explicit affected versions
13 explicit affected versions
72 explicit affected versions
7 explicit affected versions
139 explicit affected versions
92 explicit affected versions
10 explicit affected versions
12 explicit affected versions
108 explicit affected versions
80 explicit affected versions
56 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
37 explicit affected versions
38 explicit affected versions
165 explicit affected versions
9 explicit affected versions
11 explicit affected versions
7 explicit affected versions
120 explicit affected versions
4 explicit affected versions
43 explicit affected versions
77 explicit affected versions
119 explicit affected versions
10 explicit affected versions
8 explicit affected versions
88 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
1 explicit affected versions
68 explicit affected versions
123 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
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.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/9817d763dbe15327b9b3ff4404fa6f27f927e744
- https://git.kernel.org/stable/c/9817d763dbe15327b9b3ff4404fa6f27f927e744
- https://git.kernel.org/stable/c/d268a182c56e8361e19fb781137411643312b994
- https://git.kernel.org/stable/c/ecf0dc5a904830c926a64feffd8e01141f89822f
- https://ubuntu.com/security/CVE-2021-47378
- https://ubuntu.com/security/notices/USN-8633-1
- https://ubuntu.com/security/notices/USN-8633-2
- https://ubuntu.com/security/notices/USN-8635-1
- https://ubuntu.com/security/notices/USN-8645-1
- https://www.cve.org/CVERecord?id=CVE-2021-47378