CVE-2022-49471: rtw89: cfo: check mac_id to avoid out-of-bounds
In the Linux kernel, the following vulnerability has been resolved:
rtw89: cfo: check mac_id to avoid out-of-bounds
Somehow, hardware reports incorrect mac_id and pollute memory. Check index
before we access the array.
UBSAN: array-index-out-of-bounds in rtw89/phy.c:2517:23
index 188 is out of range for type 's32 [64]'
CPU: 1 PID: 51550 Comm: irq/35-rtw89_pc Tainted: G OE
Call Trace:
<IRQ>
show_stack+0x52/0x58
dump_stack_lvl+0x4c/0x63
dump_stack+0x10/0x12
ubsan_epilogue+0x9/0x45
__ubsan_handle_out_of_bounds.cold+0x44/0x49
? __alloc_skb+0x92/0x1d0
rtw89_phy_cfo_parse+0x44/0x7f [rtw89_core]
rtw89_core_rx+0x261/0x871 [rtw89_core]
? __alloc_skb+0xee/0x1d0
rtw89_pci_napi_poll+0x3fa/0x4ea [rtw89_pci]
__napi_poll+0x33/0x1a0
net_rx_action+0x126/0x260
? __queue_work+0x217/0x4c0
__do_softirq+0xd9/0x315
? disable_irq_nosync+0x10/0x10
do_softirq.part.0+0x6d/0x90
</IRQ>
<TASK>
__local_bh_enable_ip+0x62/0x70
rtw89_pci_interrupt_threadfn+0x182/0x1a6 [rtw89_pci]
irq_thread_fn+0x28/0x60
irq_thread+0xc8/0x190
? irq_thread_fn+0x60/0x60
kthread+0x16b/0x190
? irq_thread_check_affinity+0xe0/0xe0
? set_kthread_struct+0x50/0x50
ret_from_fork+0x22/0x30
</TASK>
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the rtw89 wireless driver. Bad hardware-reported MAC IDs can cause an out-of-bounds array access, risking memory corruption in kernel context. Business impact is highest for Linux endpoints or appliances using affected rtw89 Wi-Fi support.
Executive priority
Treat as a high-priority kernel maintenance issue for Linux fleets with rtw89 Wi-Fi. It is not KEV-listed, but kernel memory corruption with high CVSS impact justifies timely patching.
Technical view
CVE-2022-49471 is a CWE-129 bounds-check flaw in rtw89 PHY CFO parsing. The source reports index 188 used against a 64-entry s32 array in interrupt receive handling. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to Linux systems using affected kernel versions with the rtw89 driver active. The bundle lists Linux 5.16 through 5.19-related affected entries, but distribution backports may change exposure.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. CVSS classifies exploitation as local with low privileges and no user interaction. No public exploit details are provided in the bundle.
Researcher notes
The public record describes the fix as validating mac_id before array access. Evidence is strongest for the bug class and code area, but sparse on real-world trigger conditions, attacker control, and distribution-specific affected ranges.
Mitigation direction
Apply vendor or distribution kernel updates containing the rtw89 bounds check fix.
Prioritize Linux endpoints using Realtek rtw89 wireless hardware or modules.
Review kernel vendor advisories before assuming upstream version numbers map directly to exposure.
If patching is delayed, evaluate disabling unused rtw89 Wi-Fi functionality.
Validation and detection
Inventory Linux hosts with the rtw89 driver or Realtek rtw89 Wi-Fi hardware.
Confirm running kernels include the referenced stable fix or a distro backport.
Check kernel logs for UBSAN out-of-bounds reports in rtw89/phy.c.
Track affected systems until patched kernels are deployed and rebooted.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-129: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-129 · source CWE mapping
Improper Validation of Array Index
Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.