Menu

Star on GitHub · 3.2k

CVE-2022-50003

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: ice: xsk: prohibit usage of non-balanced queue id Fix the following scenario: 1.

Published Jun 18, 2025CWE-476EPSS 0.19%

Overview

CVE-2022-50003 is a medium-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

ice: xsk: prohibit usage of non-balanced queue id

Fix the following scenario:

1. ethtool -L $IFACE rx 8 tx 96

2. xdpsock -q 10 -t -z

Above refers to a case where user would like to attach XSK socket in

txonly mode at a queue id that does not have a corresponding Rx queue.

At this moment ice's XSK logic is tightly bound to act on a "queue pair",

e.g. both Tx and Rx queues at a given queue id are disabled/enabled and

both of them will get XSK pool assigned, which is broken for the presented

queue configuration. This results in the splat included at the bottom,

which is basically an OOB access to Rx ring array.

To fix this, allow using the ids only in scope of "combined" queues

reported by ethtool. However, logic should be rewritten to allow such

configurations later on, which would end up as a complete rewrite of the

control path, so let us go with this temporary fix.

[420160.558008] BUG: kernel NULL pointer derefer

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50003?

CVE-2022-50003 is a medium-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-50003?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-50003?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50003?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50003 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all