CVE-2022-49385·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 5.18.4
- Published
- 2025-02-26
Affected versions
From: 5.18
Until: 5.18.4
Fixed in: 5.18.4
How to fix this CVE
Update your Linux kernel to version 5.18.4 or later to resolve a use-after-free vulnerability in the driver attachment mechanism. This flaw occurs when driver attachment fails but the driver remains registered on the bus, creating a window for memory corruption. Apply the patch immediately to systems running kernel versions 5.18 through 5.18.3.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check installed kernel version by running: uname -r
- Step 2: Confirm if kernel version is within 5.18.0 to 5.18.3 range using: cat /proc/version
- Step 3: Review kernel logs for device driver attachment failures with: dmesg | grep -i 'driver_attach\|device.*attach' | tail -20
- Step 4: Verify kernel update completed by rebooting and running uname -r to confirm version is 5.18.4 or higher
FAQ
What is CVE-2022-49385?
CVE-2022-49385 is a use-after-free vulnerability in the Linux kernel's driver base framework. When a driver fails to attach to a bus, the driver object is improperly freed while still registered, allowing potential memory corruption attacks.
Is CVE-2022-49385 being actively exploited?
No, CVE-2022-49385 is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, the high CVSS score (7.8) warrants timely patching due to its local privilege escalation potential.
What versions of Kernel are affected by CVE-2022-49385?
Linux kernel versions 5.18.0 through 5.18.3 are vulnerable. The fix is included in kernel 5.18.4 and all later releases.
How do I check if my server is vulnerable to CVE-2022-49385?
Run 'uname -r' and compare the output against the vulnerable range 5.18.0-5.18.3. If your kernel version falls within this range, your system is vulnerable and requires immediate updating.
Does Defensia detect CVE-2022-49385?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server running versions 5.18.0-5.18.3, CVE-2022-49385 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/310862e574001a97ad02272bac0fd13f75f42a27
- https://git.kernel.org/stable/c/5389101257828d1913d713d9a40acbe14f5961df
- https://git.kernel.org/stable/c/5d709f58c743166fe1c6914b9de0ae8868600d9b
- https://git.kernel.org/stable/c/823f24f2e329babd0330200d0b74882516fe57f4
- https://git.kernel.org/stable/c/c059665c84feab46b7173d3a1bf36c2fb7f9df86
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49385. Free for 1 server.
Get started free