RDMA/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[]
- 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.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.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
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[] For a user QP, qp->sq.queue is a ring the application writes directly, so rxe_post_send() takes the is_user branch and only schedules send_task without validating the WQE. rxe_requester() consumes it in place via req_next_wqe() and calls copy_data(), which indexes &wqe->dma.sge[cur_sge] with the attacker-controlled num_sge/cur_sge. Only the kernel path bounds num_sge (validate_send_wr()); the user WQE is never checked, so a local unprivileged user can post a WQE with an out-of-range cur_sge or oversized num_sge and force an out-of-bounds read of the per-WQE sge array in copy_data() (vmalloc OOB read, local DoS). Bound num_sge to qp->sq.max_sge in rxe_requester() before use, the way get_srq_wqe() already guards SRQ entries, and bound cur_sge only when the WQE carries payload (dma.resid): copy_data() returns early on a zero-length copy before touching dma->sge[], so a zero-payload WQE -- the only kind a max_sge == 0 QP can post -- stays valid. Reproduced under KASAN; the vmalloc-out-of-bounds in copy_data() is gone.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 69d3ccf6543f24c452a020c8028ca6f46cb1e8db; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 750bba6ce9bb0b11d6a166031c9728ae3f21765e; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in c067aa7b231e91a18a1b3666201ab14dfb00347a; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 13cb7160e5b791f5e3ecf9311cf32849fe7e9b62; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 5ec111ddc1f727c1e4580aea459842ae5a8359a5; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 126c757e4cd46f866ddc283143b58eb4d9bf52cd
- Linux Linux
4.8
- KernelLinux
From 4.8.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6