GHSA-862J-6X74-2P6M

Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31
VLAI
Details

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

drm/imagination: Size page table preallocation by device address

Commit 0a8224058a58 ("drm/imagination: Fix page count for page table for map() interface") passed the device address to pvr_mmu_op_context_create(), but the preallocation is still sized from device_addr + sgt_offset with an exclusive end. The offset into the object's pages has no place in a device-virtual range, and the exclusive end allocates one table too many when the range ends on a table boundary.

Count the tables from device_addr and the inclusive end of the range.

The new calculation does not take page table indices into account. This fixes another issue with the previous implementation, where the difference between start and end indices could underflow when a mapping crossed a page table boundary. This would lead to the driver preallocating a huge number of MMU pages, exhausting system memory and triggering an out of memory panic.

[Alessio: add paragraph to point out OOM bug being fixed, cc stable]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99004"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-23T13:17:22Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/imagination: Size page table preallocation by device address\n\nCommit 0a8224058a58 (\"drm/imagination: Fix page count for page table for\nmap() interface\") passed the device address to\npvr_mmu_op_context_create(), but the preallocation is still sized from\ndevice_addr + sgt_offset with an exclusive end. The offset into the\nobject\u0027s pages has no place in a device-virtual range, and the exclusive\nend allocates one table too many when the range ends on a table\nboundary.\n\nCount the tables from device_addr and the inclusive end of the range.\n\nThe new calculation does not take page table indices into account. This\nfixes another issue with the previous implementation, where the\ndifference between start and end indices could underflow when a mapping\ncrossed a page table boundary. This would lead to the driver\npreallocating a huge number of MMU pages, exhausting system memory and\ntriggering an out of memory panic.\n\n[Alessio: add paragraph to point out OOM bug being fixed, cc stable]",
  "id": "GHSA-862j-6x74-2p6m",
  "modified": "2026-10-23T15:31:34Z",
  "published": "2026-10-23T15:31:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99004"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/51b56bad96fd20127034f660b337c00317c65151"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/789f290b2e81d42820bddcb4010ffbc2ae2ded54"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7f73da0facf864fe796371ebaccacb1fee678aaf"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f9b215b3e37a5047c406545de51bf8a2aeb4cd1c"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.