Menu

Star on GitHub · 3.2k

CVE-2022-48975

5.5 · MEDIUM

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():…

Published Oct 21, 2024CWE-401EPSS 0.24%

Overview

CVE-2022-48975 is a medium-severity vulnerability. It was published on October 21, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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 0xffff88810b406400 (size 512):

comm "python3", pid 1682, jiffies 4295346908 (age 24.090s)

backtrace:

kmalloc_trace

device_add device_private_init at drivers/base/core.c:3361

(inlined by) device_add at drivers/base/core.c:3411

cdev_device_add

gpiolib_cdev_register

gpiochip_setup_dev

gpiochip_add_data_with_key

gcdev_register() & gcdev_unregister() would call device_add() &

device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to

register/unregister device.

However, if device_add() succeeds, some resource (like

struct device_private allocated by device_private_init())

is not released by device_del().

Therefore, after device_add() succeeds by gcdev_register(), it

needs to call put_device() to release resource in the error handle

path.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-48975?

CVE-2022-48975 is a medium-severity vulnerability. It was published on October 21, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-48975?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-48975?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-48975?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-48975 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all