Linux: Missing Synchronization
CVE-2026-53153 is a high-severity missing synchronization vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions c19ff4351214f059349788e13e70e74325831ff6, 2b66496d794e98f7aeec7688573051f22ec40bac, 98733f3f0becb1ae0701d021c1748e974e5fa55c as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.1% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to c19ff4351214f059349788e13e70e74325831ff6 or 2b66496d794e98f7aeec7688573051f22ec40bac or 98733f3f0becb1ae0701d021c1748e974e5fa55c, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.18.36 or 7.0.13, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | fb56fdf8b9a2f7397f8a83dce50189f3f0cf71af up to, but not including, c19ff4351214f059349788e13e70e74325831ff6; fb56fdf8b9a2f7397f8a83dce50189f3f0cf71af up to, but not including, 2b66496d794e98f7aeec7688573051f22ec40bac; fb56fdf8b9a2f7397f8a83dce50189f3f0cf71af up to, but not including, 98733f3f0becb1ae0701d021c1748e974e5fa55c; 6.13 | c19ff4351214f059349788e13e70e74325831ff6, 2b66496d794e98f7aeec7688573051f22ec40bac, 98733f3f0becb1ae0701d021c1748e974e5fa55c |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 6 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Linux | Linux Kernel | 6.13 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.1 | 6.18.36, 7.0.13 |
| Red Hat | Enterprise Linux | 10.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.0 | High | CNA |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Synchronization
The product utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- access.redhat.com/security/cve/CVE-2026-53153Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2492790Third Party Advisory
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53153.jsonThird Party Advisory
Other references
Recent Missing Synchronization vulnerabilities
- 7.8 High severity
- 7.4 High severity
- 9.0 Critical severity
- 7.5 High severity
Spotted an error? Tell us.