Thomas Hellström

A potential deadlock issue has been identified in the Linux kernel. The problem occurs when the sysfs ->store() function is called while a queue is frozen, and memory allocation with GFP KERNEL is attempted, which may lead to a direct reclaim code path and cause a deadlock. This issue is related to the block layer and involves several ->store() callbacks, including update nr requests, wbt, and scheduler.

A potential use-after-free (UAF) issue has been identified in the Linux kernel, specifically in the drm/xe/tracing component. The issue arises from the `TP printk` function and the `xe mem type to name[]` array. This problem was exposed by a commit aimed at checking dereferences via the field and not the `TP printk` format. The estimated number of potentially affected devices and details about real-world incidents are not provided.

A vulnerability has been resolved in the Linux kernel. The issue occurs when userspace holds an fd open, unbinds the device, and then closes it, causing the driver to attempt to access the hardware. This is fixed by using `drm dev enter()`/`drm dev exit()` to protect against the fault. The vulnerability results in a page fault, specifically a supervisor read access in kernel mode with an error code of 0x0000, indicating a not-present page. The functions involved include `xe lrc update timestamp()`, `xe exec queue update run ticks()`, `xe exec queue fini()`, ` guc exec queue fini async()`, `guc exec queue fini async()`, `guc exec queue fini()`, `xe exec queue destroy()`, `xe file close()`, `drm file free()`, `drm close helper.isra.0()`, and `drm release noglobal()`.