← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-89985

Last refreshed2026-10-19

Status: UPDATED  |  Advisory ID: CVE-2026-89985

Key Details

CVECVE-2026-89985
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-19
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

In the Linux kernel, the following vulnerability has been resolved:

memcg: keep folio's objcg same as its node

memcg_reparent_objcgs() has an inherent assumption that a folio's objcg is

the objcg of the folio's node. Folio migration across nodes breaks that

assumption: the new folio simply inherits the old folio's objcg while

living on a different node.

Once the assumption is broken, the reparenting of the folio's objcg and

the reparenting of the folio's LRU list are no longer atomic.

memcg_reparent_objcgs() handles one node per iteration and drops all the

locks in between, so the objcg gets reparented in the iteration for the

objcg's node while the LRU list gets spliced in the iteration for the

folio's node. Any LRU operation on that folio in between resolves its

lruvec through the objcg, and thus takes the lru_lock of the wrong memcg,

not the lru_lock of the list the folio is actually on.

Fix this by selecting the objcg by folio_nid() at charge time, and by

re-deriving it for the destination node in mem_cgroup_migrate() and

mem_cgroup_replace_folio(). (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-89985
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-89985
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.