Linux Kernel up to 6.2.2 _rtl8812ae_phy_set_txpower_limit comparison

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.2.2. It has been rated as critical. This issue affects the function _rtl8812ae_phy_set_txpower_limit. Performing a manipulation results in comparison. This vulnerability is cataloged as CVE-2022-50279. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.2.2. This affects the function _rtl8812ae_phy_set_txpower_limit. The manipulation with an unknown input leads to a comparison vulnerability. CWE is classifying the issue as CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit() There is a global-out-of-bounds reported by KASAN: BUG: KASAN: global-out-of-bounds in _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] Read of size 1 at addr ffffffffa0773c43 by task NetworkManager/411 CPU: 6 PID: 411 Comm: NetworkManager Tainted: G D 6.1.0-rc8+ #144 e15588508517267d37 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), Call Trace: <TASK> ... kasan_report+0xbb/0x1c0 _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] rtl8821ae_phy_bb_config.cold+0x346/0x641 [rtl8821ae] rtl8821ae_hw_init+0x1f5e/0x79b0 [rtl8821ae] ... </TASK> The root cause of the problem is that the comparison order of "prate_section" in _rtl8812ae_phy_set_txpower_limit() is wrong. The _rtl8812ae_eq_n_byte() is used to compare the first n bytes of the two strings from tail to head, which causes the problem. In the _rtl8812ae_phy_set_txpower_limit(), it was originally intended to meet this requirement by carefully designing the comparison order. For example, "pregulation" and "pbandwidth" are compared in order of length from small to large, first is 3 and last is 4. However, the comparison order of "prate_section" dose not obey such order requirement, therefore when "prate_section" is "HT", when comparing from tail to head, it will lead to access out of bounds in _rtl8812ae_eq_n_byte(). As mentioned above, the _rtl8812ae_eq_n_byte() has the same function as strcmp(), so just strcmp() is enough. Fix it by removing _rtl8812ae_eq_n_byte() and use strcmp() barely. Although it can be fixed by adjusting the comparison order of "prate_section", this may cause the value of "rate_section" to not be from 0 to 5. In addition, commit "21e4b0726dc6" not only moved driver from staging to regular tree, but also added setting txpower limit function during the driver config phase, so the problem was introduced by this commit.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50279 since 09/15/2025. The exploitability is told to be difficult. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/10/2026).

Upgrading to version 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16 or 6.2.3 eliminates this vulnerability. Applying the patch fc3442247716fc426bbcf62ed65e086e48a6d44f/28ea268d95e57cdf6394a058f0d854206d478772/1e950b9a841bc96e98ee25680d5c7aa305120be1/0c962dcd6bf64b78eaffc09e497a2beb4e48bc32/f1fe40120de6ad4ffa8299fde035a5feba10d4fb/057b52461dc005ecd85a3e4998913b1492ec0f72/117dbeda22ec5ea0918254d03b540ef8b8a64d53 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2053). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway
  • F5 F5OS

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.8
VulDB Meta Temp Score: 5.7

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.1
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Comparison
CWE: CWE-697
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.19.276/5.4.235/5.10.173/5.15.99/6.1.16/6.2.3
Patch: fc3442247716fc426bbcf62ed65e086e48a6d44f/28ea268d95e57cdf6394a058f0d854206d478772/1e950b9a841bc96e98ee25680d5c7aa305120be1/0c962dcd6bf64b78eaffc09e497a2beb4e48bc32/f1fe40120de6ad4ffa8299fde035a5feba10d4fb/057b52461dc005ecd85a3e4998913b1492ec0f72/117dbeda22ec5ea0918254d03b540ef8b8a64d53

Timelineinfo

09/15/2025 Advisory disclosed
09/15/2025 +0 days CVE reserved
09/15/2025 +0 days VulDB entry created
01/10/2026 +117 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50279 (🔒)
GCVE (CVE): GCVE-0-2022-50279
GCVE (VulDB): GCVE-100-324009
CERT Bund: WID-SEC-2025-2053 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/15/2025 17:00
Updated: 01/10/2026 15:35
Changes: 09/15/2025 17:00 (58), 09/17/2025 03:28 (7), 12/03/2025 22:57 (12), 12/28/2025 10:13 (1), 01/10/2026 15:35 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!