Memory leakage via missing cancellation cleanup
Published Sep 17, 2026 · Updated Sep 17, 2026
Memory leakage in Linux 6.1 Bluetooth MGMT allows local users to retain kernel allocations via canceled mesh-send commands. In net/bluetooth/mgmt.c, mesh_send_cancel() queues a command without a destroy callback, so controller unregistration cancels it without freeing the allocation or releasing its socket reference. Access requires CAP_NET_ADMIN, enabled experimental mesh support, and enabled Bluetooth LE; the documented consequence is retained memory and an unreleased management socket, not a demonstrated crash.
Summary
What happened
Memory leakage in Linux 6.1 Bluetooth MGMT allows local users to retain kernel allocations via canceled mesh-send commands. In net/bluetooth/mgmt.c, mesh_send_cancel() queues a command without a destroy callback, so controller unregistration cancels it without freeing the allocation or releasing its socket reference. Access requires CAP_NET_ADMIN, enabled experimental mesh support, and enabled Bluetooth LE; the documented consequence is retained memory and an unreleased management socket, not a demonstrated crash.
The record
- CVE
- CVE-2026-90253
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.1
- Affected versionversion=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <05438d338a875a9daa08ca3f6a35b4480cf13de4
- Affected versionversion=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <3c742feda8fcabf741a17bcf668b63c8f606f9c5
- Affected versionversion=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <416fabca9b7237b76aa9cafcf8c497b8ac00d88c
- Affected versionversion=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <88e30d036d777b00aed42bd35000de23ff40910c
- Affected versionversion=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <b609341ee56967d9a45845ff26f79336d2114b55
- Affected versionversion=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <fa46d428c014e7b72a18634679815670418e67dc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started