CVE-2026-98632
En el kernel de Linux se ha resuelto la siguiente vulnerabilidad:
Bluetooth: mgmt: Desencolar las entradas pendientes de mesh_send_sync al cancelar
En send_cancel(), los objetos mesh_tx pendientes se eliminan de la lista hdev->mesh_pending y se liberan mediante mesh_send_complete(). Sin embargo, si una transmisión de malla ya se había encolado en hdev->cmd_sync_work_list mediante mesh_next(), la entrada encolada conserva un puntero sin procesar a mesh_tx.
Cuando hci_cmd_sync_work procesa posteriormente la entrada, intenta ejecutar mesh_send_sync y su callback de destrucción mesh_send_start_complete usando el puntero mesh_tx ya liberado, lo que provoca un use-after-free (uso de memoria liberada).
Leer descripción completaMostrar menos
Para corregirlo, se invoca hci_cmd_sync_dequeue() para mesh_send_sync sobre el mesh_tx de destino antes de completarlo. Si la entrada se encuentra y se desencola, su callback de destrucción completará y liberará el objeto; en caso contrario, se llama directamente a mesh_send_complete().
Además, se asegura que la cola de transmisión avance tras una cancelación o un error. En mesh_send_start_complete(), se llama a mesh_next() en caso de error salvo que err sea -ECANCELED, porque hci_cmd_sync_dequeue() mantiene hdev->cmd_sync_work_lock y llamar a mesh_next() de forma síncrona provocaría un interbloqueo. En su lugar, la cola se hace avanzar en send_cancel() una vez liberado el bloqueo y si no hay ninguna transmisión en curso.
Traducción automática del texto original de NVD (en inglés).
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.17 %
- Percentil entre todas las CVEs puntuadas
- 6
- Fecha de la puntuación
- 20/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
Mostrar las 6 referencias
- https://git.kernel.org/stable/c/03ced4687fb79286be7fdee0fc58d2c74de3e7bb
- https://git.kernel.org/stable/c/084be90948632a5a358821e687b11a14445aae76
- https://git.kernel.org/stable/c/2189a219397d8e73808a67c4aade837b635705da
- https://git.kernel.org/stable/c/718a8ffa180d469f99ad4f746f00cafd39456415
- https://git.kernel.org/stable/c/71af682ba4692c2ed9ace4c3d4ca462ae368c029
- https://git.kernel.org/stable/c/f84e52829021d00bca8e067302f597c71af1f71a
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-98632",
"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": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3",
"lessThan": "f84e52829021d00bca8e067302f597c71af1f71a",
"versionType": "git"
},
{
"status": "affected",
"version": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3",
"lessThan": "718a8ffa180d469f99ad4f746f00cafd39456415",
"versionType": "git"
},
{
"status": "affected",
"version": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3",
"lessThan": "084be90948632a5a358821e687b11a14445aae76",
"versionType": "git"
},
{
"status": "affected",
"version": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3",
"lessThan": "2189a219397d8e73808a67c4aade837b635705da",
"versionType": "git"
},
{
"status": "affected",
"version": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3",
"lessThan": "03ced4687fb79286be7fdee0fc58d2c74de3e7bb",
"versionType": "git"
},
{
"status": "affected",
"version": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3",
"lessThan": "71af682ba4692c2ed9ace4c3d4ca462ae368c029",
"versionType": "git"
}
],
"programFiles": [
"net/bluetooth/mgmt.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.1"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.1",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.1.189",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.112",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.55",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.9",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"net/bluetooth/mgmt.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-10-18T16:17:16.297",
"references": [
{
"url": "https://git.kernel.org/stable/c/03ced4687fb79286be7fdee0fc58d2c74de3e7bb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/084be90948632a5a358821e687b11a14445aae76",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2189a219397d8e73808a67c4aade837b635705da",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/718a8ffa180d469f99ad4f746f00cafd39456415",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/71af682ba4692c2ed9ace4c3d4ca462ae368c029",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f84e52829021d00bca8e067302f597c71af1f71a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel\n\nIn send_cancel(), pending mesh_tx objects are removed from the\nhdev->mesh_pending list and freed via mesh_send_complete(). However, if\na mesh transmission was already queued onto hdev->cmd_sync_work_list via\nmesh_next(), the queued entry retains a raw pointer to mesh_tx.\n\nWhen hci_cmd_sync_work later processes the entry, it attempts to execute\nmesh_send_sync and its destroy callback mesh_send_start_complete using\nthe already freed mesh_tx pointer, leading to a use-after-free.\n\nFix this by invoking hci_cmd_sync_dequeue() for mesh_send_sync on the\ntarget mesh_tx before completing it. If the entry is found and dequeued,\nits destroy callback will complete and free the object; otherwise,\nmesh_send_complete() is called directly.\n\nAdditionally, ensure the transmission queue advances after cancellation\nor errors. In mesh_send_start_complete(), call mesh_next() on error\nunless err is -ECANCELED, because hci_cmd_sync_dequeue() holds\nhdev->cmd_sync_work_lock and calling mesh_next() synchronously would\ndeadlock. Instead, advance the queue in send_cancel() once the lock is\nreleased and if no transmission is in progress."
}
],
"lastModified": "2026-10-19T10:19:27.457",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}