RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp
- 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.160, 6.12.108, 6.18.49, 7.1.13, 7.2.3
- 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/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp rxe_qp_from_attr() handles IB_QP_MAX_DEST_RD_ATOMIC outside the IB_QP_STATE path, so it holds no state_lock and runs while the responder task rxe_receiver() (recv_task on rxe_wq) is live. A modify_qp() setting only that attribute calls free_rd_atomic_resources() then alloc_rd_atomic_resources(), swapping qp->resp.resources[] while rxe_prepare_res()/find_resource() walk it; free_rd_atomic_resources() also leaves the cached pointer qp->resp.res dangling. A local unprivileged user can race the free/realloc into a use-after-free in rxe_receiver() (local DoS). Drain recv_task around the swap with rxe_disable_task()/rxe_enable_task(), as rxe_qp_reset() already does when tearing this array down, re-enabling only after alloc_rd_atomic_resources() succeeds so the responder never resumes against a NULL qp->resp.resources on the ENOMEM path. Also clear qp->resp.res in free_rd_atomic_resources(), like the rxe_resp.c completion paths. Reproduced under KASAN; the slab-use-after-free in rxe_receiver() is gone.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 82257379061c0a7aba6c77081d988339982af115; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 0136b528b753c5a56e4d997ef20b86bb6750b8fb; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in ffa4f0be69656be1755090f02db38d49816585c6; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in d4cd32eb8bd2b0ffbdc7b1f3d82ce6a371f8f844; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 60dfd47929cd1e7070daa810d40ce538d888410d; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 6f7014237405e7f032b5c53a82d9eccf6161c291
- Linux Linux
4.8
- KernelLinux
From 4.8.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.108; From 6.13.0 · fixed in 6.18.49; From 6.19.0 · fixed in 7.1.13; From 7.2.0 · fixed in 7.2.3