PoC Monitor
← All CVEs
CVE-2026-53264published 25 Jun 2026 08:39 UTCData: JSON · API

Linux

net/sched: act_api: use RCU with deferred freeing for action lifecycle

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.

First public PoC 113 daysafter publication · 16 Oct 2026
Public PoCs11 on GitHub
CVSS7.8high · scored by CNA · CWE-416
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < 98b2e40879abf0245be5a5b7af69e0f6ff524ac3
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < 18af5d2ef0c4f65787fd1280c8b23286b9f2a835
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < 1f1b98fea6b9ea30507d0f2fbff6750292d097e2
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < 8b136f18ac4b2ace5aaad3305b3f8a5d8165a009
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < 5dd51e09020c65aa53cf128e5e3517cd53b3c113
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < b60e9391142e983fab2be53497aa8f71fdd09cd5
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < 91d105d2cbe002f9c7b43a6183adedc37e1da1f7
  • >= d7fb60b9cafb982cb2e46a267646a8dfd4f2e5da, < 5057e1aca011e51ef51498c940ef96f3d3e8a305

Fixed in 98b2e40879abf0245be5a5b7af69e0f6ff524ac3, 18af5d2ef0c4f65787fd1280c8b23286b9f2a835, 1f1b98fea6b9ea30507d0f2fbff6750292d097e2, 8b136f18ac4b2ace5aaad3305b3f8a5d8165a009, 5dd51e09020c65aa53cf128e5e3517cd53b3c113, b60e9391142e983fab2be53497aa8f71fdd09cd5, 91d105d2cbe002f9c7b43a6183adedc37e1da1f7, 5057e1aca011e51ef51498c940ef96f3d3e8a305

Linux Linux
  • 4.14

Fixed in 0, 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13, 7.1

Mitigation

Upgrade Linux to 98b2e40879abf0245be5a5b7af69e0f6ff524ac3 or 18af5d2ef0c4f65787fd1280c8b23286b9f2a835 or 1f1b98fea6b9ea30507d0f2fbff6750292d097e2 or 8b136f18ac4b2ace5aaad3305b3f8a5d8165a009 or 5dd51e09020c65aa53cf128e5e3517cd53b3c113 or b60e9391142e983fab2be53497aa8f71fdd09cd5 or 91d105d2cbe002f9c7b43a6183adedc37e1da1f7 or 5057e1aca011e51ef51498c940ef96f3d3e8a305 or later.

Upgrade Linux to 0 or 5.10.259 or 5.15.210 or 6.1.176 or 6.6.143 or 6.12.94 or 6.18.36 or 7.0.13 or 7.1 or later.

Timeline

Days relative to CVE publication
t=0+14+28+42+56+70+84+98+112CVE published25 Jun 2026 · t = 0First public PoC16 Oct 2026 · t+113d

First public PoC 113 days after publication; not in CISA KEV. First PoC: b1nhack/CVE-2026-53264 (created 16 Oct 2026, found by us: 14 Nov 2026).

PoC repositories

Found on GitHub.

1 PoCs · 1 suspicious or fake

PoCs 1
RepositoryCreatedFound by usStarsAssessment
b1nhack/CVE-2026-53264 16 Oct 2026 +113 d 14 Nov 2026 1 PoC
Suspicious or fake 1
RepositoryCreatedStarsAssessment
HORKimhab/CVE-2026-53264 28 Jul 2026 +33 d 3 Fake

Only PoCs count toward the first-PoC date and the characteristics below. "Backfilled" means we found the repository more than 30 days after it was created. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.
SourceTitlePublishedFound by us
CVE record (tagged exploit)https://starlabs.sg/blog/2026/07-when-ai-makes-0-days-feel-like-n-days/unknown14 Nov 2026