CVE-2024-50147 is a vulnerability identified in the Linux kernel's mlx5_core driver, which manages Mellanox ConnectX-5 and later network adapters. The flaw arises from improper initialization of a command bitmask related to the MANAGE_PAGES command. Specifically, the bitmask dedicated to this command is not initialized during the general command bitmask setup but only during the execution of the MANAGE_PAGES command itself. This leads to a scenario where the function mlx5_cmd_trigger_completions() attempts to trigger completion for the MANAGE_PAGES command even if no such command has been invoked yet. If a health error occurs before any MANAGE_PAGES command is issued, such as during the mlx5_enable_hca() initialization phase, the function will dereference a null pointer, causing a kernel crash (null pointer dereference). The vulnerability is confirmed by a Kernel Address Sanitizer (KASAN) report showing a null pointer dereference in mlx5_cmd_trigger_completions(), triggered by a workqueue handling firmware fatal errors. This bug can lead to a denial of service (DoS) condition by crashing the kernel or causing instability in systems using affected mlx5 devices. The patch involves correctly initializing the command bitmask for the MANAGE_PAGES command and rewriting the relevant code for clarity and robustness. The vulnerability affects Linux kernel versions containing the specified commit hash (9b98d395b85dd042fe83fb696b1ac02e6c93a520) and likely other versions prior to the fix. No known exploits are reported in the wild as of the publication date. The issue is technical and specific to the mlx5 driver, which is critical for high-performance networking in data centers and enterprise environments relying on Mellanox hardware.

For European organizations, the impact of CVE-2024-50147 primarily concerns systems running Linux kernels with the affected mlx5 driver managing Mellanox ConnectX-5 or newer network adapters. These adapters are widely used in high-performance computing, cloud infrastructure, and data centers, including those operated by telecom providers, financial institutions, research centers, and large enterprises across Europe. A successful exploitation leads to a kernel crash via null pointer dereference, resulting in denial of service and potential disruption of critical network services. This can affect availability of services, cause downtime, and impact business continuity. Although this vulnerability does not appear to allow privilege escalation or remote code execution directly, the induced DoS can be leveraged in targeted attacks or combined with other vulnerabilities to increase impact. European organizations relying on Linux-based infrastructure with Mellanox hardware should consider this a significant stability and availability risk, especially in environments requiring high uptime and low latency. The lack of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability details are public.

1. Apply the official Linux kernel patches that address CVE-2024-50147 as soon as they become available from trusted sources or Linux distributions. Monitor vendor advisories for updated kernel packages containing the fix. 2. For organizations unable to immediately patch, consider temporarily disabling or unloading the mlx5 driver if feasible, or isolating affected systems from critical network segments to reduce exposure. 3. Implement robust kernel crash monitoring and automated recovery mechanisms to minimize downtime caused by potential exploitation. 4. Conduct thorough testing of kernel updates in staging environments to ensure compatibility and stability before deployment in production. 5. Maintain up-to-date inventory of hardware using Mellanox ConnectX-5 or newer adapters and Linux kernel versions to prioritize patching efforts. 6. Employ network segmentation and access controls to limit exposure of vulnerable systems to untrusted networks or users. 7. Stay informed through security mailing lists and vendor communications for any emerging exploit reports or additional mitigation guidance. These steps go beyond generic advice by focusing on hardware-specific risk management, operational continuity, and proactive patch management tailored to the mlx5 driver context.