soc: qcom: pdr: Fix the potential deadlock
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]
- Published
- Apr 8, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 5th percentile
- CWE
- CWE-667
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.7 and later · before 6.1.132
- linux linux kernel6.2 and later · before 6.6.85
- linux linux kernel6.7 and later · before 6.12.21
- linux linux kernel6.13 and later · before 6.13.9
- linux linux kernel6.14
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.7affected
- fbe639b44a82755d639df1c5d147c93f02ac5a0f and later · before 72a222b6af10c2a05a5fad0029246229ed8912c2affected · git
- fbe639b44a82755d639df1c5d147c93f02ac5a0f and later · before daba84612236de3ab39083e62c9e326a654ebd20affected · git
- fbe639b44a82755d639df1c5d147c93f02ac5a0f and later · before 0a566a79aca9851fae140536e0fc5b0853c90a90affected · git
- fbe639b44a82755d639df1c5d147c93f02ac5a0f and later · before f2bbfd50e95bc117360f0f59e629aa03d821ebd6affected · git
- fbe639b44a82755d639df1c5d147c93f02ac5a0f and later · before f4489260f5713c94e1966e5f20445bff262876f4affected · git
- fbe639b44a82755d639df1c5d147c93f02ac5a0f and later · before 02612f1e4c34d94d6c8ee75bf7d254ed697e22d4affected · git
- fbe639b44a82755d639df1c5d147c93f02ac5a0f and later · before 2eeb03ad9f42dfece63051be2400af487ddb96d2affected · git
- before 5.7not affected · semver
- 5.10.236 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.133-1 | 6.1.133-1 |
| Debian:13 | linux | before 6.12.21-1 | 6.12.21-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02612f1e4c34d94d6c8ee75bf7d254ed697e22d4 | Vendor (CNA) |
| Linux Linux | 0a566a79aca9851fae140536e0fc5b0853c90a90 | Vendor (CNA) |
| Linux Linux | 2eeb03ad9f42dfece63051be2400af487ddb96d2 | Vendor (CNA) |
| Linux Linux | 72a222b6af10c2a05a5fad0029246229ed8912c2 | Vendor (CNA) |
| Linux Linux | daba84612236de3ab39083e62c9e326a654ebd20 | Vendor (CNA) |
| Linux Linux | f2bbfd50e95bc117360f0f59e629aa03d821ebd6 | Vendor (CNA) |
| Linux Linux | f4489260f5713c94e1966e5f20445bff262876f4 | Vendor (CNA) |
| debian:linux | 6.1.133-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/02612f1e4c34d94d6c8ee75bf7d254ed697e22d4
- git.kernel.org/stable/c/0a566a79aca9851fae140536e0fc5b0853c90a90
- git.kernel.org/stable/c/2eeb03ad9f42dfece63051be2400af487ddb96d2
- git.kernel.org/stable/c/72a222b6af10c2a05a5fad0029246229ed8912c2
- git.kernel.org/stable/c/daba84612236de3ab39083e62c9e326a654ebd20
- git.kernel.org/stable/c/f2bbfd50e95bc117360f0f59e629aa03d821ebd6
- git.kernel.org/stable/c/f4489260f5713c94e1966e5f20445bff262876f4
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.