Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53331slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl->lock

Description

In the Linux kernel, the following vulnerability has been resolved: slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl->lock During the SSR/PDR down notification the tx_lock is taken with the intent to provide synchronization with active DMA transfers. But during this period qcom_slim_ngd_down() is invoked, which ends up in slim_report_absent(), which takes the slim_controller lock. In multiple other codepaths these two locks are taken in the opposite order (i.e. slim_controller then tx_lock). The result is a lockdep splat, and a possible deadlock: rprocctl/449 is trying to acquire lock: ffff00009793e620 (&ctrl->lock){+.+.}-{4:4}, at: slim_report_absent (drivers/slimbus/core.c:322) slimbus but task is already holding lock: ffff00009793fb50 (&ctrl->tx_lock){+.+.}-{4:4}, at: qcom_slim_ngd_ssr_pdr_notify (drivers/slimbus/qcom-ngd-ctrl.c:1475) slim_qcom_ngd_ctrl which lock already depends on the new lock. Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ctrl->tx_lock); lock(&ctrl->lock); lock(&ctrl->tx_lock); lock(&ctrl->lock); The assumption is that the comment refers to the desire to not call qcom_slim_ngd_exit_dma() while we have an ongoing DMA TX transaction. But any such transaction is initiated and completed within a single qcom_slim_ngd_xfer_msg(). Prior to calling qcom_slim_ngd_exit_dma() the slim_controller is torn down, all child devices are notified that the slimbus is gone and the child devices are removed. Stop taking the tx_lock in qcom_slim_ngd_ssr_pdr_notify() to avoid the deadlock.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53331, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a899d324863a3d15ce0eea513884e1b73a758c58 – < 3d1561537237c6cc1db76155183d8bbdac2339f0
    • affected a899d324863a3d15ce0eea513884e1b73a758c58 – < dc4d5c57e012c2c669793deb1515a57bbc6bf5dd
    • affected a899d324863a3d15ce0eea513884e1b73a758c58 – < d54a221b0f3cd9e1f03f18104be34e02a8258fae
    • affected a899d324863a3d15ce0eea513884e1b73a758c58 – < aad4337a21b9ad3ae8d668fa8678d05e26ecbaa8
    • affected a899d324863a3d15ce0eea513884e1b73a758c58 – < 9f0d45d509b434c54da10e01f4ef8086e4583401
    • affected a899d324863a3d15ce0eea513884e1b73a758c58 – < 9708eb50fd7343145b422be852f890212155d845
    • affected a899d324863a3d15ce0eea513884e1b73a758c58 – < 55f2ea9ff83cc27a85526b14bc9b32f96a08d6ec
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53331 badge
[![CVE-2026-53331](https://cveledger.app/badge/CVE-2026-53331.svg)](https://cveledger.app/cve/CVE-2026-53331)

Record last updated .