CVE-2022-49645·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Fix shrinker list corruption by madvise IOCTL Calling madvise IOCTL twice on BO causes memory shrinker list corruption and crashes kernel because BO is already on the list and it's added to the list again, while BO should be removed from the list before it's re-added. Fix it.
- Severity
- high
- Software
- Kernel
- Fixed in
- 5.18.13
- Published
- 2025-02-26
Affected versions
From: 5.16
Until: 5.18.13
Fixed in: 5.18.13
How to fix this CVE
Update your Linux kernel to version 5.18.13 or later to resolve a critical memory management flaw in the DRM Panfrost driver. This vulnerability allows repeated madvise IOCTL calls to corrupt the kernel's memory shrinker list, leading to system crashes. Administrators should prioritize this update, especially on systems running kernels 5.16 through 5.18.12.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r` and confirm it falls within 5.16.x to 5.18.12
- Step 2: Verify if GPU-accelerated graphics via Panfrost driver is active by checking `lspci | grep -i vga` and `dmesg | grep -i panfrost`
- Step 3: Search kernel logs for memory shrinker list corruption symptoms using `dmesg | grep -i 'list_add double add\|shrinker\|memory corruption'`
- Step 4: After applying the patch, confirm the new kernel version with `uname -r` and verify no shrinker warnings appear in fresh dmesg output
FAQ
What is CVE-2022-49645?
This vulnerability exists in the DRM Panfrost graphics driver where calling the madvise IOCTL twice on a buffer object (BO) causes the kernel to attempt adding it to the memory shrinker list twice, corrupting critical kernel data structures and triggering system crashes.
Is CVE-2022-49645 being actively exploited?
No, this vulnerability is not actively exploited in the wild and no public exploits are available. It requires local access and knowledge of the specific madvise IOCTL sequence to trigger.
What versions of Kernel are affected by CVE-2022-49645?
Linux kernel versions 5.16.0 through 5.18.12 are affected. The fix is included starting with kernel version 5.18.13 and all subsequent releases.
How do I check if my server is vulnerable to CVE-2022-49645?
Run `uname -r` to check your kernel version. If it displays a version between 5.16 and 5.18.12 (e.g., 5.17.5 or 5.18.11), your system is vulnerable if Panfrost GPU support is enabled.
Does Defensia detect CVE-2022-49645?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2022-49645 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0581613df7f9a4c5fac096ce1d5fb15b7b994240
- https://git.kernel.org/stable/c/1807d8867402a58b831a7fc16832747ff559a0d1
- https://git.kernel.org/stable/c/393594aad55179eb761af41533d8d1d6eb4543b0
- https://git.kernel.org/stable/c/9fc33eaaa979d112d10fea729edcd2a2e21aa912
- https://git.kernel.org/stable/c/f036392edd9c49090781d8cca26ad6557a63bae4
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49645. Free for 1 server.
Get started free