CWE
667
Advisory Published
Updated

CVE-2025-22014: soc: qcom: pdr: Fix the potential deadlock

First published: Tue Apr 08 2025(Updated: )

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]

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel
Linux Kernel>=5.7<6.1.132
Linux Kernel>=6.2<6.6.85
Linux Kernel>=6.7<6.12.21
Linux Kernel>=6.13<6.13.9
Linux Kernel=6.14-rc1
Linux Kernel=6.14-rc2
Linux Kernel=6.14-rc3
Linux Kernel=6.14-rc4
Linux Kernel=6.14-rc5
Linux Kernel=6.14-rc6
Linux Kernel=6.14-rc7

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2025-22014?

    CVE-2025-22014 has been classified with a high severity rating due to the potential for deadlock in the Linux kernel.

  • How do I fix CVE-2025-22014?

    To fix CVE-2025-22014, you should update your Linux kernel to the latest patched version provided by your distribution.

  • What systems are affected by CVE-2025-22014?

    CVE-2025-22014 affects systems running the Linux kernel that utilize the qcom pdr functionality.

  • What impact does CVE-2025-22014 have?

    CVE-2025-22014 can lead to system instability and potential deadlock issues affecting service lookup processes.

  • Where can I find more information about CVE-2025-22014?

    More information about CVE-2025-22014 can typically be found in security advisories from your Linux distribution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203