CVE-2023-54267: powerpc/pseries: Rework lppaca_shared_proc() to avoid DEBUG_PREEMPT
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 2935443dc9c28499223d8c881474259e4b998f2a, 3c5e8e666794d7dde6d14ea846c6c04f2bb34900, 4c8568cf4c45b415854195c8832b557cdefba57a.
Low priority for now. Upgrade to Linux Linux 2935443dc9c28499223d8c881474259e4b998f2a, 3c5e8e666794d7dde6d14ea846c6c04f2bb34900, 4c8568cf4c45b415854195c8832b557cdefba57a 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: 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]
- Published
- Dec 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 3.12affected
- f13c13a005127b5dc5daaca190277a062d946e63 and later · before 953c54dfdc5d3eb7243ed902b50acb5ea1db4355affected · git
- f13c13a005127b5dc5daaca190277a062d946e63 and later · before 2935443dc9c28499223d8c881474259e4b998f2aaffected · git
- f13c13a005127b5dc5daaca190277a062d946e63 and later · before 4c8568cf4c45b415854195c8832b557cdefba57aaffected · git
- f13c13a005127b5dc5daaca190277a062d946e63 and later · before 3c5e8e666794d7dde6d14ea846c6c04f2bb34900affected · git
- f13c13a005127b5dc5daaca190277a062d946e63 and later · before f45ee5c074013a0fbfce77a5af5efddb01f5d4f4affected · git
- f13c13a005127b5dc5daaca190277a062d946e63 and later · before eac030b22ea12cdfcbb2e941c21c03964403c63faffected · git
- before 3.12not affected · semver
- 5.10.195 and later · up to and including 5.10.*not affected · semver
- 5.15.132 and later · up to and including 5.15.*not affected · semver
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.55-1 | 6.1.55-1 |
| Debian:13 | linux | before 6.5.3-1 | 6.5.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54265Dec 30, 2025 · ipv6: Fix an uninit variable access bug in __ip6_make_skb()0Monitor
- ← EarlierCVE-2023-54266Dec 30, 2025 · media: dvb-usb: m920x: Fix a potential memory leak in m920x_i2c_xfer()0Monitor
- Later →CVE-2023-54268Dec 30, 2025 · debugobjects: Don't wake up kswapd from fill_pool()0Monitor
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 | 2935443dc9c28499223d8c881474259e4b998f2a | Vendor (CNA) |
| Linux Linux | 3c5e8e666794d7dde6d14ea846c6c04f2bb34900 | Vendor (CNA) |
| Linux Linux | 4c8568cf4c45b415854195c8832b557cdefba57a | Vendor (CNA) |
| Linux Linux | 953c54dfdc5d3eb7243ed902b50acb5ea1db4355 | Vendor (CNA) |
| Linux Linux | eac030b22ea12cdfcbb2e941c21c03964403c63f | Vendor (CNA) |
| Linux Linux | f45ee5c074013a0fbfce77a5af5efddb01f5d4f4 | Vendor (CNA) |
| debian:linux | 6.1.55-1 · Debian:12 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3c5e8e666794d7dde6d14ea846c6c04f2bb34900
- git.kernel.org/stable/c/4c8568cf4c45b415854195c8832b557cdefba57a
- git.kernel.org/stable/c/953c54dfdc5d3eb7243ed902b50acb5ea1db4355
- git.kernel.org/stable/c/eac030b22ea12cdfcbb2e941c21c03964403c63f
- git.kernel.org/stable/c/f45ee5c074013a0fbfce77a5af5efddb01f5d4f4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.