CVE-2022-49940 Vulnerability Analysis & Exploit Details

CVE-2022-49940
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2022-49940 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-49940 Details

Status: Analyzed

Last updated: 🕢 14 Nov 2025, 19:39 UTC
Originally published on: 🕚 18 Jun 2025, 11:15 UTC

Time between publication and last update: 149 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2022-49940 Vulnerability Summary

CVE-2022-49940: In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: add sanity check for gsm->receive in gsm_receive_buf() A null pointer dereference can happen when attempting to access the "gsm->receive()" function in gsmld_receive_buf(). Currently, the code assumes that gsm->recieve is only called after MUX activation. Since the gsmld_receive_buf() function can be accessed without the need to initialize the MUX, the gsm->receive() function will not be set and a NULL pointer dereference will occur. Fix this by avoiding the call to "gsm->receive()" in case the function is not initialized by adding a sanity check. Call Trace: <TASK> gsmld_receive_buf+0x1c2/0x2f0 drivers/tty/n_gsm.c:2861 tiocsti drivers/tty/tty_io.c:2293 [inline] tty_ioctl+0xa75/0x15d0 drivers/tty/tty_io.c:2692 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Assessing the Risk of CVE-2022-49940

Access Complexity Graph

The exploitability of CVE-2022-49940 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-49940

CVE-2022-49940 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-49940, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-49940, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2022-49940 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-49940 poses no threat to data integrity.
  • Availability: High
    CVE-2022-49940 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2022-49940 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.15.61:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.61:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.62:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.62:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.63:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.63:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.64:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.64:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.65:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.65:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc9:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc9:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc3:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-49940: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-13735 – Out-of-bounds Read vulnerability in ASR1903、ASR3901 in ASR Lapwing_Linux on Linux (nr_fw modules). This vulnerability is associated with program fi...
  • CVE-2025-9558 – There is a potential OOB Write vulnerability in the gen_prov_start function in pb_adv.c. The full length of the received data is copied into the li...
  • CVE-2025-9557 – ‭An out-of-bound write can lead to an arbitrary code execution. Even on devices with some form of memory protection, this can still lead to‬ ‭a cra...
  • CVE-2025-59820 – In KDE Krita before 5.2.13, loading a manipulated TGA file could result in a heap-based buffer overflow in plugins/impex/tga/kis_tga_import.cpp (ak...
  • CVE-2025-55174 – In KDE Skanpage before 25.08.0, an attempt at file overwrite can result in the contents of the new file at the beginning followed by the partial co...