RDMA: During rereg_mr ensure that REREG_ACCESS is compatible
- 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.143, 6.12.94, 6.18.36, 7.0.13
- 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: During rereg_mr ensure that REREG_ACCESS is compatible If IB_MR_REREG_ACCESS changes from RO to RW then the umem has to be re-evaluated to ensure it is properly pinned as RW. Since the umem is hidden inside each driver's mr struct add a ib_umem_check_rereg() function that each driver has to call before processing IB_MR_REREG_ACCESS. mlx4 has to retain its duplicate ib_access_writable check because it implements IB_MR_REREG_ACCESS | IB_MR_REREG_TRANS by changing both items in place sequentially while the MR is live, so it will continue to not support this combination.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From b40656aa7d559adc1fe689396dc58b92a9a27286 · fixed in 09dc18894148381d3bfc550083b1236043870dce; From b40656aa7d559adc1fe689396dc58b92a9a27286 · fixed in eba5df21eda0fe7418efbea2f799f8ea1b8ca94c; From b40656aa7d559adc1fe689396dc58b92a9a27286 · fixed in 2904e985a2917b5dac65df82733065e78a65fc9d; From b40656aa7d559adc1fe689396dc58b92a9a27286 · fixed in 50334a05a950840b39a1ce3d2a173b4183db9b3e; From b40656aa7d559adc1fe689396dc58b92a9a27286 · fixed in badad6fad60def1b9805559dd81dbab3d97b82aa
- Linux Linux
6.2
- KernelLinux
From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.94; From 6.13.0 · fixed in 6.18.36; From 6.19.0 · fixed in 7.0.13