🛡️ UBUNTU-CVE-2022-48973
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: gpio: amd8111: Fix PCI device reference count leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() after the 'out' label. Since pci_dev_put() can handle NULL input parameter, there is no problem for the 'Device not found' branch. For the normal path, add pci_dev_put() in amd_gpio_exit().

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2024-10-21
Updated 2026-06-15
Modified 2026-06-04
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 5.15.0-67.74
linux-allwinner-5.19
linux-aws 5.15.0-1031.35
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1031.35~20.04.1
linux-aws-5.19
linux-aws-5.3
linux-aws-5.4 5.4.0-1097.105~18.04.1
linux-aws-5.8
linux-aws-6.2
linux-aws-6.5
linux-aws-fips
linux-aws-hwe 4.15.0-1151.164~16.04.1
linux-azure 5.15.0-1034.41
linux-azure-4.15 4.15.0-1162.177
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1034.41~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.4 5.4.0-1104.110~18.04.1
linux-azure-5.8
linux-azure-6.2
linux-azure-6.5
linux-azure-edge
linux-azure-fde 5.15.0-1034.41.1
linux-azure-fde-5.19
linux-azure-fde-6.2
linux-azure-fips
linux-bluefield
linux-fips
linux-gcp 5.15.0-1030.37
linux-gcp-4.15 4.15.0-1146.162
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1030.37~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.4 5.4.0-1101.110~18.04.1
linux-gcp-5.8
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-fips
linux-gke 5.15.0-1028.33
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 5.15.0-1016.21
linux-gkeop-5.15 5.15.0-1016.21~20.04.1
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-67.74~20.04.1
linux-hwe-5.19
linux-hwe-5.4 5.4.0-144.161~18.04.1
linux-hwe-5.8
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-edge
linux-ibm 5.15.0-1026.29
linux-ibm-5.4 5.4.0-1045.50~18.04.1
linux-intel-5.13
linux-intel-iot-realtime 5.15.0-1022.27
linux-intel-iotg 5.15.0-1026.31
linux-intel-iotg-5.15 5.15.0-1026.31~20.04.1
linux-iot 5.4.0-1013.15
linux-kvm 5.15.0-1029.34
linux-lowlatency 5.15.0-67.74
linux-lowlatency-hwe-5.15 5.15.0-67.74~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lts-xenial
linux-nvidia 5.15.0-1023.23
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-tegra-5.15 5.15.0-1014.14~20.04.1
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.5
linux-oracle 5.15.0-1030.36
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1030.36~20.04.1
linux-oracle-5.3
linux-oracle-5.4 5.4.0-1094.103~18.04.1
linux-oracle-5.8
linux-oracle-6.5
linux-raspi 5.15.0-1025.27
linux-raspi-5.4 5.4.0-1081.92~18.04.1
linux-raspi-realtime
linux-raspi2
linux-realtime 5.15.0-1033.36
linux-riscv
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1030.34~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.5
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx-zynqmp 5.4.0-1022.26

References

Similar Threats

Patch Gap Protection

Running software with known vulnerabilities?

BotEraser can help reduce exposure by blocking IPs associated with exploit activity — even before a patch is available.

Start Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.