Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53153: mm/list_lru: drain before clearing xarray entry on reparent

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2b66496d794e98f7aeec7688573051f22ec40bac, 98733f3f0becb1ae0701d021c1748e974e5fa55c, c19ff4351214f059349788e13e70e74325831ff6.

Low priority for now. Upgrade to Linux Linux 2b66496d794e98f7aeec7688573051f22ec40bac, 98733f3f0becb1ae0701d021c1748e974e5fa55c, c19ff4351214f059349788e13e70e74325831ff6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Sep 2, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53153

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
redhatenterprise linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.13 and later · before 6.18.36
  • linux linux kernel6.19 and later · before 7.0.13
  • linux linux kernel7.1
  • redhat enterprise linux10.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.13affected
    • fb56fdf8b9a2f7397f8a83dce50189f3f0cf71af and later · before c19ff4351214f059349788e13e70e74325831ff6affected · git
    • fb56fdf8b9a2f7397f8a83dce50189f3f0cf71af and later · before 2b66496d794e98f7aeec7688573051f22ec40bacaffected · git
    • fb56fdf8b9a2f7397f8a83dce50189f3f0cf71af and later · before 98733f3f0becb1ae0701d021c1748e974e5fa55caffected · git
    • before 6.13not affected · semver
    • 6.18.36 and later · up to and including 6.18.*not affected · semver
    • 7.0.13 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53144Jun 25, 2026 · drm/amdkfd: fix NULL dereference in get_queue_ids()
    22Monitor
  • ← EarlierCVE-2026-53152Jun 25, 2026 · mmc: dw_mmc-rockchip: Add missing private data for very old controllers
    22Monitor
  • Later →CVE-2026-53154Jun 25, 2026 · mm/hugetlb: restore reservation on error in hugetlb folio copy paths
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2b66496d794e98f7aeec7688573051f22ec40bacVendor (CNA)
Linux Linux98733f3f0becb1ae0701d021c1748e974e5fa55cVendor (CNA)
Linux Linuxc19ff4351214f059349788e13e70e74325831ff6Vendor (CNA)
almalinux:kernel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux7.0.13-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:kernel0:6.12.0-211.50.1.el10_2 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-820 · Missing Synchronization

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records