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
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.226, 5.15.167, 6.1.110, 6.10.5, 6.6.46
- CVEs
- CVE-2024-43892
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 16:15 UTC · Revision 1
Source evidence
memcg: protect concurrent access to mem_cgroup_idr
core-osv · Original sourcePublished 26 Aug 2024, 10:10 UTC
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
osv:CVE-2024-43892
Kernel
Fixed versions: 5.10.226, 5.15.167, 6.1.110, 6.6.46, 6.10.5
Complete source record
{
"id": "837efc0cf73d9a8aec1260c08162b244cceab22097cae50e11412cfe208c26b6",
"url": "https://osv.dev/vulnerability/CVE-2024-43892",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "memcg: protect concurrent access to mem_cgroup_idr",
"summary": "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",
"evidence": "osv:CVE-2024-43892",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.226",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.167",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.110",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.46",
"evidence": "/affected/1/ranges"
},
{
"value": "6.10.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-43892",
"aliases": [
"CVE-2024-43892"
],
"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": "73f576c04b9410ed19660f74f97521bee6e1c546"
},
{
"fixed": "912736a0435ef40e6a4ae78197ccb5553cb80b05"
},
{
"fixed": "e6cc9ff2ac0b5df9f25eb790934c3104f6710278"
},
{
"fixed": "56fd70f4aa8b82199dbe7e99366b1fd7a04d86fb"
},
{
"fixed": "37a060b64ae83b76600d187d76591ce488ab836b"
},
{
"fixed": "51c0b1bb7541f8893ec1accba59eb04361a70946"
},
{
"fixed": "9972605a238339b85bd16b084eed5f18414d22db"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4.4.18"
},
{
"fixed": "4.5"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4.6.6"
},
{
"fixed": "4.7"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8627c7750a66a46d56d3564e1e881aa53764497c"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "db70cd18d3da727a3a59694de428a9e41c620de7"
}
]
}
],
"versions": [
"v4.4.302",
"v4.4.301",
"v4.4.300",
"v4.4.299",
"v4.4.298",
"v4.4.297",
"v4.4.296",
"v4.4.295",
"v4.4.294",
"v4.4.293",
"v4.4.292",
"v4.4.291",
"v4.4.290",
"v4.4.289",
"v4.4.288",
"v4.4.287",
"v4.4.286",
"v4.4.285",
"v4.4.284",
"v4.4.283",
"v4.4.282",
"v4.4.281",
"v4.4.280",
"v4.4.279",
"v4.4.278",
"v4.4.277",
"v4.4.276",
"v4.4.275",
"v4.4.274",
"v4.4.273",
"v4.4.272",
"v4.4.271",
"v4.4.270",
"v4.4.269",
"v4.4.268",
"v4.4.267",
"v4.4.266",
"v4.4.265",
"v4.4.264",
"v4.4.263",
"v4.4.262",
"v4.4.261",
"v4.4.260",
"v4.4.259",
"v4.4.258",
"v4.4.257",
"v4.4.256",
"v4.4.255",
"v4.4.254",
"v4.4.253",
"v4.4.252",
"v4.4.251",
"v4.4.250",
"v4.4.249",
"v4.4.248",
"v4.4.247",
"v4.4.246",
"v4.4.245",
"v4.4.244",
"v4.4.243",
"v4.4.242",
"v4.4.241",
"v4.4.240",
"v4.4.239",
"v4.4.238",
"v4.4.237",
"v4.4.236",
"v4.4.235",
"v4.4.234",
"v4.4.233",
"v4.4.232",
"v4.4.231",
"v4.4.230",
"v4.4.229",
"v4.4.228",
"v4.4.227",
"v4.4.226",
"v4.4.225",
"v4.4.224",
"v4.4.223",
"v4.4.222",
"v4.4.221",
"v4.4.220",
"v4.4.219",
"v4.4.218",
"v4.4.217",
"v4.4.216",
"v4.4.215",
"v4.4.214",
"v4.4.213",
"v4.4.212",
"v4.4.211",
"v4.4.210",
"v4.4.209",
"v4.4.208",
"v4.4.207",
"v4.4.206",
"v4.4.205",
"v4.4.204",
"v4.4.203",
"v4.4.202",
"v4.4.201",
"v4.4.200",
"v4.4.199",
"v4.4.198",
"v4.4.197",
"v4.4.196",
"v4.4.195",
"v4.4.194",
"v4.4.193",
"v4.4.192",
"v4.4.191",
"v4.4.190",
"v4.4.189",
"v4.4.188",
"v4.4.187",
"v4.4.186",
"v4.4.185",
"v4.4.184",
"v4.4.183",
"v4.4.182",
"v4.4.181",
"v4.4.180",
"v4.4.179",
"v4.4.178",
"v4.4.177",
"v4.4.176",
"v4.4.175",
"v4.4.174",
"v4.4.173",
"v4.4.172",
"v4.4.171",
"v4.4.170",
"v4.4.169",
"v4.4.168",
"v4.4.167",
"v4.4.166",
"v4.4.165",
"v4.4.164",
"v4.4.163",
"v4.4.162",
"v4.4.161",
"v4.4.160",
"v4.4.159",
"v4.4.158",
"v4.4.157",
"v4.4.156",
"v4.4.155",
"v4.4.154",
"v4.4.153",
"v4.4.152",
"v4.4.151",
"v4.4.150",
"v4.4.149",
"v4.4.148",
"v4.4.147",
"v4.4.146",
"v4.4.145",
"v4.4.144",
"v4.4.143",
"v4.4.142",
"v4.4.141",
"v4.4.140",
"v4.4.139",
"v4.4.138",
"v4.4.137",
"v4.4.136",
"v4.4.135",
"v4.4.134",
"v4.4.133",
"v4.4.132",
"v4.4.131",
"v4.4.130",
"v4.4.129",
"v4.4.128",
"v4.4.127",
"v4.4.126",
"v4.4.125",
"v4.4.124",
"v4.4.123",
"v4.4.122",
"v4.4.121",
"v4.4.120",
"v4.4.119",
"v4.4.118",
"v4.4.117",
"v4.4.116",
"v4.4.115",
"v4.4.114",
"v4.4.113",
"v4.4.112",
"v4.4.111",
"v4.4.110",
"v4.4.109",
"v4.4.108",
"v4.4.107",
"v4.4.106",
"v4.4.105",
"v4.4.104",
"v4.4.103",
"v4.4.102",
"v4.4.101",
"v4.4.100",
"v4.4.99",
"v4.4.98",
"v4.4.97",
"v4.4.96",
"v4.4.95",
"v4.4.94",
"v4.4.93",
"v4.4.92",
"v4.4.91",
"v4.4.90",
"v4.4.89",
"v4.4.88",
"v4.4.87",
"v4.4.86",
"v4.4.85",
"v4.4.84",
"v4.4.83",
"v4.4.82",
"v4.4.81",
"v4.4.80",
"v4.4.79",
"v4.4.78",
"v4.4.77",
"v4.4.76",
"v4.4.75",
"v4.4.74",
"v4.4.73",
"v4.4.72",
"v4.4.71",
"v4.4.70",
"v4.4.69",
"v4.4.68",
"v4.4.67",
"v4.4.66",
"v4.4.65",
"v4.4.64",
"v4.4.63",
"v4.4.62",
"v4.4.61",
"v4.4.60",
"v4.4.59",
"v4.4.58",
"v4.4.57",
"v4.4.56",
"v4.4.55",
"v4.4.54",
"v4.4.53",
"v4.4.52",
"v4.4.51",
"v4.4.50",
"v4.4.49",
"v4.4.48",
"v4.4.47",
"v4.4.46",
"v4.4.45",
"v4.4.44",
"v4.4.43",
"v4.4.42",
"v4.4.41",
"v4.4.40",
"v4.4.39",
"v4.4.38",
"v4.4.37",
"v4.4.36",
"v4.4.35",
"v4.4.34",
"v4.4.33",
"v4.4.32",
"v4.4.31",
"v4.4.30",
"v4.4.29",
"v4.4.28",
"v4.4.27",
"v4.4.26",
"v4.4.25",
"v4.4.24",
"v4.4.23",
"v4.4.22",
"v4.4.21",
"v4.4.20",
"v4.4.19",
"v4.4.18",
"v4.6.7",
"v4.6.6"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-43892.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.7.0"
},
{
"fixed": "5.10.226"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.167"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.46"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.10.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-43892.json"
}
}
],
"modified": "2026-10-28T02:30:37.665012040Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/37a060b64ae83b76600d187d76591ce488ab836b",
"https://git.kernel.org/stable/c/51c0b1bb7541f8893ec1accba59eb04361a70946",
"https://git.kernel.org/stable/c/56fd70f4aa8b82199dbe7e99366b1fd7a04d86fb",
"https://git.kernel.org/stable/c/912736a0435ef40e6a4ae78197ccb5553cb80b05",
"https://git.kernel.org/stable/c/9972605a238339b85bd16b084eed5f18414d22db",
"https://git.kernel.org/stable/c/e6cc9ff2ac0b5df9f25eb790934c3104f6710278",
"https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/43xxx/CVE-2024-43892.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-43892",
"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/2024/43xxx/CVE-2024-43892.json"
}
},
"related_cves": [
{
"value": "CVE-2024-43892",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 504583,
"published_at": "2024-08-26T10:10:46.612+00:00"
}