Integer Overflow in gpio-xilinx Package

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004328: gpio: gpio-xilinx: Fix integer overflow. Affects Kernel versions >= 02b3f84d9080b0f4297f31258307f626a43faba5, < e129e5486b981d324057e6986059f852658b0d00. 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 gpio-xilinx package is a component of the Linux Kernel ecosystem. It provides functionality for handling General Purpose Input/Output (GPIO) pins on Xilinx devices. GPIO pins are used to control and monitor external devices connected to the system. The gpio-xilinx package is widely used in various embedded systems and devices that utilize Xilinx hardware. However, a vulnerability has been discovered in the package that could potentially lead to security issues.

Vulnerability Detail

The vulnerability in the gpio-xilinx package is related to an integer overflow. An attacker could exploit this vulnerability by providing malicious input that triggers the overflow during certain operations. This could lead to unexpected behavior, including memory corruption or system crashes. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v5.14 of the Linux Kernel and has been fixed in version v5.15.58 by commit e129e5486b981d324057e6986059f852658b0d00.

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 apply the fix by updating the Linux Kernel to the latest version.

Conclusion

The gpio-xilinx package in the Linux Kernel is vulnerable to an integer overflow. This vulnerability can potentially lead to memory corruption or system crashes. It is recommended to update the Linux Kernel to version v5.15.58 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The gpio-xilinx package is a component of the Linux Kernel ecosystem that provides functionality for handling GPIO pins on Xilinx devices.

An integer overflow occurs when an arithmetic operation results in a value that exceeds the maximum representable value for the data type used to store the result. In this vulnerability, the integer overflow can lead to unexpected behavior and potential security issues.

An attacker can exploit this vulnerability by providing malicious input that triggers the integer overflow during certain operations. This can lead to memory corruption or system crashes, potentially allowing the attacker to gain unauthorized access or disrupt the system.

No, the impact and attack plausibility of this vulnerability have not been proven yet. However, it is still important to apply the fix to mitigate any potential risks.

To fix this vulnerability, update the Linux Kernel to version v5.15.58 or later. Pull the latest updates from the official Linux Kernel repository and recompile/install the new kernel version on the affected system.

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