ghsa-xv88-66vv-vx9g
Vulnerability from github
Published
2024-10-21 21:30
Modified
2024-10-25 18:30
Details

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().

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2022-48973",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-10-21T20:15:09Z",
      severity: "MODERATE",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: amd8111: Fix PCI device reference count leak\n\nfor_each_pci_dev() is implemented by pci_get_device(). The comment of\npci_get_device() says that it will increase the reference count for the\nreturned pci_dev and also decrease the reference count for the input\npci_dev @from if it is not NULL.\n\nIf we break for_each_pci_dev() loop with pdev not NULL, we need to call\npci_dev_put() to decrease the reference count. Add the missing\npci_dev_put() after the 'out' label. Since pci_dev_put() can handle NULL\ninput parameter, there is no problem for the 'Device not found' branch.\nFor the normal path, add pci_dev_put() in amd_gpio_exit().",
   id: "GHSA-xv88-66vv-vx9g",
   modified: "2024-10-25T18:30:47Z",
   published: "2024-10-21T21:30:51Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-48973",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/4271515f189bd5fe2ec86b4089dab7cb804625d2",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/45fecdb9f658d9c82960c98240bc0770ade19aca",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/4749c5cc147c9860b96db1e71cc36d1de1bd3f59",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/48bd5d3801f6b67cc144449d434abbd5043a6d37",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/5ee6413d3dd972930af787b2c0c7aaeb379fa521",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/71d591ef873f9ebb86cd8d053b3caee785b2de6a",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/b2bc053ebbba57a06fa655db5ea796de2edce445",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/e364ce04d8f840478b09eee57b614de7cf1e743e",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.