# CVE-2026-89507: linux: In the Linux kernel, the following vulnerability has been resolved:  RDMA/ucma: Lock the handler in ucma_write_cm_eve...

CVE-2026-89507 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-89507, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-89507
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0013
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Sep 11, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  RDMA/ucma: Lock the handler in ucma_write_cm_event()  ctx->file may only be changed under the handler lock and the xa_lock, which is what stops uevents being queued for a ctx while ucma_migrate_id() moves it to another file.  The CM core takes that lock before invoking ucma_event_handler(), but the write() paths that queue uevents themselves do not.  ucma_write_cm_event() re-reads ctx->file for each of its four dereferences, so ucma_migrate_id() can swap it mid-sequence:  	mutex_lock(&ctx->file->mut);			/* file A */ 	list_add_tail(&uevent->list, &ctx->file->event_list);	/* file B */ 	mutex_unlock(&ctx->file->mut);			/* file B */ 	wake_up_interruptible(&ctx->file->poll_wait);	/* file B */  The window is the mutex_lock() itself: the writer sleeps in it while the migration reassigns ctx->file.  The list_add_tail() then runs on file B's event_list holding only file A's mutex:    list_add corruption. prev->next should be next (ffff888101320f30),     but was ffff88814a08c418. (prev=ffff88814a075c18).   kernel BUG at lib/list_debug.c:32!   Call Trace:    ucma_write_cm_event+0x36e/0x5e0  and file A's mut is left held forever, wedging its next writer in D state. The uevent is also stranded on a list ucma_cleanup_ctx_events() will not walk, so it outlives its context.  /dev/infiniband/rdma_cm is 0666 and no RDMA device is involved, so an unprivileged user reaches all of this.  Take the handler lock, as ucma_cleanup_mc_events() does; ctx->cm_id is pinned by the ucma_get_ctx() reference.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | bpftool6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel-livepatch-6.18.51-120.162 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-devel amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-headers amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-tools amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | linux Debian 14 | 7.2.6-1 | [DEBIAN-CVE-2026-89507](https://patchblox.com/security/data/fix/linux/debian-cve-2026-89507.md) | Sep 23, 2026 |
| Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | perf6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | python3-perf6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |
| Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 |

---

Data as of 2026-11-08T13:06:02Z 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.
