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

CVE-2025-22014

soc: qcom: pdr: Fix the potential deadlock

Description

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: pdr: Fix the potential deadlock When some client process A call pdr_add_lookup() to add the look up for the service and does schedule locator work, later a process B got a new server packet indicating locator is up and call pdr_locator_new_server() which eventually sets pdr->locator_init_complete to true which process A sees and takes list lock and queries domain list but it will timeout due to deadlock as the response will queued to the same qmi->wq and it is ordered workqueue and process B is not able to complete new server request work due to deadlock on list lock. Fix it by removing the unnecessary list iteration as the list iteration is already being done inside locator work, so avoid it here and just call schedule_work() here. Process A Process B process_scheduled_works() pdr_add_lookup() qmi_data_ready_work() process_scheduled_works() pdr_locator_new_server() pdr->locator_init_complete=true; pdr_locator_work() mutex_lock(&pdr->list_lock); pdr_locate_service() mutex_lock(&pdr->list_lock); pdr_get_domain_list() pr_err("PDR: %s get domain list txn wait failed: %d\n", req->service_name, ret); Timeout error log due to deadlock: " PDR: tms/servreg get domain list txn wait failed: -110 PDR: service lookup for msm/adsp/sensor_pd:tms/servreg failed: -110 " Thanks to Bjorn and Johan for letting me know that this commit also fixes an audio regression when using the in-kernel pd-mapper as that makes it easier to hit this race. [1]

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 13 months later

    Record updated

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-2025-22014, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.19% · top 92% of all CVEs (10 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 fbe639b44a82755d639df1c5d147c93f02ac5a0f – < 72a222b6af10c2a05a5fad0029246229ed8912c2
    • affected fbe639b44a82755d639df1c5d147c93f02ac5a0f – < daba84612236de3ab39083e62c9e326a654ebd20
    • affected fbe639b44a82755d639df1c5d147c93f02ac5a0f – < 0a566a79aca9851fae140536e0fc5b0853c90a90
    • affected fbe639b44a82755d639df1c5d147c93f02ac5a0f – < f2bbfd50e95bc117360f0f59e629aa03d821ebd6
    • affected fbe639b44a82755d639df1c5d147c93f02ac5a0f – < f4489260f5713c94e1966e5f20445bff262876f4
    • affected fbe639b44a82755d639df1c5d147c93f02ac5a0f – < 02612f1e4c34d94d6c8ee75bf7d254ed697e22d4
    • affected fbe639b44a82755d639df1c5d147c93f02ac5a0f – < 2eeb03ad9f42dfece63051be2400af487ddb96d2
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.236 – ≤ 5.10.*
    • unaffected 5.15.180 – ≤ 5.15.*
    • unaffected 6.1.132 – ≤ 6.1.*
    • unaffected 6.6.85 – ≤ 6.6.*
    • unaffected 6.12.21 – ≤ 6.12.*
    • unaffected 6.13.9 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

9

Sources

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

Badge for a README or a ticket

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

Record last updated .