PT-2026-106554

CVE-2026-98225

·

Published

2026-10-06

·

Updated

2026-10-14

Description by

CVSS 4.0
4.8
Medium
MetricsAV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions Linux kernel (affected versions not specified)
Description An issue exists in the memory management subsystem where using the cgroup.memory=nokmem configuration causes shrinker memcg alloc() to exit early without allocating an ID. Consequently, shrinker->id retains a value of 0, which list lru init() then copies into lru->shrinker id, making it appear as a valid bit index. Because expand shrinker info() is not called under this configuration, shrinker nr max remains 0, resulting in empty maps for every memory control group (memcg). When deferred split folio() passes a real memcg to list lru add(), the first Transparent Huge Page (THP) queued in a cgroup triggers the set shrinker bit() function with an index of 0, leading to a bounds check warning. This occurs because the system attempts to access a bit index that should not be valid when memory control group awareness is disabled.
Recommendations At the moment, there is no information about a newer version that contains a fix for this vulnerability.
Exploitability
Exploit
Vendors
Affected products
Related identifiers
OPENSUSE-SU-2026:12131-1
Found an issue in the description? Have something to add? Feel free to write us 👾