CVE-2022-49419 Vulnerability Analysis & Exploit Details

CVE-2022-49419
Vulnerability Scoring

7.8
/10
Very High Risk

Highly exploitable, CVE-2022-49419 poses a critical security risk that could lead to severe breaches.

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-49419 Details

Status: Analyzed

Last updated: 🕢 24 Mar 2025, 19:57 UTC
Originally published on: 🕖 26 Feb 2025, 07:01 UTC

Time between publication and last update: 26 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-49419 Vulnerability Summary

CVE-2022-49419: In the Linux kernel, the following vulnerability has been resolved: video: fbdev: vesafb: Fix a use-after-free due early fb_info cleanup Commit b3c9a924aab6 ("fbdev: vesafb: Cleanup fb_info in .fb_destroy rather than .remove") fixed a use-after-free error due the vesafb driver freeing the fb_info in the .remove handler instead of doing it in .fb_destroy. This can happen if the .fb_destroy callback is executed after the .remove callback, since the former tries to access a pointer freed by the latter. But that change didn't take into account that another possible scenario is that .fb_destroy is called before the .remove callback. For example, if no process has the fbdev chardev opened by the time the driver is removed. If that's the case, fb_info will be freed when unregister_framebuffer() is called, making the fb_info pointer accessed in vesafb_remove() after that to no longer be valid. To prevent that, move the expression containing the info->par to happen before the unregister_framebuffer() function call.

Assessing the Risk of CVE-2022-49419

Access Complexity Graph

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

CVE-2022-49419 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-49419, 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-49419, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2022-49419 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-49419 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2022-49419 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.045% (probability of exploit)

EPSS Percentile: 18.4% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 81.6% of others.

CVE-2022-49419 References

External References

CWE Common Weakness Enumeration

CWE-416

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.15.41:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.41:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.42:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.42:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.43:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.43:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.44:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.44:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.45:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.45:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.17.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.17.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.17.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.17.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.17.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.17.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.17.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.17.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.17.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.17.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-49419: 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-2723 – A vulnerability was found in GNOME libgsf up to 1.14.53. It has been rated as critical. This issue affects the function gsf_property_settings_colle...
  • CVE-2025-2722 – A vulnerability was found in GNOME libgsf up to 1.14.53. It has been declared as critical. This vulnerability affects the function gsf_prop_setting...
  • CVE-2025-2721 – A vulnerability was found in GNOME libgsf up to 1.14.53. It has been classified as critical. This affects the function gsf_base64_encode_simple. Th...
  • CVE-2025-2720 – A vulnerability was found in GNOME libgsf up to 1.14.53 and classified as problematic. Affected by this issue is the function gsf_base64_encode_sim...
  • CVE-2025-2717 – A vulnerability, which was classified as critical, has been found in D-Link DIR-823X 240126/240802. This issue affects the function sub_41710C of t...