CVE-2022-49889 Vulnerability Analysis & Exploit Details

CVE-2022-49889
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2022-49889 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-49889 Details

Status: Analyzed

Last updated: 🕐 07 May 2025, 13:19 UTC
Originally published on: 🕒 01 May 2025, 15:16 UTC

Time between publication and last update: 5 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-49889 Vulnerability Summary

CVE-2022-49889: In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters() On some machines the number of listed CPUs may be bigger than the actual CPUs that exist. The tracing subsystem allocates a per_cpu directory with access to the per CPU ring buffer via a cpuX file. But to save space, the ring buffer will only allocate buffers for online CPUs, even though the CPU array will be as big as the nr_cpu_ids. With the addition of waking waiters on the ring buffer when closing the file, the ring_buffer_wake_waiters() now needs to make sure that the buffer is allocated (with the irq_work allocated with it) before trying to wake waiters, as it will cause a NULL pointer dereference. While debugging this, I added a NULL check for the buffer itself (which is OK to do), and also NULL pointer checks against buffer->buffers (which is not fine, and will WARN) as well as making sure the CPU number passed in is within the nr_cpu_ids (which is also not fine if it isn't). Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705

Assessing the Risk of CVE-2022-49889

Access Complexity Graph

The exploitability of CVE-2022-49889 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-49889

CVE-2022-49889 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-49889, 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-49889, 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-49889 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-49889 poses no threat to data integrity.
  • Availability: High
    CVE-2022-49889 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2022-49889 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.15.75:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.75:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.76:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.76:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.77:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.77:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc8:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc8:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.7:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-49889: 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-45887 – Yifang CMS v2.0.2 is vulnerable to Server-Side Request Forgery (SSRF) in /api/file/getRemoteContent.
  • CVE-2025-45885 – PHPGURUKUL Vehicle Parking Management System v1.13 is vulnerable to SQL injection in the /vpms/users/login.php file. Attackers can inject malicious...
  • CVE-2024-12442 – EnerSys AMPA versions 24.04 through 24.16, inclusive, are vulnerable to command injection leading to privileged remote shell access.
  • CVE-2024-11861 – EnerSys AMPA 22.09 and prior versions are vulnerable to command injection leading to privileged remote shell access.
  • CVE-2025-4382 – A flaw was found in systems utilizing LUKS-encrypted disks with GRUB configured for TPM-based auto-decryption. When GRUB is set to automatically de...