PoC Monitor
← All CVEs
CVE-2026-97941published 25 Sep 2026 10:22 UTCData: JSON · API

Linux

mm/slab: take n->list_lock in __slab_try_return_freelist() to avoid race

In the Linux kernel, the following vulnerability has been resolved: mm/slab: take n->list_lock in __slab_try_return_freelist() to avoid race Commit ba7425312607 ("mm, slab: add an optimistic __slab_try_return_freelist()") incorrectly assumed that nobody has freed an object to the slab as long as slab->freelist is NULL and cmpxchg succeeds. However, as reported by Hyunwoo Kim [1], other CPUs might have freed an object to the slab, insert the slab to the partial list, then allocated an object from the slab, and be in the middle of removing the slab from the list under n->list_lock. Since __refill_objects_node() puts the slab back on pc.slabs outside n->list_lock, it might insert the slab into that list while the slab is concurrently being removed from n->partial. This led to a list corruption [1]: list_add corruption. next->prev should be prev (ffff888100000248), but was dead000000000122. (next=ffffea000416e410). kernel BUG at lib/list_debug.c:29! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 1 UID: 65534 PID: 144 Comm: poc Not tainted 7.2.0-16172-gcf72cbb39da8-dirty #1 PREEMPT(lazy) RIP: 0010:__list_add_valid_or_report+0x80/0xd0 ... Call Trace: alloc_from_new_slab+0x183/0x300 ___slab_alloc+0x31c/0x890 __kmalloc_noprof+0x3d4/0x800 lsm_blob_alloc+0x2d/0x50 security_msg_msg_alloc+0x26/0x90 load_msg+0x1aa/0x210 do_msgsnd+0x91/0x800 do_syscall_64+0x109/0x5d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... Kernel panic - not syncing: Fatal exception This is a classic ABA problem where cmpxchg succeeds but the state has changed since __refill_objects_node() took the freelist from the slab. As Vlastimil Babka mentioned [2], it should be rare to return more than one slab (due to the racy read of slab->counters in get_partial_node_bulk()). Therefore, instead of introducing additional complexity, acquire and release n->list_lock twice in the worst case. Return the slab directly to the partial list and hold n->list_lock across the cmpxchg and add_partial(). This is similar to the initial version of commit ba7425312607 [3]. This is enough to avoid the race as the list manipulation is serialized by n->list_lock. While at it, bring back unlikely() hint now that the condition is unlikely.

First public PoC 24 daysafter publication · 18 Oct 2026
Public PoCs11 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= ba742531260782a2646bc031f9a12cafebc22594, < 570a6aaf6b52c6ec098f4811cdb52b1496f13d15
  • >= ba742531260782a2646bc031f9a12cafebc22594, < 4a724bcf5d703e18957397914d79156fa2cf1174

Fixed in 570a6aaf6b52c6ec098f4811cdb52b1496f13d15, 4a724bcf5d703e18957397914d79156fa2cf1174

Linux Linux
  • 7.2

Fixed in 0, 7.2.7, 7.3

Mitigation

Upgrade Linux to 570a6aaf6b52c6ec098f4811cdb52b1496f13d15 or 4a724bcf5d703e18957397914d79156fa2cf1174 or later.

Upgrade Linux to 0 or 7.2.7 or 7.3 or later.

Timeline

Days relative to CVE publication
t=0+7+14+21CVE published25 Sep 2026 · t = 0First public PoC18 Oct 2026 · t+24d

First public PoC 24 days after publication; not in CISA KEV. First PoC: ylh440104/InfinityCore-Android-CVE-2026-97941 (created 18 Oct 2026, found by us: 14 Nov 2026).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedFound by usStarsAssessment
ylh440104/InfinityCore-Android-CVE-2026-97941 18 Oct 2026 +24 d 14 Nov 2026 2 PoC
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.