ASoC: rt5645: Fix errorenous cleanup order
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: ASoC: rt5645: Fix errorenous cleanup order There is a logic error when removing rt5645 device as the function rt5645_i2c_remove() first cancel the &rt5645->jack_detect_work and delete the &rt5645->btn_check_timer latter. However, since the timer handler rt5645_btn_check_callback() will re-queue the jack_detect_work, this cleanup order is buggy. That is, once the del_timer_sync in rt5645_i2c_remove is concurrently run with the rt5645_btn_check_callback, the canceled jack_detect_work will be rescheduled again, leading to possible use-after-free. This patch fix the issue by placing the del_timer_sync function before the cancel_delayed_work_sync.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.13
References 8
git.kernel.org
- stable/c/236d29c5857f02e0a53fdf15d3dce1536c4322ce
- stable/c/0941150100173d4eaf3fe08ff4b16740e7c3026f
- stable/c/abe7554da62cb489712a54de69ef5665c250e564
- stable/c/1a5a3dfd9f172dcb115072f0aea5e27d3083c20e
- stable/c/061a6159cea583f1155f67d1915917a6b9282662
- stable/c/88c09e4812d72c3153afc8e5a45ecac2d0eae3ff
- stable/c/453f0920ffc1a28e28ddb9c3cd5562472b2895b0
- stable/c/2def44d3aec59e38d2701c568d65540783f90f2f