PatchSiren cyber security CVE debrief
CVE-2026-90254 Linux CVE debrief
A memory leak vulnerability exists in the Linux kernel's Bluetooth hci_sync component. When an advertising instance is allocated but not properly freed on failure or cancellation paths, it can lead to memory leaks. This issue is due to the lack of a destroy callback in certain scenarios and the failure to release resources in the hci_cmd_sync_cancel_entry function.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-10-19
Who should care
Linux kernel developers and maintainers, Bluetooth protocol implementers, and Linux distribution maintainers should assess exposure and prioritize patching or mitigation strategies.
Why it matters
The CVE-2026-90254 memory leak vulnerability in the Linux kernel's Bluetooth hci_sync component requires attention from Linux kernel developers, maintainers, and distribution maintainers to assess exposure and prioritize patching or mitigation strategies.
- Memory leaks can lead to resource exhaustion and potential denial-of-service conditions.
- The vulnerability requires verification of affected versions and exposure in specific deployment contexts.
- Defenders should prioritize patching or mitigation strategies to prevent potential memory leaks.
- The vulnerability's impact is limited to the Linux kernel's Bluetooth hci_sync component.
Technical summary
The memory leak vulnerability in the Linux kernel's Bluetooth hci_sync component occurs due to the lack of a destroy callback in certain scenarios and the failure to release resources in the hci_cmd_sync_cancel_entry function. This can lead to memory leaks when an advertising instance is allocated but not properly freed on failure or cancellation paths. The vulnerability requires attention from Linux kernel developers, maintainers, and distribution maintainers to assess exposure and prioritize patching or mitigation strategies. The issue arises from the improper handling of advertising instances on failure or cancellation paths, which can cause resource exhaustion and potential denial-of-service conditions.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the patches provided by the Linux kernel repository to address the memory leak vulnerability.
- Ensure that the Linux kernel is updated to a version that includes the fix.
- Monitor the Linux kernel repository for future updates and security advisories.
- Perform a thorough review of the affected systems to identify potential exposure.
- Verify that the patches are applied correctly and test the systems to ensure the vulnerability is mitigated.
- Consider implementing compensating controls, such as monitoring and detection tools, to identify potential exploitation attempts.
- Keep track of the Linux kernel repository for future updates and security advisories related to this vulnerability.
Evidence notes
The CVE record and source item provide details on the memory leak vulnerability in the Linux kernel's Bluetooth hci_sync component. The issue arises from the improper handling of advertising instances on failure or cancellation paths. The source references include commits from the Linux kernel repository that address the vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-90254 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-90254
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-90254 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90254
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Bluetooth: hci_sync: free the advertising instance on the failure and cancel paths
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/90xxx/CVE-2026-90254.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c2019224a766245b7db39d87fdfe84c3fdc879d9
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/193182c6467f508a8a61d5db506d796ffed6eee6
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2e3d827cd56865c14f6ca118bbccd7801091fb21
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/9c3b6c1413bd0b4993642d987616331f84d9b7f5
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/bb5ca1cc7744c41c59002bd6523714a685ae6595
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/120d8dc042e3d45073bb6e50ee7b058a0b182627
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.