{ "schema_version": "1.6.1", "id": "RPI-CVE-2025-38024", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2025-38024" ], "published": "2025-06-18T09:29:20Z", "summary": "RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug\n\nCall Trace:\n \n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x7d/0xa0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcf/0x610 mm/kasan/report.c:489\n kasan_report+0xb5/0xe0 mm/kasan/report.c:602\n rxe_queue_cleanup+0xd0/0xe0 drivers/infiniband/sw/rxe/rxe_queue.c:195\n rxe_cq_cleanup+0x3f/0x50 drivers/infiniband/sw/rxe/rxe_cq.c:132\n __rxe_cleanup+0x168/0x300 drivers/infiniband/sw/rxe/rxe_pool.c:232\n rxe_create_cq+0x22e/0x3a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1109\n create_cq+0x658/0xb90 drivers/infiniband/core/uverbs_cmd.c:1052\n ib_uverbs_create_cq+0xc7/0x120 drivers/infiniband/core/uverbs_cmd.c:1095\n ib_uverbs_write+0x969/0xc90 drivers/infiniband/core/uverbs_main.c:679\n vfs_write fs/read_write.c:677 [inline]\n vfs_write+0x26a/0xcc0 fs/read_write.c:659\n ksys_write+0x1b8/0x200 fs/read_write.c:731\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nIn the function rxe_create_cq, when rxe_cq_from_init fails, the function\nrxe_cleanup will be called to handle the allocated resources. In fact,\nsome memory resources have already been freed in the function\nrxe_cq_from_init. Thus, this problem will occur.\n\nThe solution is to let rxe_cleanup do all the work.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.47-1+rpt4" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" } ] }, "database_specific": { "per_version": { "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.140", "compiled_filter": false } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2025-38024" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/7c7c80c32e00665234e373ab03fe82f5c5c2c230" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/3a3b73e135e3bd18423d0baa72571319c7feb759" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/f8f470e3a757425a8f98fb9a5991e3cf62fc7134" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/52daccfc3fa68ee1902d52124921453d7a335591" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/ee4c5a2a38596d548566560c0c022ab797e6f71a" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/336edd6b0f5b7fbffc3e065285610624f59e88df" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/16c45ced0b3839d3eee72a86bb172bef6cf58980" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/f81b33582f9339d2dc17c69b92040d3650bb4bae" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T12:19:11Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.8, "cvss_v3_severity": "High", "scenario": "AV:L - The bug is triggered by a `write()` syscall on the `/dev/infiniband/uverbs0` character device issuing an `IB_USER_VERBS_CMD_CREATE_CQ` command; it requires local access to the system and is not reachable from any remote RoCE packet path.\nAC:L - The failure branch is entered by supplying a `response` pointer to unmapped/PROT_NONE memory so `copy_to_user()` in `do_mmap_info()` returns -EFAULT, which is fully attacker-controlled and 100% deterministic \u2014 no race needs to be won to reach the use-after-free and double-free.\nPR:L - `uverbs_devnode()` sets `/dev/infiniband/uverbs*` to mode 0666 and there is no capability check anywhere on the path from `ib_uverbs_write()` to `rxe_create_cq()`, so any unprivileged local user account can trigger it on a host with Soft-RoCE configured.\nUI:N - The attacker triggers the entire sequence from its own process with a single write() syscall; no victim action or interaction is involved.\nS:U - The corruption is confined to the kernel's own heap and vmalloc allocator within the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The dangling `struct rxe_queue` lands in the sprayable kmalloc-64 cache, and the resulting double-free/freelist aliasing plus the UAF read of `q->ip` enable object type confusion and arbitrary kernel memory disclosure.\nI:H - The double-free of both the slab object and the vmalloc buffer, combined with a potentially attacker-controlled `q->ip` reaching `kref_put()`/`rxe_mmap_release()` (arbitrary decrement, `list_del` unlink, arbitrary `vfree`/`kfree`), provides write primitives sufficient for control-flow hijacking and privilege escalation.\nA:H - Even without exploitation, the KASAN-reported use-after-free read followed by a duplicate `vfree()` of an already-released vmalloc area and a double `kfree()` reliably corrupts allocator state and panics the kernel, and it can be repeated at will." } } }