CVE-2022-2585 is a medium severity use-after-free in the Linux kernel POSIX CPU timer code, scored 5.3 by NVD. Armed timers could be left on a list after being freed when a non-leader thread calls exec. Install your distribution's kernel update and reboot, since the fix is in the kernel.
What's affected
The record says that when a process executes a new program from a non-leader thread, armed POSIX CPU timers could be left on a list but freed, causing a use-after-free. The vector is CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H: a local attacker with low privileges and a high complexity attack.
The record lists the Linux kernel and Ubuntu 20.04 LTS, and references a kernel mailing list patch and four Ubuntu notices, USN-5564-1 to USN-5567-1. I read USN-5564-1, published 10 August 2022 for the Intel IoT kernel on 22.04. It lists this CVE and says a local attacker could cause a denial of service or execute arbitrary code.
The two sources frame the risk differently. NVD scores it 5.3 Medium, with high availability impact and low integrity impact. Ubuntu's notice describes possible arbitrary code execution without giving a score. I could not load the mailing list patch, so I cannot name the first fixed upstream version. Read your distribution notice for the fixed package.
Weakness class: CWE-416.
How to check if you're exposed
Kernel fixes arrive through your distribution, so the check is the running kernel against your vendor's notice. Start with the running version:
uname -r
apt list --upgradable 2>/dev/null | grep -i linux-image
The first line prints the running kernel. The second, on Debian and Ubuntu systems, shows pending kernel packages. A pending kernel update is not active until you reboot, so confirm the running version again afterwards. On other distributions use the equivalent package manager query and read the vendor's security notice for this CVE.
What to do now
- Find Linux hosts that run an unpatched kernel, using your package manager or configuration management.
- Install the kernel update from your distribution and reboot, or use a live patching service if you have one.
- Confirm the running kernel after the reboot.
- Prioritise hosts that run untrusted code for other users, such as shared build servers, container hosts and shell servers.
- Keep a record of kernel versions per host so future notices can be matched quickly.
Why it matters
A use-after-free means the kernel keeps using memory after it has been handed back to the allocator. If an attacker can get that memory reused for data they control, the stale pointer then acts on data of their choosing. The record files this as CWE-416, use after free.
A local flaw matters most where untrusted users or workloads share a kernel. On a laptop it is a step in a longer attack. On a container host, where every container shares the host kernel, it is part of the boundary between tenants.
The score of 5.3 reflects high attack complexity and the need for local access. Kernel memory corruption bugs are often chained with other flaws, so teams rarely treat a medium kernel CVE as optional once the fixed package is available.
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Do I need to reboot after updating?
Yes, unless you use live patching. The new kernel is not running until the machine restarts.
Can it be exploited remotely?
The record vector is local, so an attacker needs to run code on the machine first.
Sources
Last reviewed: 19 October 2026.