Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90253Bluetooth: MGMT: free the mesh send cancel command when it is cancelled

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < b609341ee56967d9a45845ff26f79336d2114b55
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 416fabca9b7237b76aa9cafcf8c497b8ac00d88c
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 88e30d036d777b00aed42bd35000de23ff40910c
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 05438d338a875a9daa08ca3f6a35b4480cf13de4
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < fa46d428c014e7b72a18634679815670418e67dc
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 3c742feda8fcabf741a17bcf668b63c8f606f9c5
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90253 badge
[![CVE-2026-90253](https://cveledger.app/badge/CVE-2026-90253.svg)](https://cveledger.app/cve/CVE-2026-90253)

Record last updated .