LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38647: wifi: rtw89: sar: drop lockdep assertion in rtw89_set_sar_from_acpi

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: sar: drop lockdep assertion in rtw89_set_sar_from_acpi The following assertion is triggered on the rtw89 driver startup. It looks meaningless to hold wiphy lock on the early init stage so drop the assertion. WARNING: CPU: 7 PID: 629 at drivers/net/wireless/realtek/rtw89/sar.c:502 rtw89_set_sar_from_acpi+0x365/0x4d0 [rtw89_core] CPU: 7 UID: 0 PID: 629 Comm: (udev-worker) Not tainted 6.15.0+ #29 PREEMPT(lazy) Hardware name: LENOVO 21D0/LNVNB161216, BIOS J6CN50WW 09/27/2024 RIP: 0010:rtw89_set_sar_from_acpi+0x365/0x4d0 [rtw89_core] Call Trace: <TASK> rtw89_sar_init+0x68/0x2c0 [rtw89_core] rtw89_core_init+0x188e/0x1e50 [rtw89_core] rtw89_pci_probe+0x530/0xb50 [rtw89_pci] local_pci_probe+0xd9/0x190 pci_call_probe+0x183/0x540 pci_device_probe+0x171/0x2c0 really_probe+0x1e1/0x890 __driver_probe_device+0x18c/0x390 driver_probe_device+0x4a/0x120 __driver_attach+0x1a0/0x530 bus_for_each_dev+0x10b/0x190 bus_add_driver+0x2eb/0x540 driver_register+0x1a3/0x3a0 do_one_initcall+0xd5/0x450 do_init_module+0x2cc/0x8f0 init_module_from_file+0xe1/0x150 idempotent_init_module+0x226/0x760 __x64_sys_finit_module+0xcd/0x150 do_syscall_64+0x94/0x380 entry_SYSCALL_64_after_hwframe+0x76/0x7e Found by Linux Verification Center (linuxtesting.org).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel Realtek rtw89 Wi-Fi driver issue where a startup-time lockdep assertion can trigger a kernel warning. The public record describes a resolved warning, not a confirmed data breach, remote compromise, or privilege-escalation path.

Executive priority

Treat this as routine kernel hygiene unless local evidence shows widespread warnings or impacted Wi-Fi reliability. It does not currently justify emergency response based on the provided sources.

Technical view

The issue is in rtw89_set_sar_from_acpi during rtw89 driver initialization. The kernel record says a wiphy lock assertion was triggered during early init and was removed because holding that lock there appeared meaningless. No CVSS, CWE, or exploit details are provided.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions and the Realtek rtw89 Wi-Fi driver path. The source bundle lists Linux as affected and identifies kernel-version entries including 6.16, 6.16.1, and 6.17.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The available evidence describes a startup warning found by Linux Verification Center, not a weaponized attack technique or externally reachable vulnerability.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability analysis, or impact statement beyond a driver startup warning. Validation should focus on affected kernel provenance, rtw89 hardware presence, and whether vendor kernels carry the stable commits.

Mitigation direction

  • Apply distribution or vendor kernel updates that include the referenced stable fixes.
  • Confirm whether deployed kernels contain the linked rtw89 SAR assertion fix commits.
  • Prioritize laptops or endpoints using Realtek rtw89 Wi-Fi hardware.
  • Monitor Linux distribution advisories for backported fixes and affected package versions.

Validation and detection

  • Inventory Linux kernel versions across managed endpoints and appliances.
  • Check whether the rtw89 driver is present or loaded on candidate systems.
  • Review boot logs for rtw89_set_sar_from_acpi warnings during driver startup.
  • Map installed kernel packages to vendor advisories or the referenced stable commits.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2025-38647 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux88ca3107d2ce06448018e0571f7c0f1b40f57b55, 88ca3107d2ce06448018e0571f7c0f1b40f57b55unaffected
LinuxLinux6.16, 0, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.