Memory Leak Vulnerability in Linux Kernel - CVE-2022-48975

linux Updated 02 Oct 2025

Summary

21/10/2024
N/A
No i
Medium
5.5

CVE-2022-48975: In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xff... Affects linux versions 5.10.103-1 – 6.9.9-1. 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 Linux kernel is the core component of many operating systems, providing essential services for hardware and software interaction. It manages system resources, facilitates communication between hardware and software, and ensures system stability. This vulnerability specifically affects the GPIO (General Purpose Input/Output) subsystem, which is crucial for managing input and output operations on various hardware devices. The vulnerability arises from improper resource management during device registration, leading to potential memory leaks.

Vulnerability Detail

In the Linux kernel, a memory leak was identified in the gpiochip_setup_dev() function. When a device is registered using gcdev_register(), the device_add() function is called, which allocates resources that are not properly released by device_del(). This oversight can lead to unreferenced memory objects persisting in the system, consuming resources unnecessarily. Additionally, when the number of GPIOs (gc->ngpio) is zero, the system still attempts to allocate memory, which can lead to further inefficiencies. The vulnerability can result in degraded system performance and increased memory usage over time.

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

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the patch as soon as it is available.

Conclusion

CVE-2022-48975 is a significant memory leak vulnerability in the Linux kernel that can lead to resource exhaustion. It is crucial for users to update their systems to the patched version to ensure optimal performance and security. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2022-48975 is a memory leak vulnerability in the Linux kernel's GPIO subsystem, which can lead to resource exhaustion and degraded system performance.

If your system uses the affected Linux kernel version, it may experience increased memory usage over time, potentially leading to performance issues.

Yes, a patch is available in Linux kernel version 6.1.4-1 and later. It is recommended to update your system to this version or newer.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check if your application is affected by CVE-2022-48975 using the Vulert playground without any signup.

While there are no specific workarounds, it is advisable to monitor your system's memory usage and apply the patch as soon as possible to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

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