Bug 2267737 (CVE-2023-52562) - CVE-2023-52562 kernel: mm/slab_common: slab_caches list corruption after kmem_cache_destroy()
Summary: CVE-2023-52562 kernel: mm/slab_common: slab_caches list corruption after kmem...
Keywords:
Status: NEW
Alias: CVE-2023-52562
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2267764
TreeView+ depends on / blocked
 
Reported: 2024-03-04 17:13 UTC by ybuenos
Modified: 2025-02-27 12:52 UTC (History)
51 users (show)

Fixed In Version: kernel 6.1.56, kernel 6.5.6, kernel 6.6
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description ybuenos 2024-03-04 17:13:33 UTC
In the Linux kernel, the following vulnerability has been resolved:

mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()

The Linux kernel CVE team has assigned CVE-2023-52562 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52562-da24@gregkh/T/#u

Comment 4 Audra Mitchell 2024-03-12 20:53:49 UTC
Fix for this issue already present in RHEL8 and RHEL9. Closing the jiras accordingly...

$ kerneloscope downstream 46a9ea668190
ff90662b28c9 (in rhel-9.4) mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()
5d0a1b57c9e0 (in rhel-8.10) mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()
b5c36ad3b85b (in rhel-8.8) mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()
bc29a3e15963 (in rhel-8.9) mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()
76b9c7632584 (in rhel-9.2) mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()
1c27e236e6a8 (in rhel-9.3) mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()

Comment 5 Alex 2024-06-09 16:48:01 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52562 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags DANGER INIT LEAK IMPROVEONLY  ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.


Note You need to log in before you can comment on or make changes to this bug.