CVE-2026-53264Linux Linux Kernel Use After Free
NVDCVSS scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Vulnerability Summary
In the Linux kernel, the following vulnerability has been resolved:
net/sched: act_api: use RCU with deferred freeing for action lifecycle
When NEWTFILTER and DELFILTER are run concurrently it is possible to create a
race with an associated action.
Let's illustrate with CPU0 running NEWTFILTER and CPU1 running DELFILTER:
0: mutex_lock() <-- holds the idr lock
0: rcu_read_lock()
0: p = idr_find(idr, index) <-- action p is valid (RCU protects IDR)
0: mutex_unlock() <-- releases the idr lock
1: refcount_dec_and_mutex_lock() <-- refcnt 1->0, mutex held
1: idr_remove(idr, index) <-- Action removed from IDR
1: mutex_unlock() <-- mutex released allowing us to delete the action
1: tcf_action_cleanup(p); kfree(p) <-- Kfrees p immediately, no deferral
0: refcount_inc_not_zero(&p->tcfa_refcnt) <-- ouch, UAF p points to freed memory
This patch fixes the race condition between NEWTFILTER and DELFILTER by
adding struct rcu_head to tc_action used in the deferral and introducing a
call_rcu() in the delete path to defer the final kfree().
Note: this is a revert of commit d7fb60b9cafb ("net_sched: get rid of tcfa_rcu")
but also modernization/simplification to directly use kfree_rcu().
Let's illustrate the new restored code path:
0: rcu_read_lock()
1: refcount_dec_and_mutex_lock() <-- refcnt 1->0, mutex held
1: idr_remove(idr, index)
1: mutex_unlock()
1: call_rcu(&p->tcfa_rcu, tcf_action_rcu_free) <-- defer kfree after grace period
0: p = idr_find(idr, index)
0: refcount_inc_not_zero(&p->tcfa_refcnt) <-- fails, refcnt already 0
1: rcu_read_unlock() <-- release so freeing can run after grace period
After CPU1 calls idr_remove(), the object is no longer reachable through the IDR.
CPU0's subsequent idr_find() will return NULL, and even if it still held a
stale pointer, the immediate kfree() is now deferred until after the RCU grace
period, so no UAF can occur.
net/sched: act_api: use RCU with deferred freeing for action lifecycle
When NEWTFILTER and DELFILTER are run concurrently it is possible to create a
race with an associated action.
Let's illustrate with CPU0 running NEWTFILTER and CPU1 running DELFILTER:
0: mutex_lock() <-- holds the idr lock
0: rcu_read_lock()
0: p = idr_find(idr, index) <-- action p is valid (RCU protects IDR)
0: mutex_unlock() <-- releases the idr lock
1: refcount_dec_and_mutex_lock() <-- refcnt 1->0, mutex held
1: idr_remove(idr, index) <-- Action removed from IDR
1: mutex_unlock() <-- mutex released allowing us to delete the action
1: tcf_action_cleanup(p); kfree(p) <-- Kfrees p immediately, no deferral
0: refcount_inc_not_zero(&p->tcfa_refcnt) <-- ouch, UAF p points to freed memory
This patch fixes the race condition between NEWTFILTER and DELFILTER by
adding struct rcu_head to tc_action used in the deferral and introducing a
call_rcu() in the delete path to defer the final kfree().
Note: this is a revert of commit d7fb60b9cafb ("net_sched: get rid of tcfa_rcu")
but also modernization/simplification to directly use kfree_rcu().
Let's illustrate the new restored code path:
0: rcu_read_lock()
1: refcount_dec_and_mutex_lock() <-- refcnt 1->0, mutex held
1: idr_remove(idr, index)
1: mutex_unlock()
1: call_rcu(&p->tcfa_rcu, tcf_action_rcu_free) <-- defer kfree after grace period
0: p = idr_find(idr, index)
0: refcount_inc_not_zero(&p->tcfa_refcnt) <-- fails, refcnt already 0
1: rcu_read_unlock() <-- release so freeing can run after grace period
After CPU1 calls idr_remove(), the object is no longer reachable through the IDR.
CPU0's subsequent idr_find() will return NULL, and even if it still held a
stale pointer, the immediate kfree() is now deferred until after the RCU grace
period, so no UAF can occur.
CVSS v3.1 Base Metrics — Score 7.8 (HIGH)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HAttack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
Affected & Patched Versions
- Linux Linux Kernel >= 4.14 and < 5.10.259
- Linux Linux Kernel >= 5.11 and < 5.15.210
- Linux Linux Kernel >= 5.16 and < 6.1.176
- Linux Linux Kernel >= 6.2 and < 6.6.143
- Linux Linux Kernel >= 6.7 and < 6.12.94
- Linux Linux Kernel >= 6.13 and < 6.18.36
- Linux Linux Kernel >= 6.19 and < 7.0.13
- Linux Linux Kernel
- Linux Linux Kernel 5.10.259
- Linux Linux Kernel 5.15.210
- Linux Linux Kernel 6.1.176
- Linux Linux Kernel 6.6.143
- Linux Linux Kernel 6.12.94
- Linux Linux Kernel 6.18.36
- Linux Linux Kernel 7.0.13
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run Linux Linux Kernel and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Jun 25, 2026Published
- Oct 15, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Linux Linux Kernel CVEsYou are reading CVE-2026-53264. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
External References
- Patchhttps://git.kernel.org/stable/c/18af5d2ef0c4f65787fd1280c8b23286b9f2a835
- Patchhttps://git.kernel.org/stable/c/1f1b98fea6b9ea30507d0f2fbff6750292d097e2
- Patchhttps://git.kernel.org/stable/c/5057e1aca011e51ef51498c940ef96f3d3e8a305
- Patchhttps://git.kernel.org/stable/c/5dd51e09020c65aa53cf128e5e3517cd53b3c113
- Patchhttps://git.kernel.org/stable/c/8b136f18ac4b2ace5aaad3305b3f8a5d8165a009
- Patchhttps://git.kernel.org/stable/c/91d105d2cbe002f9c7b43a6183adedc37e1da1f7
- Patchhttps://git.kernel.org/stable/c/98b2e40879abf0245be5a5b7af69e0f6ff524ac3
- Patchhttps://git.kernel.org/stable/c/b60e9391142e983fab2be53497aa8f71fdd09cd5
- Referencehttps://cert-portal.siemens.com/productcert/html/ssa-784472.html
- Referencehttps://starlabs.sg/blog/2026/07-when-ai-makes-0-days-feel-like-n-days/
Data last checked: Nov 17, 2026 15:13 UTC