FKIE_CVE-2026-99166
Vulnerability from fkie_nvd - Published: 2026-10-28 11:17 - Updated: 2026-10-30 13:21
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: rds: fix uninitialized trans dereference in CM event handler
rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA
device is an InfiniBand CA (RDMA_NODE_IB_CA). On any other device
type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but
the event switch dereferences it: unconditionally in the
RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(),
and (with a connection context) in the ROUTE_RESOLVED and
ESTABLISHED cases.
An RDS listener on an iWARP device therefore crashes the kernel as
soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO
the wild load becomes a NULL dereference at offset 0xa0
(&trans->cm_handle_connect) in the iw_cm_wq workqueue.
GCC masks the bug in default builds by folding the uninitialized
load into &rds_ib_transport; Clang-built kernels take the real
uninitialized path and oops.
The active side can land on a non-IB device too: the id that
rds_ib_conn_path_connect() creates is not restricted to a node type,
so rdma_resolve_addr() binds it to whichever device serves the local
address, and an iWARP RNIC on the same netdev qualifies. The crash
there is different: resolving a route on an iWARP id never fills in
cm_id->route.path_rec, and the ROUTE_RESOLVED case writes
path_rec[0].sl before it calls into the transport.
The iWARP transport was dropped long ago and IB is the only
transport left, so make that explicit: initialize trans to
&rds_ib_transport at declaration, drop the conditional assignment,
reject a connect request that arrives on a non-IB device, and drop a
connection whose address resolved to one instead of resolving a
route on it. The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST
on purpose: a non-zero return from the handler makes rdma_cm destroy
the id the event was delivered on, which is right for the request's
freshly created id but would free a connection id that RDS still owns
for any other event. On the active side the id stays ic->i_cm_id and
the connection's shutdown destroys it, so that case returns 0.
[achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of
bailing out for every event on a non-IB device, so that rdma_cm does
not destroy connection ids RDS still tracks; drop a connection whose
address resolved to a non-IB device before a route is resolved on it;
changelog adjusted]
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/rds/rdma_transport.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "0d15e853aa88da5375edd32b39d08a048b64a1c5",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
},
{
"lessThan": "8c77774535c3d6162929521a6fa11e3db086fa32",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
},
{
"lessThan": "8973f70cb068012d83cff1cfa3f45ef94ab02267",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
},
{
"lessThan": "a2fde862b98db8908e2ebaffbb35a75a0e9d5b33",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
},
{
"lessThan": "074bb7cdc3e26afa698888ba56fc1df0e3f24650",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
},
{
"lessThan": "5f23e4e3a31dacfd82a8f56be253adc0910ee84f",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
},
{
"lessThan": "ca14c289ed9ffed6cc64290d039e923e5720a8bf",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
},
{
"lessThan": "492ba6ac1b1ffb8a06ff52db0825c1af2cdb28c8",
"status": "affected",
"version": "dcdede0406d30e14a6ed727dce69dfac0518371d",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/rds/rdma_transport.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.6"
},
{
"lessThan": "4.6",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.273",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.224",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.191",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.161",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.115",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.59",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.13",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: rds: fix uninitialized trans dereference in CM event handler\n\nrds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA\ndevice is an InfiniBand CA (RDMA_NODE_IB_CA). On any other device\ntype, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but\nthe event switch dereferences it: unconditionally in the\nRDMA_CM_EVENT_CONNECT_REQUEST case via trans-\u003ecm_handle_connect(),\nand (with a connection context) in the ROUTE_RESOLVED and\nESTABLISHED cases.\n\nAn RDS listener on an iWARP device therefore crashes the kernel as\nsoon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO\nthe wild load becomes a NULL dereference at offset 0xa0\n(\u0026trans-\u003ecm_handle_connect) in the iw_cm_wq workqueue.\n\nGCC masks the bug in default builds by folding the uninitialized\nload into \u0026rds_ib_transport; Clang-built kernels take the real\nuninitialized path and oops.\n\nThe active side can land on a non-IB device too: the id that\nrds_ib_conn_path_connect() creates is not restricted to a node type,\nso rdma_resolve_addr() binds it to whichever device serves the local\naddress, and an iWARP RNIC on the same netdev qualifies. The crash\nthere is different: resolving a route on an iWARP id never fills in\ncm_id-\u003eroute.path_rec, and the ROUTE_RESOLVED case writes\npath_rec[0].sl before it calls into the transport.\n\nThe iWARP transport was dropped long ago and IB is the only\ntransport left, so make that explicit: initialize trans to\n\u0026rds_ib_transport at declaration, drop the conditional assignment,\nreject a connect request that arrives on a non-IB device, and drop a\nconnection whose address resolved to one instead of resolving a\nroute on it. The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST\non purpose: a non-zero return from the handler makes rdma_cm destroy\nthe id the event was delivered on, which is right for the request\u0027s\nfreshly created id but would free a connection id that RDS still owns\nfor any other event. On the active side the id stays ic-\u003ei_cm_id and\nthe connection\u0027s shutdown destroys it, so that case returns 0.\n\n[achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of\n bailing out for every event on a non-IB device, so that rdma_cm does\n not destroy connection ids RDS still tracks; drop a connection whose\n address resolved to a non-IB device before a route is resolved on it;\n changelog adjusted]"
}
],
"id": "CVE-2026-99166",
"lastModified": "2026-10-30T13:21:50.340",
"metrics": {},
"published": "2026-10-28T11:17:37.043",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/074bb7cdc3e26afa698888ba56fc1df0e3f24650"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0d15e853aa88da5375edd32b39d08a048b64a1c5"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/492ba6ac1b1ffb8a06ff52db0825c1af2cdb28c8"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5f23e4e3a31dacfd82a8f56be253adc0910ee84f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8973f70cb068012d83cff1cfa3f45ef94ab02267"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8c77774535c3d6162929521a6fa11e3db086fa32"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a2fde862b98db8908e2ebaffbb35a75a0e9d5b33"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ca14c289ed9ffed6cc64290d039e923e5720a8bf"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…