CVE-2024-50077 is a vulnerability identified in the Linux kernel's Bluetooth ISO (Isochronous Channels) subsystem. The root cause lies in the initialization logic of the ISO Bluetooth protocol when debugfs support is disabled (i.e., when CONFIG_DEBUG_FS or CONFIG_DEBUG_FS_ALLOW_ALL kernel configuration options are unset). Specifically, the iso_init() function returns early without setting the iso_inited flag to true if the bt_debugfs interface is not created successfully. This leads to a scenario where iso_init() can be called multiple times, resulting in duplicate registrations of protocol handlers and socket types via proto_register() and bt_sock_register(). When the kernel is compiled with CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, these duplicate registrations cause a kernel BUG due to a double addition in the linked list management (list_add double add). This triggers a kernel panic (Oops) with an invalid opcode exception, effectively crashing the system or the Bluetooth daemon (bluetoothd). The patch removes the early return in iso_init(), ensuring iso_inited is set properly and preventing duplicate initialization calls. The vulnerability affects Linux kernel versions prior to the fix, including 6.10.11-1-ao-desktop as referenced. No known exploits are currently reported in the wild. The issue is a stability and availability concern rather than a direct confidentiality or integrity breach, as it leads to denial of service via kernel crash when Bluetooth ISO channels are initialized improperly under specific kernel configurations.

For European organizations, this vulnerability primarily poses a risk to system availability and operational stability, especially for those relying on Linux-based systems with Bluetooth ISO support enabled. Critical infrastructure, industrial control systems, and enterprise environments that utilize Bluetooth for device communication or IoT integration could experience unexpected system crashes or service interruptions. This could disrupt business operations, particularly in sectors such as manufacturing, healthcare, transportation, and telecommunications where Linux servers or embedded devices are prevalent. Although the vulnerability does not directly expose data confidentiality or integrity, the induced kernel panic could be exploited by attackers to cause denial of service, potentially as part of a larger attack chain. Organizations with hardened Linux kernels configured with CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION are more susceptible to this crash, which may complicate incident response and recovery. The lack of known exploits reduces immediate risk, but the vulnerability's presence in widely used Linux kernels necessitates timely patching to maintain system reliability.

1. Apply the official Linux kernel patch that removes the early return in iso_init() and ensures proper initialization of the Bluetooth ISO subsystem. Monitor Linux kernel updates and backport patches if using long-term support or custom kernels. 2. Review kernel configuration options: if feasible, enable CONFIG_DEBUG_FS or CONFIG_DEBUG_FS_ALLOW_ALL to avoid the early return condition, though this may not be practical in all environments. 3. For systems where patching is delayed, consider disabling Bluetooth ISO support or the Bluetooth subsystem entirely if it is not required, to eliminate the attack surface. 4. Implement robust monitoring for kernel Oops and system crashes related to Bluetooth services to detect exploitation attempts or instability early. 5. Harden system recovery procedures to quickly restore affected systems after a crash, including automated reboots and service restarts. 6. Coordinate with Linux distribution maintainers to ensure timely distribution of patched kernel versions and advisories. 7. For embedded or IoT devices using affected kernels, work with vendors to obtain firmware updates addressing this vulnerability.