Memory Leak in gpio: sim Package

Kernel Updated 02 Oct 2025

Summary

07/03/2023
N/A
No i
Unrated
Not published

GSD-2023-1002309: gpio: sim: fix a memory leak. Affects Kernel versions >= cb8c474e79be458f58e9df073f51ca159f3a2aa0, < 854e1ecff266033d3149666d3c5b8b0e174b4210. 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 Penetration testing for web, API and mobile 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: sim package is a component of the Linux Kernel, which is responsible for managing the General Purpose Input/Output (GPIO) pins on a system. GPIO pins allow the system to interact with external devices, such as sensors, buttons, and LEDs. The gpio: sim package provides a simulation environment for testing GPIO functionality. It is used by developers to emulate GPIO behavior without the need for physical hardware. However, a vulnerability has been discovered in this package that can lead to a memory leak.

Vulnerability Detail

The vulnerability in the gpio: sim package is caused by a memory leak. A memory leak occurs when a program fails to release memory that it no longer needs, resulting in a gradual depletion of available memory resources. In the case of the gpio: sim package, this memory leak can lead to resource exhaustion, causing the system to become unresponsive or crash. An attacker could potentially exploit this vulnerability to launch denial-of-service attacks or gain unauthorized access to sensitive information stored in memory. The vulnerability was introduced in version v5.17 of the Linux Kernel and has been fixed in version v6.1.13.

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 available for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel to the latest version.

Conclusion

The memory leak vulnerability in the gpio: sim package can have severe consequences, including system crashes and unauthorized access to sensitive information. It is crucial to update the Linux Kernel to version v6.1.13 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

The gpio: sim package is a component of the Linux Kernel that provides a simulation environment for testing GPIO functionality without physical hardware.

A memory leak occurs when a program fails to release memory that it no longer needs, leading to a gradual depletion of available memory resources.

The memory leak vulnerability in the gpio: sim package can result in resource exhaustion, causing system unresponsiveness or crashes. It could also be exploited by attackers to launch denial-of-service attacks or gain unauthorized access to sensitive information stored in memory.

To fix the vulnerability, it is recommended to update the Linux Kernel to version v6.1.13 or later, which includes the necessary patch to address the memory leak issue.

No, there is no specific workaround available for this vulnerability. Updating the Linux Kernel to the latest version is the recommended solution.

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