CVE-2026-53117
UnknownSummary
A vulnerability has been identified in the Linux kernel related to the driver_override mechanism in the context of s390/cio. The issue arises because the device lock is not held when calling __driver_attach(), which can lead to a use-after-free (UAF) situation.
Risk Assessment
The lack of proper locking when accessing the driver_override field may lead to unpredictable system behavior, posing a risk to the stability and security of the operating system.
Recommendation
It is recommended to update the Linux kernel to a version that includes a fix addressing this issue to ensure proper locking mechanisms when accessing driver_override.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: s390/cio: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]