CVE-2026-90193 (GCVE-0-2026-90193)

Vulnerability from cvelistv5 – Published: 2026-09-17 16:07 – Updated: 2026-10-19 08:59
VLAI
Title
mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler
Summary
In the Linux kernel, the following vulnerability has been resolved: mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler qcom_cpucp_mbox_irq_fn() calls mbox_chan_received_data() while holding chan->lock. Under PREEMPT_RT, spin_lock_irqsave() is converted to an rt_spinlock (rtmutex-based), which tracks ownership and can sleep. The callback chain triggered by mbox_chan_received_data() eventually reaches mailbox_clear_channel() -> mbox_send_message() -> add_to_rbuf(), which attempts to re-acquire the same chan->lock. Since rtmutex detects the re-entrant lock attempt by the same owner, the thread blocks waiting for a lock it already holds, causing a permanent deadlock. This deadlock manifests as 'irq/N-apss_cpucp_mbox' stuck in D state with the following call trace: rt_spin_lock -> mbox_send_message -> mailbox_clear_channel -> scmi_rx_callback -> mbox_chan_received_data [<- held chan->lock here] Fix by saving chan->cl locally and clearing the HW interrupt register inside the lock, then invoking mbox_chan_received_data() after releasing the lock. This preserves the mutual exclusion for chan->cl access while avoiding the lock re-entrancy that causes the PREEMPT_RT deadlock.
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6649 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 , < aa482273f32117c3adeba9b1cc945e0b5d33722d (git)
Affected: 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 , < 8b8de6400c86937ed57d680d06d716e167b381de (git)
Affected: 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 , < e40b3edeaf25cd09e9c88edb1ef99373ca37593b (git)
Affected: 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 , < 3690aaa6d18f6775c3e7932fb8af8c5bf6a6b69c (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.11
Unaffected: 0 , < 6.11 (semver)
Unaffected: 6.12.110 , ≤ 6.12.* (semver)
Unaffected: 6.18.52 , ≤ 6.18.* (semver)
Unaffected: 7.2.6 , ≤ 7.2.* (semver)
Unaffected: 7.3 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/mailbox/qcom-cpucp-mbox.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "aa482273f32117c3adeba9b1cc945e0b5d33722d",
              "status": "affected",
              "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
              "versionType": "git"
            },
            {
              "lessThan": "8b8de6400c86937ed57d680d06d716e167b381de",
              "status": "affected",
              "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
              "versionType": "git"
            },
            {
              "lessThan": "e40b3edeaf25cd09e9c88edb1ef99373ca37593b",
              "status": "affected",
              "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
              "versionType": "git"
            },
            {
              "lessThan": "3690aaa6d18f6775c3e7932fb8af8c5bf6a6b69c",
              "status": "affected",
              "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/mailbox/qcom-cpucp-mbox.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.11"
            },
            {
              "lessThan": "6.11",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.52",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.110",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.52",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.6",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler\n\nqcom_cpucp_mbox_irq_fn() calls mbox_chan_received_data() while holding\nchan-\u003elock. Under PREEMPT_RT, spin_lock_irqsave() is converted to an\nrt_spinlock (rtmutex-based), which tracks ownership and can sleep.\n\nThe callback chain triggered by mbox_chan_received_data() eventually\nreaches mailbox_clear_channel() -\u003e mbox_send_message() -\u003e add_to_rbuf(),\nwhich attempts to re-acquire the same chan-\u003elock. Since rtmutex detects\nthe re-entrant lock attempt by the same owner, the thread blocks waiting\nfor a lock it already holds, causing a permanent deadlock.\n\nThis deadlock manifests as \u0027irq/N-apss_cpucp_mbox\u0027 stuck in D state\nwith the following call trace:\n  rt_spin_lock -\u003e mbox_send_message -\u003e mailbox_clear_channel -\u003e\n  scmi_rx_callback -\u003e mbox_chan_received_data [\u003c- held chan-\u003elock here]\n\nFix by saving chan-\u003ecl locally and clearing the HW interrupt register\ninside the lock, then invoking mbox_chan_received_data() after releasing\nthe lock. This preserves the mutual exclusion for chan-\u003ecl access while\navoiding the lock re-entrancy that causes the PREEMPT_RT deadlock."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:59:29.783Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/aa482273f32117c3adeba9b1cc945e0b5d33722d"
        },
        {
          "url": "https://git.kernel.org/stable/c/8b8de6400c86937ed57d680d06d716e167b381de"
        },
        {
          "url": "https://git.kernel.org/stable/c/e40b3edeaf25cd09e9c88edb1ef99373ca37593b"
        },
        {
          "url": "https://git.kernel.org/stable/c/3690aaa6d18f6775c3e7932fb8af8c5bf6a6b69c"
        }
      ],
      "title": "mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90193",
    "datePublished": "2026-09-17T16:07:13.672Z",
    "dateReserved": "2026-09-11T19:38:34.792Z",
    "dateUpdated": "2026-10-19T08:59:29.783Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-90193",
      "date": "2026-11-04",
      "epss": "0.00209",
      "percentile": "0.11127"
    },
    "microsoft_vex": {
      "current_release_date": "2026-10-21T18:34:17.000Z",
      "cve": "CVE-2026-90193",
      "id": "msrc_CVE-2026-90193",
      "initial_release_date": "2026-10-20T22:21:54.000Z",
      "product_status:under_investigation": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-90193.json",
      "version": "2"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "drivers/mailbox/qcom-cpucp-mbox.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "aa482273f32117c3adeba9b1cc945e0b5d33722d",
                    "status": "affected",
                    "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "8b8de6400c86937ed57d680d06d716e167b381de",
                    "status": "affected",
                    "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "e40b3edeaf25cd09e9c88edb1ef99373ca37593b",
                    "status": "affected",
                    "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "3690aaa6d18f6775c3e7932fb8af8c5bf6a6b69c",
                    "status": "affected",
                    "version": "0e2a9a03106cd5fa0dbc9047675e7645c55e2669",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "drivers/mailbox/qcom-cpucp-mbox.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.11"
                  },
                  {
                    "lessThan": "6.11",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.12.*",
                    "status": "unaffected",
                    "version": "6.12.110",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.18.*",
                    "status": "unaffected",
                    "version": "6.18.52",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.2.*",
                    "status": "unaffected",
                    "version": "7.2.6",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.3",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler\n\nqcom_cpucp_mbox_irq_fn() calls mbox_chan_received_data() while holding\nchan-\u003elock. Under PREEMPT_RT, spin_lock_irqsave() is converted to an\nrt_spinlock (rtmutex-based), which tracks ownership and can sleep.\n\nThe callback chain triggered by mbox_chan_received_data() eventually\nreaches mailbox_clear_channel() -\u003e mbox_send_message() -\u003e add_to_rbuf(),\nwhich attempts to re-acquire the same chan-\u003elock. Since rtmutex detects\nthe re-entrant lock attempt by the same owner, the thread blocks waiting\nfor a lock it already holds, causing a permanent deadlock.\n\nThis deadlock manifests as \u0027irq/N-apss_cpucp_mbox\u0027 stuck in D state\nwith the following call trace:\n  rt_spin_lock -\u003e mbox_send_message -\u003e mailbox_clear_channel -\u003e\n  scmi_rx_callback -\u003e mbox_chan_received_data [\u003c- held chan-\u003elock here]\n\nFix by saving chan-\u003ecl locally and clearing the HW interrupt register\ninside the lock, then invoking mbox_chan_received_data() after releasing\nthe lock. This preserves the mutual exclusion for chan-\u003ecl access while\navoiding the lock re-entrancy that causes the PREEMPT_RT deadlock."
          }
        ],
        "id": "CVE-2026-90193",
        "lastModified": "2026-10-19T09:19:09.310",
        "metrics": {},
        "published": "2026-09-17T17:17:14.030",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/3690aaa6d18f6775c3e7932fb8af8c5bf6a6b69c"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/8b8de6400c86937ed57d680d06d716e167b381de"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/aa482273f32117c3adeba9b1cc945e0b5d33722d"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/e40b3edeaf25cd09e9c88edb1ef99373ca37593b"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-10-13T14:37:30+00:00",
      "cve": "CVE-2026-90193",
      "id": "CVE-2026-90193",
      "initial_release_date": "2026-09-17T00:00:00+00:00",
      "product_status:known_not_affected": "277",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-90193.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-10-20T00:43:52Z",
      "cve": "CVE-2026-90193",
      "id": "CVE-2026-90193",
      "initial_release_date": "2026-09-18T00:20:10Z",
      "product_status:known_affected": "0",
      "product_status:known_not_affected": "348",
      "product_status:recommended": "4",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-90193",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-90193.json",
      "version": "5"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.