CVE-2022-2588 is a medium severity use-after-free in the Linux kernel cls_route traffic filter, scored 5.3 by NVD. A filter with handle 0 was not removed from the hashtable before it was freed. Install your distribution kernel update and reboot, because a public repository describes exploit code for it.
What's affected
The record says the cls_route filter implementation in the Linux kernel did not remove an old filter from the hashtable before freeing it if its handle had the value 0. The vector is CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H, which is local, with low privileges and high complexity.
The record references a kernel mailing list patch and several Ubuntu notices, including USN-5557-1, USN-5560-1 and USN-5560-2, plus a GitHub repository whose page describes it as an exploit for this CVE. I read Ubuntu's USN-5564-1, published 10 August 2022, which credits the finding to Zhenpeng Lin and says a local attacker could cause a denial of service or execute arbitrary code.
The sources frame severity differently. NVD scores 5.3 Medium. Ubuntu's notice describes the possibility of arbitrary code execution. The CVE is not on the CISA exploited list, and I read nothing that says it was used in attacks, but the existence of public exploit code raises the practical urgency. I could not load the patch, so read your distribution notice for the fixed package.
Weakness class: CWE-416, CWE-415.
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 running an unpatched kernel.
- Install the distribution kernel update and reboot, or apply live patching.
- Where you cannot update immediately, consider whether the cls_route traffic classifier is in use and whether unprivileged users can create network namespaces on those hosts, and ask your vendor what they recommend.
- Restrict shell and container access on hosts that are waiting for the update.
- Confirm the running kernel afterwards.
Why it matters
The record describes a classic bookkeeping error. An object is freed, but a table still points to it. The next time the kernel follows that pointer, it works on memory that may now belong to something else. The record files it under CWE-416, CWE-415, which covers use after free and double free.
The traffic control subsystem lets privileged users shape network traffic. Where unprivileged users can create their own network namespaces, parts of it become reachable by ordinary accounts, which is why bugs here show up in local privilege escalation stories.
A public exploit changes the timeline. Medium scores come from vectors and do not account for how much work an attacker must do. When code is published, the work is already done.
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.
Quick check
Is exploit code public?
The record references a public GitHub repository that describes itself as an exploit for this CVE. That is not the same as evidence of attacks in the wild, which I did not find.
Is it on the CISA exploited list?
No. The record's KEV flag is false.
Sources
Last reviewed: 19 October 2026.