RDMA/mad: Fix receive buffer leak when PKey enforcement fails
- 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 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- 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: RDMA/mad: Fix receive buffer leak when PKey enforcement fails ib_mad_complete_recv() initializes mad_recv_wc->rmpp_list and then runs ib_mad_enforce_security() before linking recv_buf onto that list. On failure it calls ib_free_recv_mad(), which only walks rmpp_list and frees the ib_mad_private of every buffer found there. As the list is still empty at that point, nothing is freed at all. The caller cannot clean up either: ib_mad_recv_done() sets recv to NULL right after ib_mad_complete_recv() returns, assuming the MAD layer took ownership of the buffer. Every MAD that fails the PKey check therefore leaks one ib_mad_private (about 300 bytes per IB port MAD, ~2K for OPA), and a remote node can trigger this repeatedly by sending MADs with a wrong PKey. Link recv_buf onto rmpp_list right after the list is initialized, so the error path has something to free.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in 4617c9a856188674dddb0ca66979746d07688579; From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in 8e2036fb47a5b152d53eadbd35abf311bd34cc7f; From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in bad289e42f512646a988f278f536d21547df73f1; From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in 752b30e9d339008e5ce7eed412e9446078916129; From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in 39c4ea72a40503e102ae07e6776005f96ca078a6; From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in 5091e25ec503f7fc02723ca435226467b68caac7; From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in c0d8df85db146d6275e226cb950023be69dd6c77; From 47a2b338fe63200d716d2e24131cdb49f17c77da · fixed in 3476c28c9addfa253f505e6bd87f1f5598b961d0
- Linux Linux
4.13
- KernelLinux
From 4.13.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 8
git.kernel.org
- stable/c/4617c9a856188674dddb0ca66979746d07688579
- stable/c/8e2036fb47a5b152d53eadbd35abf311bd34cc7f
- stable/c/bad289e42f512646a988f278f536d21547df73f1
- stable/c/752b30e9d339008e5ce7eed412e9446078916129
- stable/c/39c4ea72a40503e102ae07e6776005f96ca078a6
- stable/c/5091e25ec503f7fc02723ca435226467b68caac7
- stable/c/c0d8df85db146d6275e226cb950023be69dd6c77
- stable/c/3476c28c9addfa253f505e6bd87f1f5598b961d0