CVE-2026-90253
Description
In 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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://git.kernel.org/stable/c/05438d338a875a9daa08ca3f6a35b4480cf13de4
- https://git.kernel.org/stable/c/3c742feda8fcabf741a17bcf668b63c8f606f9c5
- https://git.kernel.org/stable/c/416fabca9b7237b76aa9cafcf8c497b8ac00d88c
- https://git.kernel.org/stable/c/88e30d036d777b00aed42bd35000de23ff40910c
- https://git.kernel.org/stable/c/b609341ee56967d9a45845ff26f79336d2114b55
- https://git.kernel.org/stable/c/fa46d428c014e7b72a18634679815670418e67dc
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.