Audio jack detection hang via unreleased mutex
Published Apr 3, 2024 · Updated May 23, 2026
Deadlock in affected Linux kernel releases allows local users to hang audio jack detection by triggering the rt5645 work item twice. In sound/soc/codecs/rt5645.c, one return path in rt5645_jack_detect_work() reports jack state without unlocking jd_mutex, leaving later work blocked forever. Reachability requires local low-privilege access on a system using the rt5645 codec and its jack-detection path; the bounded impact is loss of jack-detection service.
Summary
What happened
Deadlock in affected Linux kernel releases allows local users to hang audio jack detection by triggering the rt5645 work item twice. In sound/soc/codecs/rt5645.c, one return path in rt5645_jack_detect_work() reports jack state without unlocking jd_mutex, leaving later work blocked forever. Reachability requires local low-privilege access on a system using the rt5645 codec and its jack-detection path; the bounded impact is loss of jack-detection service.
The record
- CVE
- CVE-2024-26722
- Published
- Apr 3, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1613195bf31e68b192bc731bea71726773e3482f <1f0d7792e9023e8658e901b7b76a555f6aa052ec
- Affected versionversion=4.19.306 <4.19.307
- Affected versionversion=48ce529c83522944f116f03884819051f44f0fb6 <3dd2d99e2352903d0e0b8769e6c9b8293c7454b2
- Affected versionversion=5.10.209 <5.10.210
- Affected versionversion=5.15.148 <5.15.149
- Affected versionversion=5.4.268 <5.4.269
- Affected versionversion=6.1.74 <6.1.79
- Affected versionversion=6.6.13 <6.6.18
- Affected versionversion=6.7
- Affected versionversion=7a3ff8a2bb2620ba6a806f0967c38be1a8d306d9 <d14b8e2005f36319df9412d42037416d64827f6b
- Affected versionversion=8f82f2e4d9c4966282e494ae67b0bc05a6c2b904 <050ad2ca0ac169dd9e552075d2c6af1bbb46534c
- Affected versionversion=b67005b284ddaf62043468d1ce5905c17d85b0e6 <422d5243b9f780abd3d39da2b746e3915677b07d
- Affected versionversion=cdba4301adda7c60a2064bf808e48fccd352aaa9 <6ef5d5b92f7117b324efaac72b3db27ae8bb3082
- Affected versionversion=cdba4301adda7c60a2064bf808e48fccd352aaa9 <ed5b8b735369b40d6c1f8ef3e62d369f74b4c491
- Affected versionversion=ffe13302b8fd486f80c98019bdcb7f3e512d0eda <4a98bc739d0753a5810ce5630943cd7614c7717e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo