Vulnerability in Kernel package: Input: gpio-keys - cancel delayed work only in case of GPIO

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002696: Input: gpio-keys - cancel delayed work only in case of GPIO. Affects Kernel versions < 8b1ae300c2953257c146b5f0757537935c0b6027. 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 Kernel package is a fundamental component of the Linux operating system. It provides the core functionality and interfaces for various hardware devices and software components. One of its features is the gpio-keys input driver, which handles input events from GPIO (General Purpose Input/Output) buttons. This driver allows users to interact with the system through physical buttons connected to GPIO pins. However, a vulnerability has been discovered in the gpio-keys driver, which can lead to potential security issues.

Vulnerability Detail

The vulnerability in the gpio-keys driver arises from a failure to properly cancel delayed work in certain cases. When a GPIO button is pressed, the gpio-keys driver schedules a delayed work to handle the input event. However, in some scenarios, this delayed work is not canceled when it should be, potentially leading to unexpected behavior or security vulnerabilities. The exact impact and attack vectors of this vulnerability have not been proven yet, but it poses a potential risk to the system's integrity and security.

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

There is no specific workaround mentioned for this vulnerability. The recommended approach is to update the Kernel package to the fixed version.

Conclusion

The vulnerability in the gpio-keys driver of the Kernel package can lead to potential security issues. It is crucial to update the Kernel package to version v5.18.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The gpio-keys driver is a component of the Linux Kernel that handles input events from GPIO buttons. It allows users to interact with the system through physical buttons connected to GPIO pins.

Delayed work refers to tasks or actions that are scheduled to be executed after a certain delay. In the case of the gpio-keys driver, delayed work is used to handle input events from GPIO buttons.

The exact risks of this vulnerability are not yet proven, but they could include unexpected behavior or security vulnerabilities. It is important to update the Kernel package to mitigate any potential risks.

The process of updating the Linux Kernel package depends on the specific distribution you are using. Generally, it involves using package management tools or manually compiling and installing the updated Kernel version. Refer to your distribution's documentation for detailed instructions.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.

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