CVE-2022-49876 Vulnerability Analysis & Exploit Details

CVE-2022-49876
Vulnerability Scoring

5.5
/10
Significant Risk

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

Status: Analyzed

Last updated: 🕐 07 May 2025, 13:21 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-49876 Vulnerability Summary

CVE-2022-49876: In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix general-protection-fault in ieee80211_subif_start_xmit() When device is running and the interface status is changed, the gpf issue is triggered. The problem triggering process is as follows: Thread A: Thread B ieee80211_runtime_change_iftype() process_one_work() ... ... ieee80211_do_stop() ... ... ... sdata->bss = NULL ... ... ieee80211_subif_start_xmit() ieee80211_multicast_to_unicast //!sdata->bss->multicast_to_unicast cause gpf issue When the interface status is changed, the sending queue continues to send packets. After the bss is set to NULL, the bss is accessed. As a result, this causes a general-protection-fault issue. The following is the stack information: general protection fault, probably for non-canonical address 0xdffffc000000002f: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000178-0x000000000000017f] Workqueue: mld mld_ifc_work RIP: 0010:ieee80211_subif_start_xmit+0x25b/0x1310 Call Trace: <TASK> dev_hard_start_xmit+0x1be/0x990 __dev_queue_xmit+0x2c9a/0x3b60 ip6_finish_output2+0xf92/0x1520 ip6_finish_output+0x6af/0x11e0 ip6_output+0x1ed/0x540 mld_sendpack+0xa09/0xe70 mld_ifc_work+0x71c/0xdb0 process_one_work+0x9bf/0x1710 worker_thread+0x665/0x1080 kthread+0x2e4/0x3a0 ret_from_fork+0x1f/0x30 </TASK>

Assessing the Risk of CVE-2022-49876

Access Complexity Graph

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

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

CVE-2022-49876 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.19:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.1:*:*:*:*:*:*:*
  • 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:5.19.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.16:*:*:*:*:*:*:*
  • 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:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.2:*:*:*:*:*:*:*
  • 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:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-49876: 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-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...
  • CVE-2025-4206 – The WordPress CRM, Email & Marketing Automation for WordPress | Award Winner — Groundhogg plugin for WordPress is vulnerable to arbitrary file dele...
  • CVE-2025-3897 – The EUCookieLaw plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 2.7.2 via the 'file_get_contents' f...
  • CVE-2025-3528 – A flaw was found in the Mirror Registry. The quay-app container shipped as part of the Mirror Registry for OpenShift has write access to the `/etc/...
  • CVE-2025-1087 – Kong Insomnia Desktop Application before 11.0.2 contains a template injection vulnerability that allows attackers to execute arbitrary code. The vu...