Skip to content
Heist/ feed
Back to feed
UnratedFix available

i2c: designware: amdisp: Fix resume-probe race condition issue

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: i2c: designware: amdisp: Fix resume-probe race condition issue Identified resume-probe race condition in kernel v7.0 with the commit 38fa29b01a6a ("i2c: designware: Combine the init functions"),but this issue existed from the beginning though not detected. The amdisp i2c device requires ISP to be in power-on state for probe to succeed. To meet this requirement, this device is added to genpd to control ISP power using runtime PM. The pm_runtime_get_sync() called before i2c_dw_probe() triggers PM resume, which powers on ISP and also invokes the amdisp i2c runtime resume before the probe completes resulting in this race condition and a NULL dereferencing issue in v7.0 Fix this race condition by using the genpd APIs directly during probe: - Call dev_pm_genpd_resume() to Power ON ISP before probe - Call dev_pm_genpd_suspend() to Power OFF ISP after probe - Set the device to suspended state with pm_runtime_set_suspended() - Enable runtime PM only after the device is fully initialized

Products
Kernel
Affected versions
Not specified
Fixed versions
6.18.21, 6.19.11
CVEs
CVE-2026-31572
Confirmed fixed CVEs
Not specified
Updated in this feed
2 Nov 2026, 16:12 UTC · Revision 1

Source evidence

i2c: designware: amdisp: Fix resume-probe race condition issue

core-osv · Original source

Published 24 Apr 2026, 14:35 UTC

In the Linux kernel, the following vulnerability has been resolved: i2c: designware: amdisp: Fix resume-probe race condition issue Identified resume-probe race condition in kernel v7.0 with the commit 38fa29b01a6a ("i2c: designware: Combine the init functions"),but this issue existed from the beginning though not detected. The amdisp i2c device requires ISP to be in power-on state for probe to succeed. To meet this requirement, this device is added to genpd to control ISP power using runtime PM. The pm_runtime_get_sync() called before i2c_dw_probe() triggers PM resume, which powers on ISP and also invokes the amdisp i2c runtime resume before the probe completes resulting in this race condition and a NULL dereferencing issue in v7.0 Fix this race condition by using the genpd APIs directly during probe: - Call dev_pm_genpd_resume() to Power ON ISP before probe - Call dev_pm_genpd_suspend() to Power OFF ISP after probe - Set the device to suspended state with pm_runtime_set_suspended() - Enable runtime PM only after the device is fully initialized

osv:CVE-2026-31572

Kernel

Fixed versions: 6.18.21, 6.19.11

Complete source record
{
  "id": "d8f8faed92d80362265f8d62edf77e68df4e1fe752ae095f1aed2020d7745abd",
  "url": "https://osv.dev/vulnerability/CVE-2026-31572",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "i2c: designware: amdisp: Fix resume-probe race condition issue",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: i2c: designware: amdisp: Fix resume-probe race condition issue Identified resume-probe race condition in kernel v7.0 with the commit 38fa29b01a6a (\"i2c: designware: Combine the init functions\"),but this issue existed from the beginning though not detected. The amdisp i2c device requires ISP to be in power-on state for probe to succeed. To meet this requirement, this device is added to genpd to control ISP power using runtime PM. The pm_runtime_get_sync() called before i2c_dw_probe() triggers PM resume, which powers on ISP and also invokes the amdisp i2c runtime resume before the probe completes resulting in this race condition and a NULL dereferencing issue in v7.0 Fix this race condition by using the genpd APIs directly during probe: - Call dev_pm_genpd_resume() to Power ON ISP before probe - Call dev_pm_genpd_suspend() to Power OFF ISP after probe - Set the device to suspended state with pm_runtime_set_suspended() - Enable runtime PM only after the device is fully initialized",
    "evidence": "osv:CVE-2026-31572",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.21",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.11",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-31572",
      "aliases": [
        "CVE-2026-31572"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "d6263c468a761cd4c89887073614394ac48441e1"
                },
                {
                  "fixed": "83bcea9da91965484df64a6492b89e65d41ab31c"
                },
                {
                  "fixed": "e81f0341754c309e33babea2821eda8f98f0b44c"
                },
                {
                  "fixed": "e2f1ada8e089dd5a331bcd8b88125ae2af8d188f"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31572.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.16.0"
                },
                {
                  "fixed": "6.18.21"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.11"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31572.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:21.256627397Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/83bcea9da91965484df64a6492b89e65d41ab31c",
        "https://git.kernel.org/stable/c/e2f1ada8e089dd5a331bcd8b88125ae2af8d188f",
        "https://git.kernel.org/stable/c/e81f0341754c309e33babea2821eda8f98f0b44c",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31572.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-31572",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31572.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-31572",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 486974,
  "published_at": "2026-04-24T14:35:50.736+00:00"
}