We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

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]

Reserved 2024-12-29 | Published 2025-04-08 | Updated 2025-05-04 | Assigner Linux

Product status

Default status
unaffected

fbe639b44a82755d639df1c5d147c93f02ac5a0f before 72a222b6af10c2a05a5fad0029246229ed8912c2
affected

fbe639b44a82755d639df1c5d147c93f02ac5a0f before daba84612236de3ab39083e62c9e326a654ebd20
affected

fbe639b44a82755d639df1c5d147c93f02ac5a0f before 0a566a79aca9851fae140536e0fc5b0853c90a90
affected

fbe639b44a82755d639df1c5d147c93f02ac5a0f before f2bbfd50e95bc117360f0f59e629aa03d821ebd6
affected

fbe639b44a82755d639df1c5d147c93f02ac5a0f before f4489260f5713c94e1966e5f20445bff262876f4
affected

fbe639b44a82755d639df1c5d147c93f02ac5a0f before 02612f1e4c34d94d6c8ee75bf7d254ed697e22d4
affected

fbe639b44a82755d639df1c5d147c93f02ac5a0f before 2eeb03ad9f42dfece63051be2400af487ddb96d2
affected

Default status
affected

5.7
affected

Any version before 5.7
unaffected

5.10.236
unaffected

5.15.180
unaffected

6.1.132
unaffected

6.6.85
unaffected

6.12.21
unaffected

6.13.9
unaffected

6.14
unaffected

References

git.kernel.org/...c/72a222b6af10c2a05a5fad0029246229ed8912c2

git.kernel.org/...c/daba84612236de3ab39083e62c9e326a654ebd20

git.kernel.org/...c/0a566a79aca9851fae140536e0fc5b0853c90a90

git.kernel.org/...c/f2bbfd50e95bc117360f0f59e629aa03d821ebd6

git.kernel.org/...c/f4489260f5713c94e1966e5f20445bff262876f4

git.kernel.org/...c/02612f1e4c34d94d6c8ee75bf7d254ed697e22d4

git.kernel.org/...c/2eeb03ad9f42dfece63051be2400af487ddb96d2

cve.org (CVE-2025-22014)

nvd.nist.gov (CVE-2025-22014)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-22014

Support options

Helpdesk Chat, Email, Knowledgebase