usb: storage: realtek_cr: fix use-after-free on disconnect
- 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
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.51, 7.2.5
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: storage: realtek_cr: fix use-after-free on disconnect realtek_cr_destructor() calls timer_delete() before the chip containing the timer is freed. The timer callback may still be running and can rearm itself, resulting in a use-after-free. Use timer_shutdown_sync() to wait for the callback and prevent further rearming. Do this unconditionally because ss_en may be changed after the timer is armed. Move timer_setup() into init_realtek_cr() so the timer is initialized before any failure path can invoke the destructor. Found by static analysis.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From e931830bb877e2aad9a1be83506f9bdb26c91e4e · fixed in c1e7e35100efffba7c9e1dfa76519d6cd323ba3d; From e931830bb877e2aad9a1be83506f9bdb26c91e4e · fixed in 524d4257f741cd95eb85e2817c9c890928fcfef7; From e931830bb877e2aad9a1be83506f9bdb26c91e4e · fixed in 7c4e2f964c65dea4ea22386799d5fb10ef1e3e54; From e931830bb877e2aad9a1be83506f9bdb26c91e4e · fixed in cae9dbba6adae21a04a3bd045e07b489847ff2c6; From e931830bb877e2aad9a1be83506f9bdb26c91e4e · fixed in 4ffee1aebb0c0ffcda9faffd17834ea9b00d42cc
- Linux Linux
3.1
- KernelLinux
From 3.1.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5