gpio: amd8111: Fix PCI device reference count leak
Published Oct 21, 2024
5.5
MEDIUMCVSS 3.1
EPSS 0.24%
Description
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().
Affected products
-
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version
-
- Version 3.6StatusaffectedConstraints-
- Version 0StatusunaffectedConstraints<3.6
- Version 4.14.302StatusunaffectedConstraints<=4.14.*
- Version 4.19.269StatusunaffectedConstraints<=4.19.*
- Version 4.9.336StatusunaffectedConstraints<=4.9.*
- Version 5.10.159StatusunaffectedConstraints<=5.10.*
- Version 5.15.83StatusunaffectedConstraints<=5.15.*
- Version 5.4.227StatusunaffectedConstraints<=5.4.*
- Version 6.0.13StatusunaffectedConstraints<=6.0.*
- Version 6.1StatusunaffectedConstraints<=*
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unaffected |
| |||||||||||||||||||||||||||||||||
| Linux | Linux | affected |
|
- ≥ 3.6 · < 4.9.336
- ≥ 4.10 · < 4.14.302
- ≥ 4.15 · < 4.19.269
- ≥ 4.20 · < 5.4.227
- ≥ 5.5 · < 5.10.159
- ≥ 5.11 · < 5.15.83
- ≥ 5.16 · < 6.0.13
- 6.1
- 6.1
- 6.1
- 6.1
- 6.1
- 6.1
- 6.1
- 6.1
No data.
Red Hat Enterprise Linux 6
kernel
Not affected
Red Hat Enterprise Linux 7
kernel
Not affected
Red Hat Enterprise Linux 7
kernel-rt
Not affected
Red Hat Enterprise Linux 8
kernel
Not affected
Red Hat Enterprise Linux 8
kernel-rt
Not affected
Red Hat Enterprise Linux 9
kernel
Not affected
Red Hat Enterprise Linux 9
kernel-rt
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 7 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | n/a |
| Red Hat Enterprise Linux 8 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | n/a |
| Red Hat Enterprise Linux 9 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | n/a |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
References (13)
- https://access.redhat.com/security/cve/CVE-2022-48973 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2320727 Issue Tracking
- https://git.kernel.org/stable/c/4271515f189bd5fe2ec86b4089dab7cb804625d2 Patch
- https://git.kernel.org/stable/c/45fecdb9f658d9c82960c98240bc0770ade19aca Patch
- https://git.kernel.org/stable/c/4749c5cc147c9860b96db1e71cc36d1de1bd3f59 Patch
- https://git.kernel.org/stable/c/48bd5d3801f6b67cc144449d434abbd5043a6d37 Patch
- https://git.kernel.org/stable/c/5ee6413d3dd972930af787b2c0c7aaeb379fa521 Patch
- https://git.kernel.org/stable/c/71d591ef873f9ebb86cd8d053b3caee785b2de6a Patch
- https://git.kernel.org/stable/c/b2bc053ebbba57a06fa655db5ea796de2edce445 Patch
- https://git.kernel.org/stable/c/e364ce04d8f840478b09eee57b614de7cf1e743e Patch
- https://lore.kernel.org/linux-cve-announce/2024102145-CVE-2022-48973-a0e7@gregkh/T
- https://nvd.nist.gov/vuln/detail/CVE-2022-48973
- https://www.cve.org/CVERecord?id=CVE-2022-48973
Change history (0)
No recorded changes yet.