Vulnerability in drm/msm Package: Don't Free the IRQ if Not Requested

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1002734: drm/msm: don't free the IRQ if it was not requested. Affects Kernel versions >= f026e431cf861197dc03217d1920b38b80b31dd9, < 59023c4fb1ab3de0fa001681650f662c253c7fd7. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The drm/msm package is a component of the Linux Kernel that provides support for the display subsystem on Qualcomm MSM (Mobile Station Modem) chipsets. It enables graphics rendering, display control, and other related functionalities on devices utilizing these chipsets. The package is critical for proper display operation and is widely used in various Linux-based systems.

Vulnerability Detail

The vulnerability in the drm/msm package arises from a flaw that allows the freeing of an Interrupt Request (IRQ) without proper verification of whether it was requested in the first place. This issue can potentially lead to a use-after-free vulnerability, where an attacker could exploit the freed IRQ to execute arbitrary code or cause a denial-of-service condition. The vulnerability was introduced in version v5.15 of the Linux Kernel and has been fixed in version v5.18.3.

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 a workaround, users can apply the patch manually to their existing Linux Kernel version. The patch can be obtained from the commit 59023c4fb1ab3de0fa001681650f662c253c7fd7 in the Linux Kernel repository. Users should carefully review the patch and apply it following the appropriate procedures for patching the Linux Kernel.

Conclusion

In conclusion, the vulnerability in the drm/msm package of the Linux Kernel could potentially lead to the execution of arbitrary code or denial-of-service attacks. It is crucial for users to update their Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. Alternatively, users can manually apply the provided patch as a temporary workaround. For additional support and guidance, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability could potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition on systems utilizing the affected version of the drm/msm package.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this specific issue.

There are no known instances of this vulnerability being exploited in the wild. However, it is crucial to apply the necessary updates or patches to mitigate the risk.

While updating the Linux Kernel is the recommended approach, users can apply the provided patch manually as a temporary mitigation measure. However, it is still advisable to update to the latest stable version of the Linux Kernel as soon as possible.

For further support and assistance in addressing this vulnerability, you can reach out to info@devnack.com. Our team of experts will be happy to assist you in resolving the issue.

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