# CVE-2022-48925: linux: In the Linux kernel, the following vulnerability has been resolved:  RDMA/cma: Do not change route.addr.src_addr outs...

CVE-2022-48925 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-48925, released August 22, 2024. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2022-48925
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0022
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 22, 2024

## Description

In the Linux kernel, the following vulnerability has been resolved:  RDMA/cma: Do not change route.addr.src_addr outside state checks  If the state is not idle then resolve_prepare_src() should immediately fail and no change to global state should happen. However, it unconditionally overwrites the src_addr trying to build a temporary any address.  For instance if the state is already RDMA_CM_LISTEN then this will corrupt the src_addr and would cause the test in cma_cancel_operation():             if (cma_any_addr(cma_src_addr(id_priv)) && !id_priv->cma_dev)  Which would manifest as this trace from syzkaller:    BUG: KASAN: use-after-free in __list_add_valid+0x93/0xa0 lib/list_debug.c:26   Read of size 8 at addr ffff8881546491e0 by task syz-executor.1/32204    CPU: 1 PID: 32204 Comm: syz-executor.1 Not tainted 5.12.0-rc8-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011   Call Trace:    __dump_stack lib/dump_stack.c:79 [inline]    dump_stack+0x141/0x1d7 lib/dump_stack.c:120    print_address_description.constprop.0.cold+0x5b/0x2f8 mm/kasan/report.c:232    __kasan_report mm/kasan/report.c:399 [inline]    kasan_report.cold+0x7c/0xd8 mm/kasan/report.c:416    __list_add_valid+0x93/0xa0 lib/list_debug.c:26    __list_add include/linux/list.h:67 [inline]    list_add_tail include/linux/list.h:100 [inline]    cma_listen_on_all drivers/infiniband/core/cma.c:2557 [inline]    rdma_listen+0x787/0xe00 drivers/infiniband/core/cma.c:3751    ucma_listen+0x16a/0x210 drivers/infiniband/core/ucma.c:1102    ucma_write+0x259/0x350 drivers/infiniband/core/ucma.c:1732    vfs_write+0x28e/0xa30 fs/read_write.c:603    ksys_write+0x1ee/0x250 fs/read_write.c:658    do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46    entry_SYSCALL_64_after_hwframe+0x44/0xae  This is indicating that an rdma_id_private was destroyed without doing cma_cancel_listens().  Instead of trying to re-use the src_addr memory to indirectly create an any address derived from the dst build one explicitly on the stack and bind to that as any other normal flow would do. rdma_bind_addr() will copy it over the src_addr once it knows the state is valid.  This is similar to commit bc0bdc5afaa7 ("RDMA/cma: Do not change route.addr.src_addr.ss_family")

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 5.16.12-1 | [DEBIAN-CVE-2022-48925](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48925.md) | Aug 22, 2024 |
| Linux | linux Debian 13.5 (trixie) | 5.16.12-1 | [DEBIAN-CVE-2022-48925](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48925.md) | Aug 22, 2024 |
| Linux | linux Debian 14 | 5.16.12-1 | [DEBIAN-CVE-2022-48925](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48925.md) | Aug 22, 2024 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.