mm/list_lru: drain before clearing xarray entry on reparent
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.36, 7.0.13
- CVEs
- CVE-2026-53153
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 12:56 UTC · Revision 1
Source evidence
mm/list_lru: drain before clearing xarray entry on reparent
core-osv · Original sourcePublished 25 Jun 2026, 08:38 UTC
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.
osv:CVE-2026-53153
Kernel
Fixed versions: 6.18.36, 7.0.13
Complete source record
{
"id": "93e7b9dcb516daf3939f32d95a1347c319a6303073647950b19b7ea38c702c79",
"url": "https://osv.dev/vulnerability/CVE-2026-53153",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "mm/list_lru: drain before clearing xarray entry on reparent",
"summary": "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.",
"evidence": "osv:CVE-2026-53153",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.36",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.13",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-53153",
"aliases": [
"CVE-2026-53153"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "fb56fdf8b9a2f7397f8a83dce50189f3f0cf71af"
},
{
"fixed": "c19ff4351214f059349788e13e70e74325831ff6"
},
{
"fixed": "2b66496d794e98f7aeec7688573051f22ec40bac"
},
{
"fixed": "98733f3f0becb1ae0701d021c1748e974e5fa55c"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53153.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.36"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.13"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53153.json"
}
}
],
"modified": "2026-10-28T02:30:28.811118689Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/2b66496d794e98f7aeec7688573051f22ec40bac",
"https://git.kernel.org/stable/c/98733f3f0becb1ae0701d021c1748e974e5fa55c",
"https://git.kernel.org/stable/c/c19ff4351214f059349788e13e70e74325831ff6",
"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53153.json",
"https://access.redhat.com/errata/RHSA-2026:61887",
"https://access.redhat.com/security/cve/CVE-2026-53153",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53153.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-53153",
"https://bugzilla.redhat.com/show_bug.cgi?id=2492790",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53153.json"
}
},
"related_cves": [
{
"value": "CVE-2026-53153",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 495588,
"published_at": "2026-06-25T08:38:37.521+00:00"
}