All reports
Medium

kernel: driver: base: fix UAF when driver_attach failed

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2022-49385

Probability of exploitation in the next 30 days: 0.30%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: driver: base: fix UAF when driver_attach failed When driver_attach(drv); failed, the driver_private will be freed. But it has been added to the bus, which caused a UAF. To fix it, we need to delete it from the bus when failed.

A flaw was discovered in the Linux kernel’s device driver core. When driver_attach(drv) fails, the associated driver_private structure is freed—but the driver remains registered on the bus. This leads to a use-after-free condition when the kernel subsequently references the freed driver_private. A local, authenticated user with low privileges can trigger this flaw to cause memory corruption, system instability, or denial of service.