Answer in brief
CVE-2026-89506 records a Unknown severity vulnerability in RDMA/uverbs: Add UVERBS_ATTR_UHW to UVERBS_METHOD_REG_MR. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5b2e45049dc06a876bc6b138218ddeb0814502ef <71d5c41ac583df09a7c32199bef7d42de7267d07 || >=5b2e45049dc06a876bc6b138218ddeb0814502ef <9e71d0f4944ba5641e01db29b3256c963656d671 || >=5b2e45049dc06a876bc6b138218ddeb0814502ef <011199f46f44a9fd93a9e5ab5d7fd1328d80e9bf | 71d5c41ac583df09a7c32199bef7d42de7267d07, 9e71d0f4944ba5641e01db29b3256c963656d671, 011199f46f44a9fd93a9e5ab5d7fd1328d80e9bf |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/uverbs: Add UVERBS_ATTR_UHW to UVERBS_METHOD_REG_MR The original commit missed that three drivers (mthca, irdma, siw) have UHW data associated with reg_mr that cannot be passed through the ioctl. They also assume that the udata cannot be NULL, so failing to pass a valid udata can trigger a NULL udata crash in those drivers. This never happens in real systems since in rdma-core ibv_cmd_reg_mr_ex() does not accept a udata and those three drivers don't use it, however a malicious userspace could trigger it.
Quoted source text, attributed separately from HOL analysis.