CVE-2023-52562: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()
Noroxi assessment
Priority: Monitor (action score 22/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.22% (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 46a9ea6681907a3be6b6b0d43776dccc62cad6cf, 5.20, 51988be187b041e5355245957b0b9751fa382e0d.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 46a9ea6681907a3be6b6b0d43776dccc62cad6cf, 5.20, 51988be187b041e5355245957b0b9751fa382e0d 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/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (next=ffff89f595a1b268) [ 1041.219165] ------------[ cut here ]------------ [ 1041.221517] kernel BUG at lib/list_debug.c:62! [ 1041.223452] invalid opcode: 0000 [#1] PREEMPT SMP PTI [ 1041.225408] CPU: 2 PID: 1852 Comm: rmmod Kdump: loaded Tainted: G B W OE 6.5.0 #15 [ 1041.228244] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20230524-3.fc37 05/24/2023 [ 1041.231212] RIP: 0010:__list_del_entry_valid+0xae/0xb0 Another quick way to trigger this issue, in a kernel with CONFIG_SLUB=y, is to set slub_debug to poison the released objects and then just run cat /proc/slabinfo after removing the module that leaks slab objects, in which case the kernel will panic: [ 50.954843] general protection fault, probably for non-canonical address 0xa56b6b6b6b6b6b8b: 0000 [#1] PREEMPT SMP PTI [ 50.961545] CPU: 2 PID: 1495 Comm: cat Kdump: loaded Tainted: G B W OE 6.5.0 #15 [ 50.966808] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20230524-3.fc37 05/24/2023 [ 50.972663] RIP: 0010:get_slabinfo+0x42/0xf0 This patch fixes this issue by properly checking shutdown_cache()'s return value before taking the kmem_cache_release() branch.
- Published
- Mar 2, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 357321557920c805de2b14832002465c320eea4f, 6.0affected
- 0495e337b7039191dfce6e03f5f830454b1fae6b and later · before a5569bb187521432f509b69dda7d29f78b2d38b0affected · git
- 0495e337b7039191dfce6e03f5f830454b1fae6b and later · before 51988be187b041e5355245957b0b9751fa382e0daffected · git
- 0495e337b7039191dfce6e03f5f830454b1fae6b and later · before 46a9ea6681907a3be6b6b0d43776dccc62cad6cfaffected · git
- 5.19.8 and later · before 5.20affected · semver
- before 6.0not affected · semver
- 6.1.56 and later · up to and including 6.1.*not affected · semver
- 6.5.6 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.0 and later · before 6.1.56
- linux linux kernel6.2 and later · before 6.5.6
- linux linux kernel6.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.64-1 | 6.1.64-1 |
| Debian:13 | linux | before 6.5.6-1 | 6.5.6-1 |
| Red Hat:enterprise_linux:8::baseos | bpftool | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | bpftool-debuginfo | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-abi-stablelists | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-core | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-core | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-debuginfo | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-devel | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules-extra | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-aarch64 | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-ppc64le | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-s390x | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-devel | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-doc | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules-extra | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools-debuginfo | before 0:4.18.0-513.9.1.el8_9 | 0:4.18.0-513.9.1.el8_9 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52559Mar 2, 2024 · iommu/vt-d: Avoid memory allocation in iommu_suspend()22Monitor
- ← EarlierCVE-2023-52560Mar 2, 2024 · mm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions()22Monitor
- Later →CVE-2023-52563Mar 2, 2024 · drm/meson: fix memory leak on ->hpd_notify callback22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 46a9ea6681907a3be6b6b0d43776dccc62cad6cf | Vendor (CNA) |
| Linux Linux | 5.20 | Vendor (CNA) |
| Linux Linux | 51988be187b041e5355245957b0b9751fa382e0d | Vendor (CNA) |
| Linux Linux | a5569bb187521432f509b69dda7d29f78b2d38b0 | Vendor (CNA) |
| debian:linux | 6.1.64-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0160 · Mar 4, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.