ghsa-w6jp-r2wp-jmpx
Vulnerability from github
Published
2024-05-20 12:30
Modified
2024-06-10 18:31
Details

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

drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr()

Subject: [PATCH] drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr()

If some the pages or sgt allocation failed, we shouldn't release the pages ref we got earlier, otherwise we will end up with unbalanced get/put_pages() calls. We should instead leave everything in place and let the BO release function deal with extra cleanup when the object is destroyed, or let the fault handler try again next time it's called.

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2024-35951",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-05-20T10:15:10Z",
      severity: null,
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr()\n\nSubject: [PATCH] drm/panfrost: Fix the error path in\n panfrost_mmu_map_fault_addr()\n\nIf some the pages or sgt allocation failed, we shouldn't release the\npages ref we got earlier, otherwise we will end up with unbalanced\nget/put_pages() calls. We should instead leave everything in place\nand let the BO release function deal with extra cleanup when the object\nis destroyed, or let the fault handler try again next time it's called.",
   id: "GHSA-w6jp-r2wp-jmpx",
   modified: "2024-06-10T18:31:03Z",
   published: "2024-05-20T12:30:27Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-35951",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/1fc9af813b25e146d3607669247d0f970f5a87c3",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/31806711e8a4b75e09b1c43652f2a6420e6e1002",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/e18070c622c63f0cab170348e320454728c277aa",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2024/05/30/1",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2024/05/30/2",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
}


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.