GHSA-QMMQ-QM3C-V3PP
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: MGMT: free the mesh send cancel command when it is cancelled
mesh_send_cancel() queues the pending command with a NULL destroy callback, so it is only freed if send_cancel() runs. A cancelled entry is leaked, as _hci_cmd_sync_cancel_entry() does not release entry->data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered. Nothing else reclaims it either: mgmt_pending_new() does not put the command on hdev->mgmt_pending.
The leak also pins the socket reference taken by mgmt_pending_new(), so the mgmt socket is never released.
Free the command from a destroy callback.
{
"affected": [],
"aliases": [
"CVE-2026-90253"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:21Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: free the mesh send cancel command when it is cancelled\n\nmesh_send_cancel() queues the pending command with a NULL destroy\ncallback, so it is only freed if send_cancel() runs. A cancelled entry is\nleaked, as _hci_cmd_sync_cancel_entry() does not release entry-\u003edata when\nthere is no destroy callback, and hci_cmd_sync_clear() cancels every\npending entry when the controller is unregistered. Nothing else reclaims\nit either: mgmt_pending_new() does not put the command on\nhdev-\u003emgmt_pending.\n\nThe leak also pins the socket reference taken by mgmt_pending_new(), so\nthe mgmt socket is never released.\n\nFree the command from a destroy callback.",
"id": "GHSA-qmmq-qm3c-v3pp",
"modified": "2026-09-17T18:31:57Z",
"published": "2026-09-17T18:31:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90253"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/05438d338a875a9daa08ca3f6a35b4480cf13de4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3c742feda8fcabf741a17bcf668b63c8f606f9c5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/416fabca9b7237b76aa9cafcf8c497b8ac00d88c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/88e30d036d777b00aed42bd35000de23ff40910c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b609341ee56967d9a45845ff26f79336d2114b55"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fa46d428c014e7b72a18634679815670418e67dc"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.
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.