15/11/2026

Linux Kernel: n_gsm race condition may enable local privilege escalation

CVE-2024-50073 Linux Kernel

Zero Day Initiative published an advisory for CVE-2024-50073, a race condition in the Linux Kernel n_gsm driver. An attacker needs local access to execute highly privileged code; successful exploitation may enable privilege escalation and code execution in the kernel context. Identify the kernel…

Linux Kernel: n_gsm race condition may enable local privilege escalation

At a glance

  • CVE-2024-50073 is a race condition in the Linux Kernel n_gsm driver.
  • Local exploitation may lead to privilege escalation and code execution in the kernel context.
  • An attacker must be able to execute highly privileged code on the target system.
  • Identify the kernel branch and update according to the applicable Linux fix.
In this article

Zero Day Initiative published an advisory for vulnerability CVE-2024-50073 in the Linux Kernel. This article summarizes the stated exploitation requirements, impact, and response guidance from the Zero Day Initiative advisory.

Overview and technical details

The Linux Kernel is the core of the Linux operating system, managing system resources and providing essential services to software. The vulnerability is in the n_gsm driver and is identified as CVE-2024-50073.

FieldDetails
ProductLinux Kernel, n_gsm driver
CVECVE-2024-50073
CVSS7.5 (AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H)
SourceZero Day Initiative

Affected systems

The advisory identifies the n_gsm driver in the Linux Kernel as the affected component, but the source record does not provide affected or fixed version ranges. Administrators should identify the kernel branch in use and compare it with the applicable update guidance before deployment.

Mechanism and impact

The issue results from a lack of appropriate locking when operating on an object. An attacker must be able to execute highly privileged code on the target system; successful exploitation may lead to privilege escalation and code execution in the kernel context.

System checks

  1. Identify the running kernel version so it can be compared with the appropriate update.

    uname -r

    This command checks the version; it does not fix the vulnerability.

Remediation and mitigation

  1. Prioritize updating the Linux Kernel with a fix released by Linux. Identify the kernel branch in use and compare it with the applicable update guidance before deployment; the source record does not specify a fixed version.

  2. The related fix is referenced in Linux commit 9462f4ca56e7d2430fdb6dcc8498244acbfc4489.

References