In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Fix opregion leak
Being part o the display, ideally the setup and cleanup would be done by display itself. However this is a bigger refactor that needs to be done on both i915 and xe. For now, just fix the leak:
unreferenced object 0xffff8881a0300008 (size 192): comm "modprobe", pid 4354, jiffies 4295647021 hex dump (first 32 bytes): 00 00 87 27 81 88 ff ff 18 80 9b 00 00 c9 ff ff ...'............ 18 81 9b 00 00 c9 ff ff 00 00 00 00 00 00 00 00 ................ backtrace (crc 99260e31): [<ffffffff823ce65b>] kmemleakalloc+0x4b/0x80 [<ffffffff81493be2>] kmalloctracenoprof+0x312/0x3d0 [<ffffffffa1345679>] intelopregionsetup+0x89/0x700 [xe] [<ffffffffa125bfaf>] xedisplayinitnoirq+0x2f/0x90 [xe] [<ffffffffa1199ec3>] xedeviceprobe+0x7a3/0xbf0 [xe] [<ffffffffa11f3713>] xepciprobe+0x333/0x5b0 [xe] [<ffffffff81af6be8>] localpciprobe+0x48/0xb0 [<ffffffff81af8778>] pcideviceprobe+0xc8/0x280 [<ffffffff81d09048>] reallyprobe+0xf8/0x390 [<ffffffff81d0937a>] _driverprobedevice+0x8a/0x170 [<ffffffff81d09503>] driverprobedevice+0x23/0xb0 [<ffffffff81d097b7>] _driverattach+0xc7/0x190 [<ffffffff81d0628d>] busforeachdev+0x7d/0xd0 [<ffffffff81d0851e>] driverattach+0x1e/0x30 [<ffffffff81d07ac7>] busadddriver+0x117/0x250
(cherry picked from commit 6f4e43a2f771b737d991142ec4f6d4b7ff31fbb4)