GHSA-C4PH-4532-7VQ7

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33
VLAI
Details

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

gpu/buddy: bail out of try_harder when alignment cannot be honoured

The try_harder contiguous fallback could return a range whose start offset did not match the caller's min_block_size. When a candidate's start is misaligned, realign it: free the misaligned run and reallocate exactly @size at the next lower min_block_size boundary. This keeps the returned size unchanged with no surplus to trim, and rejects the request only when no aligned candidate fits.

v2: align misaligned candidates down to min_block_size instead of bailing out, for both the RHS and LHS paths (Matthew).

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-72244"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:21:51Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ngpu/buddy: bail out of try_harder when alignment cannot be honoured\n\nThe try_harder contiguous fallback could return a range whose start\noffset did not match the caller\u0027s min_block_size. When a candidate\u0027s\nstart is misaligned, realign it: free the misaligned run and reallocate\nexactly @size at the next lower min_block_size boundary. This keeps the\nreturned size unchanged with no surplus to trim, and rejects the request\nonly when no aligned candidate fits.\n\nv2: align misaligned candidates down to min_block_size instead of\n    bailing out, for both the RHS and LHS paths (Matthew).",
  "id": "GHSA-c4ph-4532-7vq7",
  "modified": "2026-08-17T06:33:18Z",
  "published": "2026-08-15T06:32:17Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72244"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/419d7d9306491f3e0e417cf794844c73cabee090"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4289531106ee175a6eb45db7d4f2734d1dae9887"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/56bc6384314fb9ae98975fb2af8b143097ede3dc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7185c5262435b93e5eeffa647008992256b9c51a"
    }
  ],
  "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.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…