Vulnerability-Lookup

GHSA-832M-273V-9HPC

Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31

Details

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

kho: fix size calculation in kho_preserved_memory_reserve()

kho_preserved_memory_reserve() calculates the size of a preservation by doing 1 << (order + PAGE_SHIFT). Since the '1' is a 32-bit integer, it can only be shifted by 31. That is, it will only work for preservations up to 2 GiB. Larger preservations will trigger undefined behaviour.

While preservations larger than 2 GiB can't be obtained via folios currently, they can be obtained via kho_preserve_pages().

For example, memblock reserve_mem uses kho_preserve_pages(). Reservations larger than 2 GiB are valid and will trigger this bug if properly aligned.

Fix it by using 1UL for shifting.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-89568"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-11T20:19:40Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nkho: fix size calculation in kho_preserved_memory_reserve()\n\nkho_preserved_memory_reserve() calculates the size of a preservation by\ndoing 1 \u003c\u003c (order + PAGE_SHIFT). Since the \u00271\u0027 is a 32-bit integer, it\ncan only be shifted by 31. That is, it will only work for preservations\nup to 2 GiB. Larger preservations will trigger undefined behaviour.\n\nWhile preservations larger than 2 GiB can\u0027t be obtained via folios\ncurrently, they can be obtained via kho_preserve_pages().\n\nFor example, memblock reserve_mem uses kho_preserve_pages().\nReservations larger than 2 GiB are valid and will trigger this bug if\nproperly aligned.\n\nFix it by using 1UL for shifting.",
  "id": "GHSA-832m-273v-9hpc",
  "modified": "2026-09-11T21:31:32Z",
  "published": "2026-09-11T21:31:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89568"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3a0b8fa2eb36afc88b62a95f33f0c77c71fa5ded"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/42a6f03cf352eb6e6dbeef95e75e686f4cdb9bd1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-89568 (GCVE-0-2026-89568)

Vulnerability from cvelistv5 – Published: 2026-09-11 19:44 – Updated: 2026-09-11 19:44

Title

kho: fix size calculation in kho_preserved_memory_reserve()

Summary

In the Linux kernel, the following vulnerability has been resolved: kho: fix size calculation in kho_preserved_memory_reserve() kho_preserved_memory_reserve() calculates the size of a preservation by doing 1 << (order + PAGE_SHIFT). Since the '1' is a 32-bit integer, it can only be shifted by 31. That is, it will only work for preservations up to 2 GiB. Larger preservations will trigger undefined behaviour. While preservations larger than 2 GiB can't be obtained via folios currently, they can be obtained via kho_preserve_pages(). For example, memblock reserve_mem uses kho_preserve_pages(). Reservations larger than 2 GiB are valid and will trigger this bug if properly aligned. Fix it by using 1UL for shifting.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/42a6f03cf352eb6e6…
https://git.kernel.org/stable/c/3a0b8fa2eb36afc88…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: fc33e4b44b2717feba2f6f07ce7943a96499c9ec , < 42a6f03cf352eb6e6dbeef95e75e686f4cdb9bd1 (git) Affected: fc33e4b44b2717feba2f6f07ce7943a96499c9ec , < 3a0b8fa2eb36afc88b62a95f33f0c77c71fa5ded (git)
Linux	Linux	Affected: 6.16 Unaffected: 0 , < 6.16 (semver) Unaffected: 7.2.4 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/liveupdate/kexec_handover.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "42a6f03cf352eb6e6dbeef95e75e686f4cdb9bd1",
              "status": "affected",
              "version": "fc33e4b44b2717feba2f6f07ce7943a96499c9ec",
              "versionType": "git"
            },
            {
              "lessThan": "3a0b8fa2eb36afc88b62a95f33f0c77c71fa5ded",
              "status": "affected",
              "version": "fc33e4b44b2717feba2f6f07ce7943a96499c9ec",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/liveupdate/kexec_handover.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "lessThan": "6.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.4",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nkho: fix size calculation in kho_preserved_memory_reserve()\n\nkho_preserved_memory_reserve() calculates the size of a preservation by\ndoing 1 \u003c\u003c (order + PAGE_SHIFT). Since the \u00271\u0027 is a 32-bit integer, it\ncan only be shifted by 31. That is, it will only work for preservations\nup to 2 GiB. Larger preservations will trigger undefined behaviour.\n\nWhile preservations larger than 2 GiB can\u0027t be obtained via folios\ncurrently, they can be obtained via kho_preserve_pages().\n\nFor example, memblock reserve_mem uses kho_preserve_pages().\nReservations larger than 2 GiB are valid and will trigger this bug if\nproperly aligned.\n\nFix it by using 1UL for shifting."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-11T19:44:38.078Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/42a6f03cf352eb6e6dbeef95e75e686f4cdb9bd1"
        },
        {
          "url": "https://git.kernel.org/stable/c/3a0b8fa2eb36afc88b62a95f33f0c77c71fa5ded"
        }
      ],
      "title": "kho: fix size calculation in kho_preserved_memory_reserve()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89568",
    "datePublished": "2026-09-11T19:44:38.078Z",
    "dateReserved": "2026-09-11T19:38:34.726Z",
    "dateUpdated": "2026-09-11T19:44:38.078Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.