CVE-2022-49385Published Feb 26, 2025 · Feb 26Updated Oct 28
driver: base: fix UAF when driver_attach failed
Linux
High7.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 190888ac01d059e38ffe77a2291d44cafa9016fb · < 310862e574001a97ad02272bac0fd13f75f42a27| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel has a use-after-free in the driver core when driver_attach fails: freed driver_private data remains on the bus. The input does not specify how an attacker could trigger the failure or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.