ghsa-3c4m-3xhw-2cr2
Vulnerability from github
Published
2024-05-17 15:31
Modified
2025-01-10 18:31
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Details

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/pm: fix a double-free in si_dpm_init

When the allocation of adev->pm.dpm.dyn_state.vddc_dependency_on_dispclk.entries fails, amdgpu_free_extended_power_table is called to free some fields of adev. However, when the control flow returns to si_dpm_sw_init, it goes to label dpm_failed and calls si_dpm_fini, which calls amdgpu_free_extended_power_table again and free those fields again. Thus a double-free is triggered.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2023-52691",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-415",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-05-17T15:15:20Z",
      severity: "HIGH",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: fix a double-free in si_dpm_init\n\nWhen the allocation of\nadev->pm.dpm.dyn_state.vddc_dependency_on_dispclk.entries fails,\namdgpu_free_extended_power_table is called to free some fields of adev.\nHowever, when the control flow returns to si_dpm_sw_init, it goes to\nlabel dpm_failed and calls si_dpm_fini, which calls\namdgpu_free_extended_power_table again and free those fields again. Thus\na double-free is triggered.",
   id: "GHSA-3c4m-3xhw-2cr2",
   modified: "2025-01-10T18:31:37Z",
   published: "2024-05-17T15:31:11Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2023-52691",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/06d95c99d5a4f5accdb79464076efe62e668c706",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/2bf47c89bbaca2bae16581ef1b28aaec0ade0334",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/ac16667237a82e2597e329eb9bc520d1cf9dff30",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/aeed2b4e4a70c7568d4a5eecd6a109713c0dfbf4",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/afe9f5b871f86d58ecdc45b217b662227d7890d0",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/ca8e2e251c65e5a712f6025e27bd9b26d16e6f4a",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/f957a1be647f7fc65926cbf572992ec2747a93f2",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/fb1936cb587262cd539e84b34541abb06e42b2f9",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2024/06/msg00016.html",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.




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.