CVE-2023-54267 Details
Description
In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Rework lppaca_shared_proc() to avoid DEBUG_PREEMPT lppaca_shared_proc() takes a pointer to the lppaca which is typically accessed through get_lppaca(). With DEBUG_PREEMPT enabled, this leads to checking if preemption is enabled, for example: BUG: using smp_processor_id() in preemptible [00000000] code: grep/10693 caller is lparcfg_data+0x408/0x19a0 CPU: 4 PID: 10693 Comm: grep Not tainted 6.5.0-rc3 #2 Call Trace: dump_stack_lvl+0x154/0x200 (unreliable) check_preemption_disabled+0x214/0x220 lparcfg_data+0x408/0x19a0 ... This isn't actually a problem however, as it does not matter which lppaca is accessed, the shared proc state will be the same. vcpudispatch_stats_procfs_init() already works around this by disabling preemption, but the lparcfg code does not, erroring any time /proc/powerpc/lparcfg is accessed with DEBUG_PREEMPT enabled. Instead of disabling preemption on the caller side, rework lppaca_shared_proc() to not take a pointer and instead directly access the lppaca, bypassing any potential preemption checks. [mpe: Rework to avoid needing a definition in paca.h and lppaca.h]
A vulnerability has been identified in the Linux kernel's PowerPC pseries platform, specifically within the LPPACA shared processor handling. The issue arises when the DEBUG_PREEMPT feature is enabled, leading to improper preemption management. This can cause errors when accessing certain procfs entries related to the lparcfg configuration, as the shared processor state is not correctly synchronized across CPUs. The vulnerability stems from the lppaca_shared_proc() function, which originally accepted a pointer to the LPPACA structure but failed to account for preemption, potentially leading to inconsistent processor state checks. The problem is exacerbated in the lparcfg data handling, which does not disable preemption before accessing shared processor information, unlike other parts of the code that have implemented a workaround.
The vulnerability has been addressed by modifying the lppaca_shared_proc() function to directly access the LPPACA structure without using a pointer, thereby avoiding preemption-related issues. Users should update to the latest version of the Linux kernel where this fix has been applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 30, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2935443dc9c28499223d8c881474259e4b998f2a | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/3c5e8e666794d7dde6d14ea846c6c04f2bb34900 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/4c8568cf4c45b415854195c8832b557cdefba57a | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/953c54dfdc5d3eb7243ed902b50acb5ea1db4355 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/eac030b22ea12cdfcbb2e941c21c03964403c63f | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/f45ee5c074013a0fbfce77a5af5efddb01f5d4f4 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 30, 2025 | New CVE Received | kernel.org |
Volerion