Threats Tagged 'cve-2026-53364'
View all threats tagged with 'cve-2026-53364'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-53364'
Click on any threat for detailed analysis and mitigation recommendations
Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: Fix memory leak in hci_le_big_terminate()… (CVE-2026-53364)CVE-2026-53364 0 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: Fix memory leak in hci_le_big_terminate() hci_le_big_terminate() allocates iso_list_data via kzalloc_obj but returns 0 without freeing it when neither pa_sync_term nor big_sync_term flags are set after evaluating the PA and BIG sync connection state. This early-return path was introduced when hci_le_big_terminate() was refactored to take struct hci_conn instead of raw u8 parameters, adding PA/BIG flag evaluation logic. The existing kfree() on hci_cmd_sync_queue failure does not cover this path. Join the discussion | GCVE Database | 07/13/2026, 18:16:00 UTC Added: 07/16/2026, 10:37:48 UTC |
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: Fix memory leak in hci_le_big_terminate()… (CVE-2026-53364)CVE-2026-53364 0 A memory leak vulnerability was identified and resolved in the Linux kernel's Bluetooth component, specifically in the hci_le_big_terminate() function. The function allocates memory but may return early without freeing it under certain conditions related to PA and BIG sync termination flags. This flaw was introduced during a refactor that changed parameter handling and added new flag evaluation logic. The vulnerability is categorized as CWE-401 (memory leak) and has a medium severity impact due to potential resource exhaustion. Join the discussion | GCVE Database | 07/13/2026, 18:30:52 UTC Added: 07/14/2026, 09:21:47 UTC |
Showing 1 to 2 of 2 results