Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2022-49471 — kernel

🟠 CVSS 8.8 — High ✅ No Known Exploit NVD
8.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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>

How this vulnerability can be exploited

This issue can be reached from an adjacent network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Adjacent network — the attacker has to sit on the same local or logical network.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2022-49471 is recorded against 2 packages.

  • kernel (from 5.18.0 up to 5.18.3)
  • linux-kernel (from 5.18 up to 5.18.3)

Timeline and source

Published on 26 February 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2022-49471 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity High
CVSS Score 8.8
CVSS Vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-02-26
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 5.18.0 5.18.3
linux-kernel 5.18 5.18.3

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2022-49471 is rated CVSS 8.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2022
✓