CVE-2024-46691usb: typec: ucsi: Move unregister out of atomic section
- 5.5MediumCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: Move unregister out of atomic section Commit '9329933699b3 ("soc: qcom: pmic_glink: Make client-lock non-sleeping")' moved the pmic_glink client list under a spinlock, as it is accessed by the rpmsg/glink callback, which in turn is invoked from IRQ context. This means that ucsi_unregister() is now called from atomic context, which isn't feasible as it's expecting a sleepable context. An effort is under way to get GLINK to invoke its callbacks in a sleepable context, but until then lets schedule the unregistration. A side effect of this is that ucsi_unregister() can now happen after the remote processor, and thereby the communication link with it, is gone. pmic_glink_send() is amended with a check to avoid the resulting NULL pointer dereference. This does however result in the user being informed about this error by the following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
Timeline
ID reserved
By Linux
- 2 days later
· 2 days later
Published
- 21 months later
· 21 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected fbadcde1572f6b00e1e343d8b24ec8bf7f3ec08d – < 1e3769aa0946c2b6e509c06d7a0aa9b955eaef9e
- affected 9329933699b32d467a99befa20415c4b2172389a – < 095b0001aefddcd9361097c971b7debc84e72714
- affected 9329933699b32d467a99befa20415c4b2172389a – < 11bb2ffb679399f99041540cf662409905179e3a
- affected 8d62ab7d89a4906385ea8c11a4b2475578bec0f0
- affected bd54d7c8e76d235b4a70be3a545eb13f5ac531e4
- affected 6.6.33 – < 6.6.130
- affected 6.8.12 – < 6.9
- affected 6.9.3 – < 6.10
- affected 6.10
- unaffected < 6.10
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.10.8 – ≤ 6.10.*
- unaffected 6.11 – ≤ *
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-41952 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-46691)Record last updated .