CVE-2026-90108
In the Linux kernel, the following vulnerability has been resolved:
net/smc: free stashed qentry before overwrite in REQ_ADD_LINK to ADD_LINK transition
When smc_llc_event_handler() transitions the local LLC flow from SMC_LLC_FLOW_REQ_ADD_LINK to SMC_LLC_FLOW_ADD_LINK on arrival of an ADD_LINK request, it calls smc_llc_flow_qentry_set() unconditionally:
A CONFIRM_LINK or ADD_LINK_CONT arriving while flow->type is SMC_LLC_FLOW_REQ_ADD_LINK is stashed into flow->qentry via the SMC_LLC_CONFIRM_LINK / SMC_LLC_ADD_LINK_CONT handler (which stores into flow->qentry for any non-NONE flow type). When the subsequent ADD_LINK arrives, the REQ_ADD_LINK branch overwrites flow->qentry with the new pointer without first freeing the stashed allocation, leaking one kmalloc object.
Leer descripción completaMostrar menos
The stashed entry has no consumer: smc_llc_wait() is only called from llc_add_link_work, which is not yet scheduled while the flow type remains REQ_ADD_LINK. No waiter is sleeping on llc_msg_waiter at this point. It is safe to unconditionally free any stashed qentry before the overwrite.
Call smc_llc_flow_qentry_del() before smc_llc_flow_qentry_set() in the REQ_ADD_LINK branch. smc_llc_flow_qentry_del() already checks flow->qentry before freeing, so the normal path where no entry is stashed is a no-op.
Detalles técnicos trazas, registros y código del informe original
if (lgr->llc_flow_lcl.type == SMC_LLC_FLOW_REQ_ADD_LINK) {
lgr->llc_flow_lcl.type = SMC_LLC_FLOW_ADD_LINK;
smc_llc_flow_qentry_set(&lgr->llc_flow_lcl, qentry);
...
}CVSS
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.21%
- Percentil entre todas las CVEs puntuadas: 10
- Fecha de la puntuación: 5/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
- https://git.kernel.org/stable/c/036322025d6e440cb75fc6fecbba9a16b271a2ae
- https://git.kernel.org/stable/c/056395acb7041b3a1f2baa08d89a1938a8b8776a
- https://git.kernel.org/stable/c/0fb9a513766071ea9d5f3bf988e39241b8e9ee3b
- https://git.kernel.org/stable/c/7dd55348c0d9399a9448847819e9f3904ae507ad
- https://git.kernel.org/stable/c/b08aacfb226a840628151643b6a34eecf545d311
- https://git.kernel.org/stable/c/e25a602c45c76a7130878db72bcf6f76df04bf85
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-90108",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "b4ba4652b3f8b7c9bbb5786f8acf4724bdab2196",
"lessThan": "7dd55348c0d9399a9448847819e9f3904ae507ad",
"versionType": "git"
},
{
"status": "affected",
"version": "b4ba4652b3f8b7c9bbb5786f8acf4724bdab2196",
"lessThan": "056395acb7041b3a1f2baa08d89a1938a8b8776a",
"versionType": "git"
},
{
"status": "affected",
"version": "b4ba4652b3f8b7c9bbb5786f8acf4724bdab2196",
"lessThan": "b08aacfb226a840628151643b6a34eecf545d311",
"versionType": "git"
},
{
"status": "affected",
"version": "b4ba4652b3f8b7c9bbb5786f8acf4724bdab2196",
"lessThan": "0fb9a513766071ea9d5f3bf988e39241b8e9ee3b",
"versionType": "git"
},
{
"status": "affected",
"version": "b4ba4652b3f8b7c9bbb5786f8acf4724bdab2196",
"lessThan": "e25a602c45c76a7130878db72bcf6f76df04bf85",
"versionType": "git"
},
{
"status": "affected",
"version": "b4ba4652b3f8b7c9bbb5786f8acf4724bdab2196",
"lessThan": "036322025d6e440cb75fc6fecbba9a16b271a2ae",
"versionType": "git"
}
],
"programFiles": [
"net/smc/smc_llc.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "5.16"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "5.16",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.1.188",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"net/smc/smc_llc.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-17T17:17:02.730",
"references": [
{
"url": "https://git.kernel.org/stable/c/036322025d6e440cb75fc6fecbba9a16b271a2ae",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/056395acb7041b3a1f2baa08d89a1938a8b8776a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/0fb9a513766071ea9d5f3bf988e39241b8e9ee3b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7dd55348c0d9399a9448847819e9f3904ae507ad",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b08aacfb226a840628151643b6a34eecf545d311",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e25a602c45c76a7130878db72bcf6f76df04bf85",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: free stashed qentry before overwrite in REQ_ADD_LINK to ADD_LINK transition\n\nWhen smc_llc_event_handler() transitions the local LLC flow from\nSMC_LLC_FLOW_REQ_ADD_LINK to SMC_LLC_FLOW_ADD_LINK on arrival of an ADD_LINK\nrequest, it calls smc_llc_flow_qentry_set() unconditionally:\n\n\tif (lgr->llc_flow_lcl.type == SMC_LLC_FLOW_REQ_ADD_LINK) {\n\t\tlgr->llc_flow_lcl.type = SMC_LLC_FLOW_ADD_LINK;\n\t\tsmc_llc_flow_qentry_set(&lgr->llc_flow_lcl, qentry);\n\t\t...\n\t}\n\nA CONFIRM_LINK or ADD_LINK_CONT arriving while flow->type is\nSMC_LLC_FLOW_REQ_ADD_LINK is stashed into flow->qentry via the\nSMC_LLC_CONFIRM_LINK / SMC_LLC_ADD_LINK_CONT handler (which stores into\nflow->qentry for any non-NONE flow type). When the subsequent ADD_LINK\narrives, the REQ_ADD_LINK branch overwrites flow->qentry with the new pointer\nwithout first freeing the stashed allocation, leaking one kmalloc object.\n\nThe stashed entry has no consumer: smc_llc_wait() is only called from\nllc_add_link_work, which is not yet scheduled while the flow type remains\nREQ_ADD_LINK. No waiter is sleeping on llc_msg_waiter at this point.\nIt is safe to unconditionally free any stashed qentry before\nthe overwrite.\n\nCall smc_llc_flow_qentry_del() before smc_llc_flow_qentry_set() in the\nREQ_ADD_LINK branch. smc_llc_flow_qentry_del() already checks flow->qentry\nbefore freeing, so the normal path where no entry is stashed is a no-op."
}
],
"lastModified": "2026-09-17T17:17:02.730",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}