{"id":"CVE-2022-50279","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:\n\nwifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit()\n\nThere is a global-out-of-bounds reported by KASAN:\n\n  BUG: KASAN: global-out-of-bound…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < fc3442247716fc426bbcf62ed65e086e48a6d44f","Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 28ea268d95e57cdf6394a058f0d854206d478772","Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 1e950b9a841bc96e98ee25680d5c7aa305120be1","Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 0c962dcd6bf64b78eaffc09e497a2beb4e48bc32","Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < f1fe40120de6ad4ffa8299fde035a5feba10d4fb","Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 057b52461dc005ecd85a3e4998913b1492ec0f72","Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 117dbeda22ec5ea0918254d03b540ef8b8a64d53","Linux 3.18"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-11-05T20:08:47.709104Z"},"published":"2025-09-15","updated":"2026-11-05","sourceUpdated":"2026-11-05T20:10:32.737Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2022-50279","references":[{"url":"https://git.kernel.org/stable/c/fc3442247716fc426bbcf62ed65e086e48a6d44f"},{"url":"https://git.kernel.org/stable/c/28ea268d95e57cdf6394a058f0d854206d478772"},{"url":"https://git.kernel.org/stable/c/1e950b9a841bc96e98ee25680d5c7aa305120be1"},{"url":"https://git.kernel.org/stable/c/0c962dcd6bf64b78eaffc09e497a2beb4e48bc32"},{"url":"https://git.kernel.org/stable/c/f1fe40120de6ad4ffa8299fde035a5feba10d4fb"},{"url":"https://git.kernel.org/stable/c/057b52461dc005ecd85a3e4998913b1492ec0f72"},{"url":"https://git.kernel.org/stable/c/117dbeda22ec5ea0918254d03b540ef8b8a64d53"}],"tags":["cve.org"],"epss":0.00164,"epssPercentile":0.05613,"ingestedAt":"2026-11-05T22:38:31.716Z","slug":"CVE-2022-50279","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit()\n\nThere is a global-out-of-bounds reported by KASAN:\n\n  BUG: KASAN: global-out-of-bounds in\n  _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae]\n  Read of size 1 at addr ffffffffa0773c43 by task NetworkManager/411\n\n  CPU: 6 PID: 411 Comm: NetworkManager Tainted: G      D\n  6.1.0-rc8+ #144 e15588508517267d37\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),\n  Call Trace:\n   <TASK>\n   ...\n   kasan_report+0xbb/0x1c0\n   _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae]\n   rtl8821ae_phy_bb_config.cold+0x346/0x641 [rtl8821ae]\n   rtl8821ae_hw_init+0x1f5e/0x79b0 [rtl8821ae]\n   ...\n   </TASK>\n\nThe root cause of the problem is that the comparison order of\n\"prate_section\" in _rtl8812ae_phy_set_txpower_limit() is wrong. The\n_rtl8812ae_eq_n_byte() is used to compare the first n bytes of the two\nstrings from tail to head, which causes the problem. In the\n_rtl8812ae_phy_set_txpower_limit(), it was originally intended to meet\nthis requirement by carefully designing the comparison order.\nFor example, \"pregulation\" and \"pbandwidth\" are compared in order of\nlength from small to large, first is 3 and last is 4. However, the\ncomparison order of \"prate_section\" dose not obey such order requirement,\ntherefore when \"prate_section\" is \"HT\", when comparing from tail to head,\nit will lead to access out of bounds in _rtl8812ae_eq_n_byte(). As\nmentioned above, the _rtl8812ae_eq_n_byte() has the same function as\nstrcmp(), so just strcmp() is enough.\n\nFix it by removing _rtl8812ae_eq_n_byte() and use strcmp() barely.\nAlthough it can be fixed by adjusting the comparison order of\n\"prate_section\", this may cause the value of \"rate_section\" to not be\nfrom 0 to 5. In addition, commit \"21e4b0726dc6\" not only moved driver\nfrom staging to regular tree, but also added setting txpower limit\nfunction during the driver config phase, so the problem was introduced\nby this commit.\n\n## Affected\n\n- `Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < fc3442247716fc426bbcf62ed65e086e48a6d44f`\n- `Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 28ea268d95e57cdf6394a058f0d854206d478772`\n- `Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 1e950b9a841bc96e98ee25680d5c7aa305120be1`\n- `Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 0c962dcd6bf64b78eaffc09e497a2beb4e48bc32`\n- `Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < f1fe40120de6ad4ffa8299fde035a5feba10d4fb`\n- `Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 057b52461dc005ecd85a3e4998913b1492ec0f72`\n- `Linux >= 21e4b0726dc671c423e2dc9a85364716219c4502 < 117dbeda22ec5ea0918254d03b540ef8b8a64d53`\n- `Linux 3.18`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}