wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit()
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: ... 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] ... 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 strc
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.276, 5.10.173, 5.15.99, 5.4.235, 6.1.16, 6.2.3
- CVEs
- CVE-2022-50279
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 05:32 UTC · Revision 1
Source evidence
wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit()
core-osv · Original sourcePublished 15 Sept 2025, 14:21 UTC
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: ... 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] ... 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 strc
osv:CVE-2022-50279
Kernel
Fixed versions: 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3
Complete source record
{
"id": "acebdab952d8cfcf46d2e245aac90e00b8a66767d9d571ed05663266926d9658",
"url": "https://osv.dev/vulnerability/CVE-2022-50279",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit()",
"summary": "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: ... 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] ... 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 strc",
"evidence": "osv:CVE-2022-50279",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.276",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.235",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.173",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.99",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.16",
"evidence": "/affected/1/ranges"
},
{
"value": "6.2.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-50279",
"aliases": [
"CVE-2022-50279"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "21e4b0726dc671c423e2dc9a85364716219c4502"
},
{
"fixed": "fc3442247716fc426bbcf62ed65e086e48a6d44f"
},
{
"fixed": "28ea268d95e57cdf6394a058f0d854206d478772"
},
{
"fixed": "1e950b9a841bc96e98ee25680d5c7aa305120be1"
},
{
"fixed": "0c962dcd6bf64b78eaffc09e497a2beb4e48bc32"
},
{
"fixed": "f1fe40120de6ad4ffa8299fde035a5feba10d4fb"
},
{
"fixed": "057b52461dc005ecd85a3e4998913b1492ec0f72"
},
{
"fixed": "117dbeda22ec5ea0918254d03b540ef8b8a64d53"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50279.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.18.0"
},
{
"fixed": "4.19.276"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.235"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.173"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.99"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.16"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.2.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50279.json"
}
}
],
"modified": "2026-10-28T02:30:43.006530836Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/057b52461dc005ecd85a3e4998913b1492ec0f72",
"https://git.kernel.org/stable/c/0c962dcd6bf64b78eaffc09e497a2beb4e48bc32",
"https://git.kernel.org/stable/c/117dbeda22ec5ea0918254d03b540ef8b8a64d53",
"https://git.kernel.org/stable/c/1e950b9a841bc96e98ee25680d5c7aa305120be1",
"https://git.kernel.org/stable/c/28ea268d95e57cdf6394a058f0d854206d478772",
"https://git.kernel.org/stable/c/f1fe40120de6ad4ffa8299fde035a5feba10d4fb",
"https://git.kernel.org/stable/c/fc3442247716fc426bbcf62ed65e086e48a6d44f",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50279.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-50279",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50279.json"
}
},
"related_cves": [
{
"value": "CVE-2022-50279",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 510723,
"published_at": "2025-09-15T14:21:16.051+00:00"
}