drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7cdb9a9da935c687563cc682155461fef5f9b48d, Kernel c6d30b65b7a44dac52ad49513268adbf19eab4a2 and Kernel dcb171931954c51a1a7250d558f02b8f36570783.
In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl() In xe_oa_add_config_ioctl(), we accessed oa_config->id after dropping metrics_lock. Since this lock protects the lifetime of oa_config, an attacker could guess the id and call xe_oa_remove_config_ioctl() with perfect timing, freeing oa_config before we dereference it, leading to a potential use-after-free. Fix this by caching the id in a local variable while holding the lock. v2: (Matt A) - Dropped mutex_unlock(&oa->metrics_lock) ordering change from xe_oa_remove_config_ioctl() (cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.11, >=cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 <7cdb9a9da935c687563cc682155461fef5f9b48d, >=cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 <c6d30b65b7a44dac52ad49513268adbf19eab4a2, >=cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 <dcb171931954c51a1a7250d558f02b8f36570783 | 7cdb9a9da935c687563cc682155461fef5f9b48d, c6d30b65b7a44dac52ad49513268adbf19eab4a2, dcb171931954c51a1a7250d558f02b8f36570783 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket