CVE-2022-49139: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt This event is just specified for SCO and eSCO link types. On the reception of a HCI_Synchronous_Connection_Complete for a BDADDR of an existing LE connection, LE link type and a status that triggers the second case of the packet processing a NULL pointer dereference happens, as conn->link is NULL.
AI Analysis
Technical Summary
CVE-2022-49139 is a vulnerability identified in the Linux kernel's Bluetooth subsystem, specifically related to the handling of the HCI_Synchronous_Connection_Complete event. This event is designed for SCO (Synchronous Connection-Oriented) and eSCO (extended SCO) link types, which are used primarily for audio data transmission over Bluetooth. The vulnerability arises when the kernel receives an HCI_Synchronous_Connection_Complete event for a Bluetooth device address (BDADDR) that corresponds to an existing Low Energy (LE) connection, which uses a different link type. Under certain status conditions that trigger a specific packet processing path, the kernel attempts to dereference a NULL pointer because the connection's link pointer (conn->link) is NULL. This NULL pointer dereference can lead to a kernel crash (denial of service) or potentially be leveraged for more severe exploitation depending on the kernel's memory layout and protections. The vulnerability affects multiple versions of the Linux kernel as indicated by the repeated affected version hashes, and it was publicly disclosed on February 26, 2025. There are no known exploits in the wild at the time of disclosure, and no CVSS score has been assigned. The issue was resolved by fixing the null pointer dereference in the Bluetooth HCI event handling code.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running vulnerable Linux kernel versions with Bluetooth enabled, particularly those using SCO or eSCO links for audio or other synchronous data transmission. The impact includes potential denial of service through kernel crashes, which can disrupt critical services, especially in environments relying on Bluetooth for communication or device connectivity. While no known exploits exist currently, the vulnerability could be targeted in the future by attackers aiming to cause system instability or to escalate privileges if combined with other vulnerabilities. Industries such as telecommunications, manufacturing, healthcare, and public sector entities that use Linux-based systems with Bluetooth capabilities are at risk. Additionally, embedded systems and IoT devices running Linux kernels with Bluetooth support may be affected, potentially impacting operational technology environments. The disruption of availability could have cascading effects on business continuity and safety-critical operations.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to the latest patched versions that address CVE-2022-49139. Since the vulnerability is triggered by specific Bluetooth events, organizations should audit and restrict Bluetooth usage where possible, especially on critical infrastructure and servers. Disabling Bluetooth on systems where it is not required can reduce the attack surface. For systems that must use Bluetooth, implementing strict network segmentation and access controls can limit exposure. Monitoring kernel logs for unusual Bluetooth HCI events or crashes can provide early detection of attempted exploitation. Additionally, organizations should ensure their incident response plans include procedures for handling kernel-level crashes and potential denial of service scenarios. For embedded and IoT devices, vendors should be contacted to confirm patch availability or mitigations. Finally, maintaining an up-to-date asset inventory to identify vulnerable Linux systems with Bluetooth enabled is essential for targeted remediation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland, Belgium
CVE-2022-49139: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt This event is just specified for SCO and eSCO link types. On the reception of a HCI_Synchronous_Connection_Complete for a BDADDR of an existing LE connection, LE link type and a status that triggers the second case of the packet processing a NULL pointer dereference happens, as conn->link is NULL.
AI-Powered Analysis
Technical Analysis
CVE-2022-49139 is a vulnerability identified in the Linux kernel's Bluetooth subsystem, specifically related to the handling of the HCI_Synchronous_Connection_Complete event. This event is designed for SCO (Synchronous Connection-Oriented) and eSCO (extended SCO) link types, which are used primarily for audio data transmission over Bluetooth. The vulnerability arises when the kernel receives an HCI_Synchronous_Connection_Complete event for a Bluetooth device address (BDADDR) that corresponds to an existing Low Energy (LE) connection, which uses a different link type. Under certain status conditions that trigger a specific packet processing path, the kernel attempts to dereference a NULL pointer because the connection's link pointer (conn->link) is NULL. This NULL pointer dereference can lead to a kernel crash (denial of service) or potentially be leveraged for more severe exploitation depending on the kernel's memory layout and protections. The vulnerability affects multiple versions of the Linux kernel as indicated by the repeated affected version hashes, and it was publicly disclosed on February 26, 2025. There are no known exploits in the wild at the time of disclosure, and no CVSS score has been assigned. The issue was resolved by fixing the null pointer dereference in the Bluetooth HCI event handling code.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running vulnerable Linux kernel versions with Bluetooth enabled, particularly those using SCO or eSCO links for audio or other synchronous data transmission. The impact includes potential denial of service through kernel crashes, which can disrupt critical services, especially in environments relying on Bluetooth for communication or device connectivity. While no known exploits exist currently, the vulnerability could be targeted in the future by attackers aiming to cause system instability or to escalate privileges if combined with other vulnerabilities. Industries such as telecommunications, manufacturing, healthcare, and public sector entities that use Linux-based systems with Bluetooth capabilities are at risk. Additionally, embedded systems and IoT devices running Linux kernels with Bluetooth support may be affected, potentially impacting operational technology environments. The disruption of availability could have cascading effects on business continuity and safety-critical operations.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to the latest patched versions that address CVE-2022-49139. Since the vulnerability is triggered by specific Bluetooth events, organizations should audit and restrict Bluetooth usage where possible, especially on critical infrastructure and servers. Disabling Bluetooth on systems where it is not required can reduce the attack surface. For systems that must use Bluetooth, implementing strict network segmentation and access controls can limit exposure. Monitoring kernel logs for unusual Bluetooth HCI events or crashes can provide early detection of attempted exploitation. Additionally, organizations should ensure their incident response plans include procedures for handling kernel-level crashes and potential denial of service scenarios. For embedded and IoT devices, vendors should be contacted to confirm patch availability or mitigations. Finally, maintaining an up-to-date asset inventory to identify vulnerable Linux systems with Bluetooth enabled is essential for targeted remediation.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-02-26T01:49:39.269Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982dc4522896dcbe5015
Added to database: 5/21/2025, 9:09:01 AM
Last enriched: 6/30/2025, 3:24:47 AM
Last updated: 1/7/2026, 9:53:59 AM
Views: 40
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-68637: CWE-297 Improper Validation of Certificate with Host Mismatch in Apache Software Foundation Apache Uniffle
UnknownCVE-2025-15158: CWE-434 Unrestricted Upload of File with Dangerous Type in eastsidecode WP Enable WebP
HighCVE-2025-15018: CWE-639 Authorization Bypass Through User-Controlled Key in djanym Optional Email
CriticalCVE-2025-15000: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in tfrommen Page Keys
MediumCVE-2025-14999: CWE-352 Cross-Site Request Forgery (CSRF) in kentothemes Latest Tabs
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.