Vulnerability-Lookup

GHSA-GXMW-VHGM-HQG8

Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-05-27 15:33

Details

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

mm/memfd_luo: fix physical address conversion in put_folios cleanup

In memfd_luo_retrieve_folios()'s put_folios cleanup path:

kho_restore_folio() expects a phys_addr_t (physical address) but receives a raw PFN (pfolio->pfn). This causes kho_restore_page() to check the wrong physical address (pfn << PAGE_SHIFT instead of the actual physical address).
This loop lacks the !pfolio->pfn check that exists in the main retrieval loop and memfd_luo_discard_folios(), which could incorrectly process sparse file holes where pfn=0.

Fix by converting PFN to physical address with PFN_PHYS() and adding the !pfolio->pfn check, matching the pattern used elsewhere in this file.

This issue was identified by the AI review. https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-46013"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-27T14:17:19Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/memfd_luo: fix physical address conversion in put_folios cleanup\n\nIn memfd_luo_retrieve_folios()\u0027s put_folios cleanup path:\n\n1. kho_restore_folio() expects a phys_addr_t (physical address) but\n   receives a raw PFN (pfolio-\u003epfn). This causes kho_restore_page() to\n   check the wrong physical address (pfn \u003c\u003c PAGE_SHIFT instead of the\n   actual physical address).\n\n2. This loop lacks the !pfolio-\u003epfn check that exists in the main\n   retrieval loop and memfd_luo_discard_folios(), which could\n   incorrectly process sparse file holes where pfn=0.\n\nFix by converting PFN to physical address with PFN_PHYS() and adding\nthe !pfolio-\u003epfn check, matching the pattern used elsewhere in this file.\n\nThis issue was identified by the AI review.\nhttps://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn",
  "id": "GHSA-gxmw-vhgm-hqg8",
  "modified": "2026-05-27T15:33:20Z",
  "published": "2026-05-27T15:33:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46013"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3538f90ab89aaf302782b4b073a0aae66904cd67"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-46013 (GCVE-0-2026-46013)

Vulnerability from cvelistv5 – Published: 2026-05-27 12:56 – Updated: 2026-05-27 12:56

Title

mm/memfd_luo: fix physical address conversion in put_folios cleanup

Summary

In the Linux kernel, the following vulnerability has been resolved: mm/memfd_luo: fix physical address conversion in put_folios cleanup In memfd_luo_retrieve_folios()'s put_folios cleanup path: 1. kho_restore_folio() expects a phys_addr_t (physical address) but receives a raw PFN (pfolio->pfn). This causes kho_restore_page() to check the wrong physical address (pfn << PAGE_SHIFT instead of the actual physical address). 2. This loop lacks the !pfolio->pfn check that exists in the main retrieval loop and memfd_luo_discard_folios(), which could incorrectly process sparse file holes where pfn=0. Fix by converting PFN to physical address with PFN_PHYS() and adding the !pfolio->pfn check, matching the pattern used elsewhere in this file. This issue was identified by the AI review. https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn

Severity

No CVSS data available.

Assigner

Linux

References

2 references

URL	Tags
https://git.kernel.org/stable/c/bd0d6bde286a2b8e3…
https://git.kernel.org/stable/c/3538f90ab89aaf302…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: b3749f174d686627f702234e64bad976dc432dbc , < bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9 (git) Affected: b3749f174d686627f702234e64bad976dc432dbc , < 3538f90ab89aaf302782b4b073a0aae66904cd67 (git)
Linux	Linux	Affected: 6.19 Unaffected: 0 , < 6.19 (semver) Unaffected: 7.0.4 , ≤ 7.0.* (semver) Unaffected: 7.1-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/memfd_luo.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9",
              "status": "affected",
              "version": "b3749f174d686627f702234e64bad976dc432dbc",
              "versionType": "git"
            },
            {
              "lessThan": "3538f90ab89aaf302782b4b073a0aae66904cd67",
              "status": "affected",
              "version": "b3749f174d686627f702234e64bad976dc432dbc",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/memfd_luo.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.19"
            },
            {
              "lessThan": "6.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.4",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1-rc1",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/memfd_luo: fix physical address conversion in put_folios cleanup\n\nIn memfd_luo_retrieve_folios()\u0027s put_folios cleanup path:\n\n1. kho_restore_folio() expects a phys_addr_t (physical address) but\n   receives a raw PFN (pfolio-\u003epfn). This causes kho_restore_page() to\n   check the wrong physical address (pfn \u003c\u003c PAGE_SHIFT instead of the\n   actual physical address).\n\n2. This loop lacks the !pfolio-\u003epfn check that exists in the main\n   retrieval loop and memfd_luo_discard_folios(), which could\n   incorrectly process sparse file holes where pfn=0.\n\nFix by converting PFN to physical address with PFN_PHYS() and adding\nthe !pfolio-\u003epfn check, matching the pattern used elsewhere in this file.\n\nThis issue was identified by the AI review.\nhttps://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-27T12:56:15.236Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9"
        },
        {
          "url": "https://git.kernel.org/stable/c/3538f90ab89aaf302782b4b073a0aae66904cd67"
        }
      ],
      "title": "mm/memfd_luo: fix physical address conversion in put_folios cleanup",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-46013",
    "datePublished": "2026-05-27T12:56:15.236Z",
    "dateReserved": "2026-05-13T15:03:33.092Z",
    "dateUpdated": "2026-05-27T12:56:15.236Z",
    "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.

Action not permitted

GHSA-GXMW-VHGM-HQG8

CVE-2026-46013 (GCVE-0-2026-46013)

Tags

Sightings

Nomenclature