CVE-2026-53153
What it is
In the Linux kernel, the following vulnerability has been resolved: mm/list_lru: drain before clearing xarray entry on reparent memcg_reparent_list_lrus() clears the dying memcg's xarray entry with xas_store(&xas, NULL) before reparenting its per-node lists into the parent. This opens a window where a concurrent list_lru_del() arriving for the dying memcg sees xa_load() == NULL, walks to the parent in lock_list_lru_of_memcg(), takes the parent's per-node lock, and calls list_del_init() on an item still physically linked on the dying memcg's list. If another in-flight thread holds the dying memcg's per-node lock at the same moment (another list_lru_del, or a list_lru_walk_one running an isolate callback), both threads modify ->next/->prev pointers on the same physical list under different locks. Adjacent items can corrupt each other's links. Fix it by reversing the order: reparent each per-node list and mark the child's list lru dead and then clear the xarray entry. Any concurrent list_lru op that finds the still-set xarray entry either takes the dying memcg's per-node lock (synchronizing with the drain) or sees LONG_MIN and walks to the parent, where the items now live.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-820
- Record status
- Modified
Affected
- Linux Kernel < 6.18.36
- Linux Kernel < 7.0.13
- Linux Kernel 7.1
- Redhat Enterprise Linux 10.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53153.md and follow it. Check whether this project is affected by CVE-2026-53153. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2b66496d794e98f7aeec7688573051f22ec40bac
- https://git.kernel.org/stable/c/98733f3f0becb1ae0701d021c1748e974e5fa55c
- https://git.kernel.org/stable/c/c19ff4351214f059349788e13e70e74325831ff6
References
- https://git.kernel.org/stable/c/2b66496d794e98f7aeec7688573051f22ec40bac
- https://git.kernel.org/stable/c/98733f3f0becb1ae0701d021c1748e974e5fa55c
- https://git.kernel.org/stable/c/c19ff4351214f059349788e13e70e74325831ff6
- https://access.redhat.com/errata/RHSA-2026:61887
- https://access.redhat.com/security/cve/CVE-2026-53153
- https://bugzilla.redhat.com/show_bug.cgi?id=2492790
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53153.json