Vulnerability in ath11k: mhi: use mhi_sync_power_up()

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001074: ath11k: mhi: use mhi_sync_power_up(). Affects Kernel versions < 646d533af2911be1184eaee8c900b7eb8ecc4396. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ath11k package is a component of the Linux Kernel ecosystem. It provides support for Qualcomm Atheros 802.11ax wireless LAN devices. The package includes drivers and firmware necessary for the proper functioning of these devices. The vulnerability in question affects the MHI (Mobile Host Interface) module within ath11k. MHI is responsible for communication between the host processor and the wireless device. The vulnerability arises from the improper usage of the mhi_sync_power_up() function.

Vulnerability Detail

The vulnerability in ath11k's MHI module arises from the incorrect usage of the mhi_sync_power_up() function. This function is responsible for powering up the MHI channel and ensuring synchronization with the device. The improper usage of this function can lead to various security issues, although the exact impact and attack plausibility have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.17.3 by commit 646d533af2911be1184eaee8c900b7eb8ecc4396.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is strongly advised to update to the fixed version rather than relying on workarounds.

Conclusion

In conclusion, the vulnerability in ath11k's MHI module arises from the improper usage of the mhi_sync_power_up() function. It is crucial to update the Linux Kernel to version v5.17.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

ath11k is a package within the Linux Kernel ecosystem that provides support for Qualcomm Atheros 802.11ax wireless LAN devices. It includes drivers and firmware necessary for the proper functioning of these devices.

MHI (Mobile Host Interface) is a module within ath11k responsible for communication between the host processor and the wireless device.

The exact impact of this vulnerability is not yet proven. However, it can potentially lead to security issues related to the ath11k MHI module.

To fix this vulnerability, update the Linux Kernel to version v5.17.3 or later and ensure that the ath11k module is properly recompiled and installed.

No, there is no specific workaround available for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback