cbcvebase.
CVE-2025-22014
published 2025-04-08

CVE-2025-22014: 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()…

PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.15%
4.9th percentile
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]

Affected

25 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.133-1 (bookworm)linux 6.1.133-1 (bookworm)
debianlinux-6.1< linux 6.1.133-1 (bookworm)linux 6.1.133-1 (bookworm)
linuxlinux
linuxlinux>= fbe639b44a82755d639df1c5d147c93f02ac5a0f < 72a222b6af10c2a05a5fad0029246229ed8912c272a222b6af10c2a05a5fad0029246229ed8912c2
linuxlinux>= fbe639b44a82755d639df1c5d147c93f02ac5a0f < daba84612236de3ab39083e62c9e326a654ebd20daba84612236de3ab39083e62c9e326a654ebd20
linuxlinux>= fbe639b44a82755d639df1c5d147c93f02ac5a0f < 0a566a79aca9851fae140536e0fc5b0853c90a900a566a79aca9851fae140536e0fc5b0853c90a90
linuxlinux>= fbe639b44a82755d639df1c5d147c93f02ac5a0f < f2bbfd50e95bc117360f0f59e629aa03d821ebd6f2bbfd50e95bc117360f0f59e629aa03d821ebd6
linuxlinux>= fbe639b44a82755d639df1c5d147c93f02ac5a0f < f4489260f5713c94e1966e5f20445bff262876f4f4489260f5713c94e1966e5f20445bff262876f4
linuxlinux>= fbe639b44a82755d639df1c5d147c93f02ac5a0f < 02612f1e4c34d94d6c8ee75bf7d254ed697e22d402612f1e4c34d94d6c8ee75bf7d254ed697e22d4
linuxlinux>= fbe639b44a82755d639df1c5d147c93f02ac5a0f < 2eeb03ad9f42dfece63051be2400af487ddb96d22eeb03ad9f42dfece63051be2400af487ddb96d2
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.237-15.10.237-1
linuxlinux_kernel>= 0 < 6.1.133-16.1.133-1
linuxlinux_kernel>= 0 < 6.12.21-16.12.21-1
linuxlinux_kernel>= 0 < 6.12.21-16.12.21-1
linuxlinux_kernel>= 0 < 5.15.0-142.1525.15.0-142.152
linuxlinux_kernel>= 0 < 6.8.0-84.846.8.0-84.84
linuxlinux_kernel>= 5.7 < 6.1.1326.1.132
linuxlinux_kernel>= 6.13 < 6.13.96.13.9
linuxlinux_kernel>= 6.2 < 6.6.856.6.85
linuxlinux_kernel>= 6.7 < 6.12.216.12.21
msrcazl3_kernel_6.6.82.1-1_on_azure_linux_3.0
msrcazl3_kernel_6.6.85.1-2_on_azure_linux_3.0
msrccbl2_kernel_5.15.180.1-1_on_cbl_mariner_2.0
msrccbl2_kernel_5.15.182.1-1_on_cbl_mariner_2.0

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.