LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52451: powerpc/pseries/memhp: Fix access beyond end of drmem array

In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries/memhp: Fix access beyond end of drmem array dlpar_memory_remove_by_index() may access beyond the bounds of the drmem lmb array when the LMB lookup fails to match an entry with the given DRC index. When the search fails, the cursor is left pointing to &drmem_info->lmbs[drmem_info->n_lmbs], which is one element past the last valid entry in the array. The debug message at the end of the function then dereferences this pointer: pr_debug("Failed to hot-remove memory at %llx\n", lmb->base_addr); This was found by inspection and confirmed with KASAN: pseries-hotplug-mem: Attempting to hot-remove LMB, drc index 1234 ================================================================== BUG: KASAN: slab-out-of-bounds in dlpar_memory+0x298/0x1658 Read of size 8 at addr c000000364e97fd0 by task bash/949 dump_stack_lvl+0xa4/0xfc (unreliable) print_report+0x214/0x63c kasan_report+0x140/0x2e0 __asan_load8+0xa8/0xe0 dlpar_memory+0x298/0x1658 handle_dlpar_errorlog+0x130/0x1d0 dlpar_store+0x18c/0x3e0 kobj_attr_store+0x68/0xa0 sysfs_kf_write+0xc4/0x110 kernfs_fop_write_iter+0x26c/0x390 vfs_write+0x2d4/0x4e0 ksys_write+0xac/0x1a0 system_call_exception+0x268/0x530 system_call_vectored_common+0x15c/0x2ec Allocated by task 1: kasan_save_stack+0x48/0x80 kasan_set_track+0x34/0x50 kasan_save_alloc_info+0x34/0x50 __kasan_kmalloc+0xd0/0x120 __kmalloc+0x8c/0x320 kmalloc_array.constprop.0+0x48/0x5c drmem_init+0x2a0/0x41c do_one_initcall+0xe0/0x5c0 kernel_init_freeable+0x4ec/0x5a0 kernel_init+0x30/0x1e0 ret_from_kernel_user_thread+0x14/0x1c The buggy address belongs to the object at c000000364e80000 which belongs to the cache kmalloc-128k of size 131072 The buggy address is located 0 bytes to the right of allocated 98256-byte region [c000000364e80000, c000000364e97fd0) ================================================================== pseries-hotplug-mem: Failed to hot-remove memory at 0 Log failed lookups with a separate message and dereference the cursor only when it points to a valid entry.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52451 is a Linux kernel bug in PowerPC pseries memory hot-remove handling. A failed memory block lookup can make the kernel read just past an internal array while logging a debug message. The evidence points to a platform-specific kernel issue, not a broad internet-facing service flaw.

Executive priority

Treat this as a targeted infrastructure maintenance issue. It deserves patch tracking for affected PowerPC pseries estates, but current sources do not support emergency prioritization for typical x86 Linux servers or internet-facing applications.

Technical view

In dlpar_memory_remove_by_index(), a failed DRC index search leaves the cursor at drmem_info->lmbs[n_lmbs]. The function then dereferences lmb->base_addr for pr_debug, causing a slab out-of-bounds read confirmed by KASAN. Kernel stable commits change failed lookup logging to avoid dereferencing an invalid cursor.

Likely exposure

Exposure appears limited to Linux on PowerPC pseries systems using DLPAR memory hotplug. The call trace shows a sysfs write path, but the source bundle does not state required privileges, default reachability, or whether debugging must be enabled for impact.

Exploitation context

The source bundle says the bug was found by inspection and confirmed with KASAN. It does not cite public exploitation, and KEV is false. No exploit path, weaponized proof, or remotely reachable scenario is provided.

Researcher notes

The incomplete pieces are impact severity, access requirements, and practical exploitability. The strongest evidence is the KASAN out-of-bounds read on a failed DRC index lookup and the upstream stable fixes. Avoid broad claims beyond pseries memory hotplug exposure.

Mitigation direction

  • Apply the relevant Linux stable kernel fix for your maintained branch.
  • Prioritize affected PowerPC pseries hosts that use memory hotplug operations.
  • Check Debian LTS or vendor kernel advisories for packaged fixed versions.
  • If patching is delayed, review vendor guidance for operational workarounds.

Validation and detection

  • Inventory Linux PowerPC pseries systems and kernel versions.
  • Confirm whether pseries DLPAR memory hotplug is used or exposed operationally.
  • Verify the kernel includes one of the referenced stable commits.
  • Review kernel or distribution advisory status for CVE-2023-52451.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52451 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux51925fb3c5c901aa06cdc853268a6e19e19bcdc7, 51925fb3c5c901aa06cdc853268a6e19e19bcdc7, 51925fb3c5c901aa06cdc853268a6e19e19bcdc7, 51925fb3c5c901aa06cdc853268a6e19e19bcdc7, 51925fb3c5c901aa06cdc853268a6e19e19bcdc7, 51925fb3c5c901aa06cdc853268a6e19e19bcdc7, 51925fb3c5c901aa06cdc853268a6e19e19bcdc7, 51925fb3c5c901aa06cdc853268a6e19e19bcdc7unaffected
LinuxLinux4.1, 0, 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.