CVE-2022-50041 Vulnerability Analysis & Exploit Details

CVE-2022-50041
Vulnerability Scoring

5.5
/10
Significant Risk

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

Status: Analyzed

Last updated: 🕡 13 Nov 2025, 18:58 UTC
Originally published on: 🕚 18 Jun 2025, 11:15 UTC

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

CVE-2022-50041: In the Linux kernel, the following vulnerability has been resolved: ice: Fix call trace with null VSI during VF reset During stress test with attaching and detaching VF from KVM and simultaneously changing VFs spoofcheck and trust there was a call trace in ice_reset_vf that VF's VSI is null. [145237.352797] WARNING: CPU: 46 PID: 840629 at drivers/net/ethernet/intel/ice/ice_vf_lib.c:508 ice_reset_vf+0x3d6/0x410 [ice] [145237.352851] Modules linked in: ice(E) vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio iavf dm_mod xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink tun bridge stp llc sunrpc intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iTCO_wdt iTC O_vendor_support irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rapl ipmi_si intel_cstate ipmi_devintf joydev intel_uncore m ei_me ipmi_msghandler i2c_i801 pcspkr mei lpc_ich ioatdma i2c_smbus acpi_pad acpi_power_meter ip_tables xfs libcrc32c i2c_algo_bit drm_sh mem_helper drm_kms_helper sd_mod t10_pi crc64_rocksoft syscopyarea crc64 sysfillrect sg sysimgblt fb_sys_fops drm i40e ixgbe ahci libahci libata crc32c_intel mdio dca wmi fuse [last unloaded: ice] [145237.352917] CPU: 46 PID: 840629 Comm: kworker/46:2 Tainted: G S W I E 5.19.0-rc6+ #24 [145237.352921] Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.0008.021120151325 02/11/2015 [145237.352923] Workqueue: ice ice_service_task [ice] [145237.352948] RIP: 0010:ice_reset_vf+0x3d6/0x410 [ice] [145237.352984] Code: 30 ec f3 cc e9 28 fd ff ff 0f b7 4b 50 48 c7 c2 48 19 9c c0 4c 89 ee 48 c7 c7 30 fe 9e c0 e8 d1 21 9d cc 31 c0 e9 a 9 fe ff ff <0f> 0b b8 ea ff ff ff e9 c1 fc ff ff 0f 0b b8 fb ff ff ff e9 91 fe [145237.352987] RSP: 0018:ffffb453e257fdb8 EFLAGS: 00010246 [145237.352990] RAX: ffff8bd0040181c0 RBX: ffff8be68db8f800 RCX: 0000000000000000 [145237.352991] RDX: 000000000000ffff RSI: 0000000000000000 RDI: ffff8be68db8f800 [145237.352993] RBP: ffff8bd0040181c0 R08: 0000000000001000 R09: ffff8bcfd520e000 [145237.352995] R10: 0000000000000000 R11: 00008417b5ab0bc0 R12: 0000000000000005 [145237.352996] R13: ffff8bcee061c0d0 R14: ffff8bd004019640 R15: 0000000000000000 [145237.352998] FS: 0000000000000000(0000) GS:ffff8be5dfb00000(0000) knlGS:0000000000000000 [145237.353000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [145237.353002] CR2: 00007fd81f651d68 CR3: 0000001a0fe10001 CR4: 00000000001726e0 [145237.353003] Call Trace: [145237.353008] <TASK> [145237.353011] ice_process_vflr_event+0x8d/0xb0 [ice] [145237.353049] ice_service_task+0x79f/0xef0 [ice] [145237.353074] process_one_work+0x1c8/0x390 [145237.353081] ? process_one_work+0x390/0x390 [145237.353084] worker_thread+0x30/0x360 [145237.353087] ? process_one_work+0x390/0x390 [145237.353090] kthread+0xe8/0x110 [145237.353094] ? kthread_complete_and_exit+0x20/0x20 [145237.353097] ret_from_fork+0x22/0x30 [145237.353103] </TASK> Remove WARN_ON() from check if VSI is null in ice_reset_vf. Add "VF is already removed\n" in dev_dbg(). This WARN_ON() is unnecessary and causes call trace, despite that call trace, driver still works. There is no need for this warn because this piece of code is responsible for disabling VF's Tx/Rx queues when VF is disabled, but when VF is already removed there is no need to do reset or disable queues.

Assessing the Risk of CVE-2022-50041

Access Complexity Graph

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

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

CVE-2022-50041 References

External References

CWE Common Weakness Enumeration

CWE-617

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.18.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.17:*:*:*:*:*:*:*
  • 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.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:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:-:*:*:*:*:*:*
  • 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:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-50041: 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-66026 – REDAXO is a PHP-based CMS. Prior to version 5.20.1, a reflected Cross-Site Scripting (XSS) vulnerability exists in the Mediapool view where the req...
  • CVE-2025-66025 – Caido is a web security auditing toolkit. Prior to version 0.53.0, the Markdown renderer used in Caido’s Findings page improperly handled user-supp...
  • CVE-2025-66022 – FACTION is a PenTesting Report Generation and Collaboration Framework. Prior to version 1.7.1, an extension execution path in Faction’s extension f...
  • CVE-2025-66269 – The RupsMon and USBMate services in UPSilon 2000 run with SYSTEM privileges and contain unquoted service paths. This allows a local attacker to per...
  • CVE-2025-66266 – The RupsMon.exe service executable in UPSilon 2000 has insecure permissions, allowing the 'Everyone' group Full Control. A local attacker can repla...