RDMA/rxe: Fix double free in rxe_srq_from_init
- 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 4.20, 5.10.259, 5.15.210, 6.1.176, 6.6.128, and 3 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix double free in rxe_srq_from_init In rxe_srq_from_init(), the queue pointer 'q' is assigned to 'srq->rq.queue' before copying the SRQ number to user space. If copy_to_user() fails, the function calls rxe_queue_cleanup() to free the queue, but leaves the now-invalid pointer in 'srq->rq.queue'. The caller of rxe_srq_from_init() (rxe_create_srq) eventually calls rxe_srq_cleanup() upon receiving the error, which triggers a second rxe_queue_cleanup() on the same memory, leading to a double free. The call trace looks like this: kmem_cache_free+0x.../0x... rxe_queue_cleanup+0x1a/0x30 [rdma_rxe] rxe_srq_cleanup+0x42/0x60 [rdma_rxe] rxe_elem_release+0x31/0x70 [rdma_rxe] rxe_create_srq+0x12b/0x1a0 [rdma_rxe] ib_create_srq_user+0x9a/0x150 [ib_core] Fix this by moving 'srq->rq.queue = q' after copy_to_user.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in b98ab5494dbd48652561aa0b9c32f10500220745; From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in d493e0bfc748a520c349d6c8791b262aa5ad2e4e; From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in 9abff51163aa1bc275ec356f74fe976291860a7f; From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in 26793db60925df1e88a29466813d586cbc190b8c; From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in ce6f8e007682f378279d4cf83b240f12d52c723b; From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in 5c07aef09a121a4cd622a71eb0753a9e135c84a8; From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in 26a9cfe12f4ffdeaa136f252478986fa5f397ddc; From aae0484e15f062ad2c2502e68e15dfb8b8f84608 · fixed in 0beefd0e15d962f497aad750b2d5e9c3570b66d1; From 4.19.86 · fixed in 4.20
- Linux Linux
4.20
- KernelLinux
From 4.20.0 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.128; From 6.7.0 · fixed in 6.12.75; From 6.13.0 · fixed in 6.18.14; From 6.19.0 · fixed in 6.19.4
References 8
git.kernel.org
- stable/c/b98ab5494dbd48652561aa0b9c32f10500220745
- stable/c/d493e0bfc748a520c349d6c8791b262aa5ad2e4e
- stable/c/9abff51163aa1bc275ec356f74fe976291860a7f
- stable/c/26793db60925df1e88a29466813d586cbc190b8c
- stable/c/ce6f8e007682f378279d4cf83b240f12d52c723b
- stable/c/5c07aef09a121a4cd622a71eb0753a9e135c84a8
- stable/c/26a9cfe12f4ffdeaa136f252478986fa5f397ddc
- stable/c/0beefd0e15d962f497aad750b2d5e9c3570b66d1