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)
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/7cdb9a9da935c687563cc682155461fef5f9b48d Patch
- https://git.kernel.org/stable/c/c6d30b65b7a44dac52ad49513268adbf19eab4a2 Patch
- https://git.kernel.org/stable/c/dcb171931954c51a1a7250d558f02b8f36570783 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.8 · linuxNVD modified 2026-10-16 15:16
Affected (CPE criteria) 10
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*