i2c: designware: Fix handling of real but unexpected device interrupts

{
  "id": "a9a7275316d1ebfe234fd1aa16bb971721bbe34af1588547e504033ed21ba953",
  "url": "https://osv.dev/vulnerability/CVE-2022-50370",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "i2c: designware: Fix handling of real but unexpected device interrupts",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: i2c: designware: Fix handling of real but unexpected device interrupts Commit c7b79a752871 (\"mfd: intel-lpss: Add Intel Alder Lake PCH-S PCI IDs\") caused a regression on certain Gigabyte motherboards for Intel Alder Lake-S where system crashes to NULL pointer dereference in i2c_dw_xfer_msg() when system resumes from S3 sleep state (\"deep\"). I was able to debug the issue on Gigabyte Z690 AORUS ELITE and made following notes: - Issue happens when resuming from S3 but not when resuming from \"s2idle\" - PCI device 00:15.0 == i2c_designware.0 is already in D0 state when system enters into pci_pm_resume_noirq() while all other i2c_designware PCI devices are in D3. Devices were runtime suspended and in D3 prior entering into suspend - Interrupt comes after pci_pm_resume_noirq() when device interrupts are re-enabled - According to register dump the interrupt really comes from the i2c_designware.0. Controller is enabled, I2C target address register points to a one detectable I2C device address 0x60 and the DW_IC_RAW_INTR_STAT register START_DET, STOP_DET, ACTIVITY and TX_EMPTY bits are set indicating completed I2C transaction. My guess is that the firmware uses this controller to communicate with an on-board I2C device during resume but does not disable the controller before giving control to an operating system. I was told the UEFI update fixes this but never the less it revealed the driver is not ready to handle TX_E",
    "evidence": "osv:CVE-2022-50370",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.15.75",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.19.17",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.0.3",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "CVE-2022-50370",
      "aliases": [
        "CVE-2022-50370"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "c7b79a75287141cef5bbaeaf1c942269c08cd52e"
                },
                {
                  "fixed": "7fa5304c4b5b425d4a0b3acf10139a7f6108a85f"
                },
                {
                  "fixed": "a206f7fbe9589c60fafad12884628c909ecb042f"
                },
                {
                  "fixed": "aa59ac81e859006d3a1df035a19b3f2089110f93"
                },
                {
                  "fixed": "301c8f5c32c8fb79c67539bc23972dc3ef48024c"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50370.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.12.0"
                },
                {
                  "fixed": "5.15.75"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "5.19.17"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.20.0"
                },
                {
                  "fixed": "6.0.3"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50370.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:23.800183245Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/301c8f5c32c8fb79c67539bc23972dc3ef48024c",
        "https://git.kernel.org/stable/c/7fa5304c4b5b425d4a0b3acf10139a7f6108a85f",
        "https://git.kernel.org/stable/c/a206f7fbe9589c60fafad12884628c909ecb042f",
        "https://git.kernel.org/stable/c/aa59ac81e859006d3a1df035a19b3f2089110f93",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50370.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-50370",
        "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/2022/50xxx/CVE-2022-50370.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-50370",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 489877,
  "published_at": "2025-09-17T14:56:26.015+00:00"
}