cveboard RSS feed

CVE-2024-43892

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2024
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

memcg: protect concurrent access to mem_cgroup_idr

In the Linux kernel, the following vulnerability has been resolved: memcg: protect concurrent access to mem_cgroup_idr Commit 73f576c04b94 ("mm: memcontrol: fix cgroup creation failure after many small jobs") decoupled the memcg IDs from the CSS ID space to fix the cgroup creation failures. It introduced IDR to maintain the memcg ID space. The IDR depends on external synchronization mechanisms for modifications. For the mem_cgroup_idr, the idr_alloc() and idr_replace() happen within css callback and thus are protected through cgroup_mutex from concurrent modifications. However idr_remove() for mem_cgroup_idr was not protected against concurrency and can be run concurrently for different memcgs when they hit their refcnt to zero. Fix that. We have been seeing list_lru based kernel crashes at a low frequency in our fleet for a long time. These crashes were in different part of list_lru code including list_lru_add(), list_lru_del() and reparenting code. Upon further inspection, it looked like for a given object (dentry and inode), the super_block's list_lru didn't have list_lru_one for the memcg of that object. The initial suspicions were either the object is not allocated through kmem_cache_alloc_lru() or somehow memcg_list_lru_alloc() failed to allocate list_lru_one() for a memcg but returned success. No evidence were found for these cases. Looking more deeply, we started seeing situations where valid memcg's id is not present in mem_cgroup_idr and in some cases multiple valid memcgs have same id and mem_cgroup_idr is pointing to one of them. So, the most reasonable explanation is that these situations can happen due to race between multiple idr_remove() calls or race between idr_alloc()/idr_replace() and idr_remove(). These races are causing multiple memcgs to acquire the same ID and then offlining of one of them would cleanup list_lrus on the system for all of them. Later access from other memcgs to the list_lru cause crashes due to missing list_lru_one.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
73f576c04b9410ed19660f74f97521bee6e1c546affectedgit912736a0435ef40e6a4ae78197ccb5553cb80b05UnavailableNone listed
73f576c04b9410ed19660f74f97521bee6e1c546affectedgite6cc9ff2ac0b5df9f25eb790934c3104f6710278UnavailableNone listed
73f576c04b9410ed19660f74f97521bee6e1c546affectedgit56fd70f4aa8b82199dbe7e99366b1fd7a04d86fbUnavailableNone listed
73f576c04b9410ed19660f74f97521bee6e1c546affectedgit37a060b64ae83b76600d187d76591ce488ab836bUnavailableNone listed
73f576c04b9410ed19660f74f97521bee6e1c546affectedgit51c0b1bb7541f8893ec1accba59eb04361a70946UnavailableNone listed
73f576c04b9410ed19660f74f97521bee6e1c546affectedgit9972605a238339b85bd16b084eed5f18414d22dbUnavailableNone listed
8627c7750a66a46d56d3564e1e881aa53764497caffectedgitUnavailableUnavailableNone listed
db70cd18d3da727a3a59694de428a9e41c620de7affectedgitUnavailableUnavailableNone listed
4.4.18affectedsemver4.5UnavailableNone listed
4.6.6affectedsemver4.7UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.7affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.7UnavailableNone listed
5.10.226unaffectedsemverUnavailable5.10.*None listed
5.15.167unaffectedsemverUnavailable5.15.*None listed
6.1.110unaffectedsemverUnavailable6.1.*None listed
6.6.46unaffectedsemverUnavailable6.6.*None listed
6.10.5unaffectedsemverUnavailable6.10.*None listed
6.11unaffectedoriginal_commit_for_fixUnavailable*None listed