rpmsg: core: fix race in driver_override_show() and use core helper
- 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 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, and 2 more
- 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: rpmsg: core: fix race in driver_override_show() and use core helper The driver_override_show function reads the driver_override string without holding the device_lock. However, the store function modifies and frees the string while holding the device_lock. This creates a race condition where the string can be freed by the store function while being read by the show function, leading to a use-after-free. To fix this, replace the rpmsg_string_attr macro with explicit show and store functions. The new driver_override_store uses the standard driver_set_override helper. Since the introduction of driver_set_override, the comments in include/linux/rpmsg.h have stated that this helper must be used to set or clear driver_override, but the implementation was not updated until now. Because driver_set_override modifies and frees the string while holding the device_lock, the new driver_override_show now correctly holds the device_lock during the read operation to prevent the race. Additionally, since rpmsg_string_attr has only ever been used for driver_override, removing the macro simplifies the code.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in 392c6b68334aa0e0ae9aba95c0a366bcb0d92f5d; From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in d66b8074c555e8abb0ae19eea1c9f3635498bdde; From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in 47615557447185917afa432b7958f87583c417cb; From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in 90c8353f471821d7ccd4fe573a2402e056192494; From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in 7654e6e3cd6bdee9602f6063b3c670bd556d7e61; From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in 2e4a70f3c30910427e5ea848b799066d67b963d5; From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in 954557957177c3c13d7c655976665b1170da5e50; From 39e47767ec9b22f844c2a07c9d329256960d4021 · fixed in 42023d4b6d2661a40ee2dcf7e1a3528a35c638ca
- Linux Linux
4.18
- KernelLinux
From 4.18.0 · fixed in 5.10.252; From 5.11.0 · fixed in 5.15.202; From 5.16.0 · fixed in 6.1.165; From 6.2.0 · fixed in 6.6.128; From 6.7.0 · fixed in 6.12.75; From 6.13.0 · fixed in 6.18.16; From 6.19.0 · fixed in 6.19.6
References 8
git.kernel.org
- stable/c/392c6b68334aa0e0ae9aba95c0a366bcb0d92f5d
- stable/c/d66b8074c555e8abb0ae19eea1c9f3635498bdde
- stable/c/47615557447185917afa432b7958f87583c417cb
- stable/c/90c8353f471821d7ccd4fe573a2402e056192494
- stable/c/7654e6e3cd6bdee9602f6063b3c670bd556d7e61
- stable/c/2e4a70f3c30910427e5ea848b799066d67b963d5
- stable/c/954557957177c3c13d7c655976665b1170da5e50
- stable/c/42023d4b6d2661a40ee2dcf7e1a3528a35c638ca