CVE-2022-50144
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2022-50144
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-50144.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2022-50144
- Downstream
- Related
- Published
- 2025-06-18T11:03:05Z
- Modified
- 2025-10-16T07:40:52.069038Z
- Summary
- soundwire: revisit driver bind/unbind and callbacks
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
soundwire: revisit driver bind/unbind and callbacks
In the SoundWire probe, we store a pointer from the driver ops into the 'slave' structure. This can lead to kernel oopses when unbinding codec drivers, e.g. with the following sequence to remove machine driver and codec driver.
/sbin/modprobe -r sndsocsofsdw /sbin/modprobe -r sndsoc_rt711
The full details can be found in the BugLink below, for reference the two following examples show different cases of driver ops/callbacks being invoked after the driver .remove().
kernel: BUG: kernel NULL pointer dereference, address: 0000000000000150 kernel: Workqueue: events cdnsupdateslavestatuswork [soundwirecadence] kernel: RIP: 0010:mutexlock+0x19/0x30 kernel: Call Trace: kernel: ? sdwhandleslavestatus+0x426/0xe00 [soundwirebus 94ff184bf398570c3f8ff7efe9e32529f532e4ae] kernel: ? newidlebalance+0x26a/0x400 kernel: ? cdnsupdateslavestatuswork+0x1e9/0x200 [soundwirecadence 1bcf98eebe5ba9833cd433323769ac923c9c6f82]
kernel: BUG: unable to handle page fault for address: ffffffffc07654c8 kernel: Workqueue: pm pmruntimework kernel: RIP: 0010:sdwbusprepclkstop+0x6f/0x160 [soundwirebus] kernel: Call Trace: kernel: <TASK> kernel: sdwcdnsclockstop+0xb5/0x1b0 [soundwirecadence 1bcf98eebe5ba9833cd433323769ac923c9c6f82] kernel: intelsuspendruntime+0x5f/0x120 [soundwireintel aca858f7c87048d3152a4a41bb68abb9b663a1dd] kernel: ? dpmsysfsremove+0x60/0x60
This was not detected earlier in Intel tests since the tests first remove the parent PCI device and shut down the bus. The sequence above is a corner case which keeps the bus operational but without a driver bound.
While trying to solve this kernel oopses, it became clear that the existing SoundWire bus does not deal well with the unbind case.
Commit 528be501b7d4a ("soundwire: sdwslave: add probecomplete structure and new fields") added a 'probed' status variable and a 'probecomplete' struct completion. This status is however not reset on remove and likewise the 'probe complete' is not re-initialized, so the bind/unbind/bind test cases would fail. The timeout used before the 'updatestatus' callback was also a bad idea in hindsight, there should really be no timing assumption as to if and when a driver is bound to a device.
An initial draft was based on devicelock() and deviceunlock() was tested. This proved too complicated, with deadlocks created during the suspend-resume sequences, which also use the same devicelock/unlock() as the bind/unbind sequences. On a CometLake device, a bad DSDT/BIOS caused spurious resumes and the use of devicelock() caused hangs during suspend. After multiple weeks or testing and painful reverse-engineering of deadlocks on different devices, we looked for alternatives that did not interfere with the device core.
A bus notifier was used successfully to keep track of DRIVERBOUND and DRIVERUNBIND events. This solved the bind-unbind-bind case in tests, but it can still be defeated with a theoretical corner case where the memory is freed by a .remove while the callback is in use. The notifier only helps make sure the driver callbacks are valid, but not that the memory allocated in probe remains valid while the callbacks are invoked.
This patch suggests the introduction of a new 'sdwdevlock' mutex protecting probe/remove and all driver callbacks. Since this mutex is 'local' to SoundWire only, it does not interfere with existing locks and does not create deadlocks. In addition, this patch removes the 'probecomplete' completion, instead we directly invoke the 'updatestatus' from the probe routine. That removes any sort of timing dependency and a much better support for the device/driver model, the driver could be bound before the bus started, or eons after the bus started and the hardware would be properly initialized in all cases.
BugLink: https://github.com/thesofproject/linux/is ---truncated---
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/250b46505175889c6b5958c3829f610f52199f5f
- https://git.kernel.org/stable/c/432b30f08ca3303d2ebb22352cb04c4b6cfefe65
- https://git.kernel.org/stable/c/8fd6b03646b9a9e16d1ec19bd724cd6bd78e0ea5
- https://git.kernel.org/stable/c/bd29c00edd0a5dac8b6e7332bb470cd50f92e893
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced56d4fe31af77f684bed62fb8201e6327e6ddf4e6Fixed250b46505175889c6b5958c3829f610f52199f5f
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced56d4fe31af77f684bed62fb8201e6327e6ddf4e6Fixed8fd6b03646b9a9e16d1ec19bd724cd6bd78e0ea5
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced56d4fe31af77f684bed62fb8201e6327e6ddf4e6Fixed432b30f08ca3303d2ebb22352cb04c4b6cfefe65
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced56d4fe31af77f684bed62fb8201e6327e6ddf4e6Fixedbd29c00edd0a5dac8b6e7332bb470cd50f92e893