RDMA/irdma: Prevent rereg_mr for non-mem regions
- 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.6.148, 6.12.101, 6.18.42, 7.1.6
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Prevent rereg_mr for non-mem regions When a QP/CQ/SRQ is created, a two step process is used where the buffer is allocated in userspace and explicitly registered with the normal reg_mr mechanism prior to creating the actual QP/CQ/SRQ object. These special registrations are indicated via an ABI field so the driver knows that they do not have a valid mkey and to skip the actual CQP command submission. Since these are real MR objects from the core's perspective, it is possible for a user application to invoke rereg_mr on them and cause a real CQP op to be emitted with the zero-initialized mkey value of 0. Fix this by preventing rereg_mr on these special regions.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 715fdb3b30541cc8180b7cdc6aa9f8c307afdf25 · fixed in fb46d134e1b8690bed2da9005b36d32d2efd34ac; From 5ac388db27c443dadfbb0b8b23fa7ccf429d901a · fixed in b5029e91c63406e4f4c8d58161048b41b6f0bd8c; From 5ac388db27c443dadfbb0b8b23fa7ccf429d901a · fixed in ca1c29f05274b737dc964e28b97803750d7cf7ec; From 5ac388db27c443dadfbb0b8b23fa7ccf429d901a · fixed in dbaa37e060918c45517786e37ecab0f300b48fa9; From 5ac388db27c443dadfbb0b8b23fa7ccf429d901a · fixed in a846aecb931b4d65d5eafa92a0623545af46d4f2; From 6.6.120 · fixed in 6.6.148
- Linux Linux
6.7
- KernelLinux
fixed in 6.6.148; From 6.7.0 · fixed in 6.12.101; fixed in 6.18.42; From 6.13.0 · fixed in 7.1.6