CVE-2022-49543

Local service interruption via unbalanced device-wake accounting

Published Feb 26, 2025 · Updated Aug 15, 2026

Improper device-wake accounting in Linux 5.6 before 5.17.14 and 5.18 before 5.18.3 allows local users to interrupt ath11k recovery. During recovery, ath11k_pci_read32() and ath11k_pci_write32() call mhi_device_put() even when mhi_device_get_sync() skipped the matching wake assertion because MHI was not in a normal power state. Exploitation requires local access and compatible Qualcomm PCI wireless hardware; the mismatch raises a kernel warning and interrupts recovery without reported data disclosure or modification.

CVSS severity5.5
Medium
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper device-wake accounting in Linux 5.6 before 5.17.14 and 5.18 before 5.18.3 allows local users to interrupt ath11k recovery. During recovery, ath11k_pci_read32() and ath11k_pci_write32() call mhi_device_put() even when mhi_device_get_sync() skipped the matching wake assertion because MHI was not in a normal power state. Exploitation requires local access and compatible Qualcomm PCI wireless hardware; the mismatch raises a kernel warning and interrupts recovery without reported data disclosure or modification.

The record

CVE
CVE-2022-49543
Published
Feb 26, 2025
Updated
Aug 15, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 26, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 15, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.10
  2. Affected versionversion=a05bd85133357b0c1b0a52dda4ee4d7e31069f4f <0d7a8a6204ea9271f1d0a8c66a9fd2f54d2e3cbc
  3. Affected versionversion=a05bd85133357b0c1b0a52dda4ee4d7e31069f4f <5f18206cddae033c488e4879f198699092ca0524
  4. Affected versionversion=a05bd85133357b0c1b0a52dda4ee4d7e31069f4f <a2d9b7357469949ad02f511fc69f8fa3a1afbf89

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.10; version=a05bd85133357b0c1b0a52dda4ee4d7e31069f4f <0d7a8a6204ea9271f1d0a8c66a9fd2f54d2e3cbc; version=a05bd85133357b0c1b0a52dda4ee4d7e31069f4f <5f18206cddae033c488e4879f198699092ca0524; version=a05bd85133357b0c1b0a52dda4ee4d7e31069f4f <a2d9b7357469949ad02f511fc69f8fa3a1afbf89

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo