Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2022-48851

A use-after-free flaw was found in the Linux kernel's gdm724x driver (staging: gdm724x) in the gdm_lte_rx() function, allowing remote attackers to execute arbitrary code or cause a denial of service. The vulnerability has been assigned a critical CVSS score of 9.8. A patch has been released that resolves the issue.

publishedJul 16, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
41th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 4, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users, specifically those using the gdm724x staging driver.

02

Real-world impact

An attacker could exploit this flaw remotely to gain elevated privileges, crash the system, or execute arbitrary code with kernel privileges.

03

Why this severity

The CVSS v3.1 base score of 9.8 reflects a network‑reachable attack with low complexity, no privileges or user interaction required, and high impacts to confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 011. Determine the Linux kernel version currently running on your system.
  2. 022. Obtain the latest kernel update from your distribution's security repository that includes the fix for CVE-2022-48851 (the patch addressing the use‑after‑free in gdm_lte_rx()).
  3. 033. Install the updated kernel following your distribution's standard upgrade procedure.
  4. 044. Reboot the system to load the patched kernel.

NVD description stating the vulnerability has been resolved in the Linux kernel (staging: gdm724x: fix use after free in gdm_lte_rx()).

05

Timeline

  1. Jul 16, 2024 · Jul 16, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 5, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

NVD advisory ↗Search advisories ↗
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →