Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CVE-2022-50279— wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit()

EPSS 0.02% · P4

Affected Version Matrix 16

VendorProductVersion RangeStatus
LinuxLinux21e4b0726dc671c423e2dc9a85364716219c4502< fc3442247716fc426bbcf62ed65e086e48a6d44faffected
21e4b0726dc671c423e2dc9a85364716219c4502< 28ea268d95e57cdf6394a058f0d854206d478772affected
21e4b0726dc671c423e2dc9a85364716219c4502< 1e950b9a841bc96e98ee25680d5c7aa305120be1affected
21e4b0726dc671c423e2dc9a85364716219c4502< 0c962dcd6bf64b78eaffc09e497a2beb4e48bc32affected
21e4b0726dc671c423e2dc9a85364716219c4502< f1fe40120de6ad4ffa8299fde035a5feba10d4fbaffected
21e4b0726dc671c423e2dc9a85364716219c4502< 057b52461dc005ecd85a3e4998913b1492ec0f72affected
21e4b0726dc671c423e2dc9a85364716219c4502< 117dbeda22ec5ea0918254d03b540ef8b8a64d53affected
3.18affected
… +8 more rows
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2022-50279

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit()
Source: NVD (National Vulnerability Database)
Vulnerability Description
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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于_rtl8812ae_phy_set_txpower_limit函数中prate_section比较顺序错误，可能导致全局溢出。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 21e4b0726dc671c423e2dc9a85364716219c4502 ~ fc3442247716fc426bbcf62ed65e086e48a6d44f -
LinuxLinux 3.18 -

II. Public POCs for CVE-2022-50279

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-50279

请登录查看更多情报信息。

Same Patch Batch · Linux · 2025-09-15 · 210 CVEs total

CVE-2022-50293btrfs: do not BUG_ON() on ENOMEM when dropping extent items for a range
CVE-2023-53232mt76: mt7921: fix kernel panic by accessing unallocated eeprom.data
CVE-2023-53233net/smc: fix deadlock triggered by cancel_delayed_work_syn()
CVE-2023-53234watchdog: Fix kmemleak in watchdog_cdev_register
CVE-2023-53235drm/tests: helpers: Avoid a driver uaf
CVE-2023-53236iommufd: Do not corrupt the pfn list when doing batch carry
CVE-2023-53237drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v11_0_hw_fini
CVE-2023-53238phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe()
CVE-2023-53239drm/msm/mdp5: Add check for kzalloc
CVE-2023-53240xsk: check IFF_UP earlier in Tx path
CVE-2023-53241nfsd: call op_release, even when op_func returns an error
CVE-2023-53242thermal/drivers/hisi: Drop second sensor hi3660
CVE-2022-50291kcm: annotate data-races around kcm->rx_psock
CVE-2022-50292drm/msm/dp: fix bridge lifetime
CVE-2022-50303drm/amdkfd: Fix double release compute pasid
CVE-2022-50300btrfs: fix extent map use-after-free when handling missing device in read_one_chunk
CVE-2022-50301iommu/omap: Fix buffer overflow in debugfs
CVE-2022-50302lockd: set other missing fields when unlocking files
CVE-2022-50299md: Replace snprintf with scnprintf
CVE-2022-50304mtd: core: fix possible resource leak in init_mtd()

Showing top 20 of 210 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2022-50279

No comments yet

Leave a comment