CVE-2025-37868 (GCVE-0-2025-37868)

Vulnerability from cvelistv5 – Published: 2025-05-09 06:43 – Updated: 2026-05-23 15:58
VLAI
Title
drm/xe/userptr: fix notifier vs folio deadlock
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/xe/userptr: fix notifier vs folio deadlock User is reporting what smells like notifier vs folio deadlock, where migrate_pages_batch() on core kernel side is holding folio lock(s) and then interacting with the mappings of it, however those mappings are tied to some userptr, which means calling into the notifier callback and grabbing the notifier lock. With perfect timing it looks possible that the pages we pulled from the hmm fault can get sniped by migrate_pages_batch() at the same time that we are holding the notifier lock to mark the pages as accessed/dirty, but at this point we also want to grab the folio locks(s) to mark them as dirty, but if they are contended from notifier/migrate_pages_batch side then we deadlock since folio lock won't be dropped until we drop the notifier lock. Fortunately the mark_page_accessed/dirty is not really needed in the first place it seems and should have already been done by hmm fault, so just remove it. (cherry picked from commit bd7c0cb695e87c0e43247be8196b4919edbe0e85)
Severity
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 2a24c98f0e4cc994334598d4f3a851972064809d , < 65dc4e3d5b01db0179fc95c1f0bdb87194c28ab5 (git)
Affected: 0a98219bcc961edd3388960576e4353e123b4a51 , < 90574ecf6052be83971d91d16600c5cf07003bbb (git)
Affected: 0a98219bcc961edd3388960576e4353e123b4a51 , < 2577b202458cddff85cc154b1fe7f313e0d1f418 (git)
Affected: f9326f529da7298a95643c3267f1c0fdb0db55eb (git)
Affected: 6.12.19 , < 6.12.25 (semver)
Affected: 6.13.7 , < 6.14 (semver)
Create a notification for this product.
Linux Linux Affected: 6.14
Unaffected: 0 , < 6.14 (semver)
Unaffected: 6.12.25 , ≤ 6.12.* (semver)
Unaffected: 6.14.4 , ≤ 6.14.* (semver)
Unaffected: 6.15 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/xe/xe_hmm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "65dc4e3d5b01db0179fc95c1f0bdb87194c28ab5",
              "status": "affected",
              "version": "2a24c98f0e4cc994334598d4f3a851972064809d",
              "versionType": "git"
            },
            {
              "lessThan": "90574ecf6052be83971d91d16600c5cf07003bbb",
              "status": "affected",
              "version": "0a98219bcc961edd3388960576e4353e123b4a51",
              "versionType": "git"
            },
            {
              "lessThan": "2577b202458cddff85cc154b1fe7f313e0d1f418",
              "status": "affected",
              "version": "0a98219bcc961edd3388960576e4353e123b4a51",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "f9326f529da7298a95643c3267f1c0fdb0db55eb",
              "versionType": "git"
            },
            {
              "lessThan": "6.12.25",
              "status": "affected",
              "version": "6.12.19",
              "versionType": "semver"
            },
            {
              "lessThan": "6.14",
              "status": "affected",
              "version": "6.13.7",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/xe/xe_hmm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.25",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.14.*",
              "status": "unaffected",
              "version": "6.14.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.25",
                  "versionStartIncluding": "6.12.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14.4",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.13.7",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe/userptr: fix notifier vs folio deadlock\n\nUser is reporting what smells like notifier vs folio deadlock, where\nmigrate_pages_batch() on core kernel side is holding folio lock(s) and\nthen interacting with the mappings of it, however those mappings are\ntied to some userptr, which means calling into the notifier callback and\ngrabbing the notifier lock. With perfect timing it looks possible that\nthe pages we pulled from the hmm fault can get sniped by\nmigrate_pages_batch() at the same time that we are holding the notifier\nlock to mark the pages as accessed/dirty, but at this point we also want\nto grab the folio locks(s) to mark them as dirty, but if they are\ncontended from notifier/migrate_pages_batch side then we deadlock since\nfolio lock won\u0027t be dropped until we drop the notifier lock.\n\nFortunately the mark_page_accessed/dirty is not really needed in the\nfirst place it seems and should have already been done by hmm fault, so\njust remove it.\n\n(cherry picked from commit bd7c0cb695e87c0e43247be8196b4919edbe0e85)"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-23T15:58:28.407Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/65dc4e3d5b01db0179fc95c1f0bdb87194c28ab5"
        },
        {
          "url": "https://git.kernel.org/stable/c/90574ecf6052be83971d91d16600c5cf07003bbb"
        },
        {
          "url": "https://git.kernel.org/stable/c/2577b202458cddff85cc154b1fe7f313e0d1f418"
        }
      ],
      "title": "drm/xe/userptr: fix notifier vs folio deadlock",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-37868",
    "datePublished": "2025-05-09T06:43:57.383Z",
    "dateReserved": "2025-04-16T04:51:23.959Z",
    "dateUpdated": "2026-05-23T15:58:28.407Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-37868",
      "date": "2026-06-05",
      "epss": "0.00038",
      "percentile": "0.11744"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-37868\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-05-09T07:16:07.880\",\"lastModified\":\"2025-11-12T20:37:04.923\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/xe/userptr: fix notifier vs folio deadlock\\n\\nUser is reporting what smells like notifier vs folio deadlock, where\\nmigrate_pages_batch() on core kernel side is holding folio lock(s) and\\nthen interacting with the mappings of it, however those mappings are\\ntied to some userptr, which means calling into the notifier callback and\\ngrabbing the notifier lock. With perfect timing it looks possible that\\nthe pages we pulled from the hmm fault can get sniped by\\nmigrate_pages_batch() at the same time that we are holding the notifier\\nlock to mark the pages as accessed/dirty, but at this point we also want\\nto grab the folio locks(s) to mark them as dirty, but if they are\\ncontended from notifier/migrate_pages_batch side then we deadlock since\\nfolio lock won\u0027t be dropped until we drop the notifier lock.\\n\\nFortunately the mark_page_accessed/dirty is not really needed in the\\nfirst place it seems and should have already been done by hmm fault, so\\njust remove it.\\n\\n(cherry picked from commit bd7c0cb695e87c0e43247be8196b4919edbe0e85)\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/xe/userptr: fix notifier vs folio deadlock El usuario informa lo que parece ser un deadlock entre notifier y folio, donde migration_pages_batch() en el lado del n\u00facleo central mantiene el bloqueo de folio y luego interact\u00faa con las asignaciones de este, sin embargo, esas asignaciones est\u00e1n vinculadas a alg\u00fan userptr, lo que significa llamar a la devoluci\u00f3n de llamada del notificador y tomar el bloqueo del notificador. Con una sincronizaci\u00f3n perfecta, parece posible que las p\u00e1ginas que extrajimos de la falla hmm puedan ser atacadas por migration_pages_batch() al mismo tiempo que mantenemos el bloqueo del notificador para marcar las p\u00e1ginas como accedidas/sucias, pero en este punto tambi\u00e9n queremos tomar el bloqueo de folio para marcarlos como sucios, pero si se disputan desde el lado de notifier/migrate_pages_batch, entonces nos bloqueamos ya que el bloqueo de folio no se eliminar\u00e1 hasta que eliminemos el bloqueo del notificador. Afortunadamente, mark_page_accessed/dirty no es realmente necesario en primer lugar, al parecer, y ya deber\u00eda haber sido realizado por hmm fault, as\u00ed que simplemente elim\u00ednelo. (seleccionado del commit bd7c0cb695e87c0e43247be8196b4919edbe0e85)\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-667\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.12.19\",\"versionEndExcluding\":\"6.12.25\",\"matchCriteriaId\":\"4E18BED3-0115-482C-861A-9ECA8B05EEB2\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.13.7\",\"versionEndExcluding\":\"6.14\",\"matchCriteriaId\":\"87A94BBB-C489-4F0E-AC35-A6E9E1316FCE\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.14.1\",\"versionEndExcluding\":\"6.14.4\",\"matchCriteriaId\":\"26175852-4D93-410C-BC8C-C405F2A9D737\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:-:*:*:*:*:*:*\",\"matchCriteriaId\":\"7DE421BA-0600-4401-A175-73CAB6A6FB4E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"1759FFB7-531C-41B1-9AE1-FD3D80E0D920\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:rc7:*:*:*:*:*:*\",\"matchCriteriaId\":\"AD948719-8628-4421-A340-1066314BBD4A\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"8D465631-2980-487A-8E65-40AE2B9F8ED1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"4C9D071F-B28E-46EC-AC61-22B913390211\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/2577b202458cddff85cc154b1fe7f313e0d1f418\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/65dc4e3d5b01db0179fc95c1f0bdb87194c28ab5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/90574ecf6052be83971d91d16600c5cf07003bbb\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.