GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-94JH-P9FJ-QXF8

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:

s390/mm: Fix handling of _PAGE_UNUSED pte bit

The _PAGE_UNUSED softbit should not really be lying around. Its sole purpose is to signal to try_to_unmap_one() and try_to_migrate_one() that the page can be discarded instead of being moved / swapped.

KVM has no way to know why a page is being unmapped, so it sets the bit on userspace ptes corresponding to unused guest pages every time they get unmapped. KVM has no reasonable way to clear the bit once the page is in use again.

While set_ptes() checks and clears the bit, other paths that set new ptes did not. This led to used pages being thrown out as if they were unused, causing guest corruption.

Fix the issue by clearing the _PAGE_UNUSED bit for present ptes in set_pte(), i.e. whenever a present pte is getting set. The check in set_ptes() is then redundant and can be removed.

Also fix gmap_helper_try_set_pte_unused() to only set the bit if the pte is present; the _PAGE_UNUSED bit is only defined for present ptes and thus should not be set for non-present ptes.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-72412"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:14Z",
    "severity": "CRITICAL"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/mm: Fix handling of _PAGE_UNUSED pte bit\n\nThe _PAGE_UNUSED softbit should not really be lying around. Its sole\npurpose is to signal to try_to_unmap_one() and try_to_migrate_one()\nthat the page can be discarded instead of being moved / swapped.\n\nKVM has no way to know why a page is being unmapped, so it sets the bit\non userspace ptes corresponding to unused guest pages every time they\nget unmapped. KVM has no reasonable way to clear the bit once the page\nis in use again.\n\nWhile set_ptes() checks and clears the bit, other paths that set new\nptes did not. This led to used pages being thrown out as if they were\nunused, causing guest corruption.\n\nFix the issue by clearing the _PAGE_UNUSED bit for present ptes in\nset_pte(), i.e. whenever a present pte is getting set. The check in\nset_ptes() is then redundant and can be removed.\n\nAlso fix gmap_helper_try_set_pte_unused() to only set the bit if the\npte is present; the _PAGE_UNUSED bit is only defined for present ptes\nand thus should not be set for non-present ptes.",
  "id": "GHSA-94jh-p9fj-qxf8",
  "modified": "2026-08-17T06:33:28Z",
  "published": "2026-08-15T06:32:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72412"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d4bb00704a66024502261fa7a523c07420249fea"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fda07c8e4b54b9105f1ca73f0adea7b244d405f4"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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…