drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()
- 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.12.64, 6.18.4
- 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: 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)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 · fixed in c6d30b65b7a44dac52ad49513268adbf19eab4a2; From cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 · fixed in 7cdb9a9da935c687563cc682155461fef5f9b48d; From cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 · fixed in dcb171931954c51a1a7250d558f02b8f36570783
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.64; From 6.13.0 · fixed in 6.18.4