LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26722: ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work()

In the Linux kernel, the following vulnerability has been resolved: ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work() There is a path in rt5645_jack_detect_work(), where rt5645->jd_mutex is left locked forever. That may lead to deadlock when rt5645_jack_detect_work() is called for the second time. Found by Linux Verification Center (linuxtesting.org) with SVACE.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26722 is a Linux kernel driver bug in the Realtek RT5645 audio codec path. A mutex can remain locked after jack detection work runs, causing a later detection attempt to deadlock. The known business impact is availability or reliability disruption on systems using this driver, not confirmed data theft or remote compromise.

Executive priority

Treat as a targeted kernel availability issue. It should be handled through normal kernel patch management, with higher priority for devices where audio hardware reliability affects operations or where embedded Linux images are slow to update.

Technical view

The issue is in rt5645_jack_detect_work() in the Linux ASoC rt5645 driver. A control path leaves rt5645->jd_mutex locked, so a second call can deadlock. Linux stable commits are cited as the resolution. The source bundle provides no CVSS, CWE, exploit details, or complete downstream product mapping.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the rt5645 ASoC driver relevant to their hardware. The bundle lists Linux versions and stable commits, but exact affected-versus-fixed range interpretation is incomplete and should be validated against the running distribution kernel.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. The issue appears to require the vulnerable driver path to run, likely tied to local hardware or kernel event handling. No remote attack path is described in the provided evidence.

Researcher notes

Evidence supports a mutex-locking defect fixed upstream. There is no CVSS, CWE, proof of exploitation, or weaponized detail in the bundle. The affected version data appears non-obvious, so researchers should rely on upstream stable commits and distribution advisories for precise status.

Mitigation direction

  • Update to a kernel containing the cited Linux stable fix commits.
  • Check Debian LTS advisories if using Debian-packaged kernels.
  • Prioritize affected endpoint, embedded, or appliance fleets using RT5645 audio hardware.
  • If no vendor package is available, monitor vendor kernel guidance before changing kernels manually.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Check whether the rt5645 ASoC driver is present or loaded.
  • Map distribution kernel packages to the cited stable fixes or vendor advisories.
  • Review system logs for recurring audio jack detection or driver deadlock symptoms.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26722 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux48ce529c83522944f116f03884819051f44f0fb6, b67005b284ddaf62043468d1ce5905c17d85b0e6, ffe13302b8fd486f80c98019bdcb7f3e512d0eda, 7a3ff8a2bb2620ba6a806f0967c38be1a8d306d9, 1613195bf31e68b192bc731bea71726773e3482f, 8f82f2e4d9c4966282e494ae67b0bc05a6c2b904, cdba4301adda7c60a2064bf808e48fccd352aaa9, cdba4301adda7c60a2064bf808e48fccd352aaa9, 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.74, 6.6.13unaffected
LinuxLinux6.7, 0, 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.