Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-49326

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: rtl818x: Prevent using not initialized queues Using not existing queues can panic the kernel with rtl8180/rtl8185 cards.

Published Feb 26, 2025CWE-908EPSS 0.30%

Overview

CVE-2022-49326 is a medium-severity vulnerability. It was published on February 26, 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:

rtl818x: Prevent using not initialized queues

Using not existing queues can panic the kernel with rtl8180/rtl8185 cards.

Ignore the skb priority for those cards, they only have one tx queue. Pierre

Asselin ([email protected]) reported the kernel crash in the Gentoo forum:

https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html

He also confirmed that this patch fixes the issue. In summary this happened:

After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a

"divide error: 0000" when connecting to an AP. Control port tx now tries to

use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in

2.10.

Since only the rtl8187se part of the driver supports QoS, the priority

of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185

cards.

rtl8180 is then unconditionally reading out the priority and finally crashes on

drivers/net/wireless/realtek/rtl

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.

References

Refgit.kernel.org/stable/c/6ad81ad0cf5744738ce94c8e64051ddd80a1734cRefgit.kernel.org/stable/c/746285cf81dc19502ab238249d75f5990bd2d231Refgit.kernel.org/stable/c/769ec2a824deae2f1268dfda14999a4d14d0d0c5Refgit.kernel.org/stable/c/98e55b0b876bde3353f4e074883d66ecb55c65a3Refgit.kernel.org/stable/c/9ad1981fc4de3afb7db3e8eb5a6a52d4c7d0d577Refgit.kernel.org/stable/c/9d5e96cc1f1720019ce27b127a31695148d38bb0Refgit.kernel.org/stable/c/b5dca2cd3f0239512da808598b4e70557eb4c2a1Refgit.kernel.org/stable/c/b8ce58ab80faaea015c206382041ff3bcf5495ffRefgit.kernel.org/stable/c/d7e30dfc166d33470bba31a42f9bbc346e5409d5

How CyberStrike helps

Frequently asked questions

What is CVE-2022-49326?

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

How severe is CVE-2022-49326?

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-49326?

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-49326?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-49326 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
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999