CVE-2023-52598: s390/ptrace: handle setting of fpc register correctly
In the Linux kernel, the following vulnerability has been resolved:
s390/ptrace: handle setting of fpc register correctly
If the content of the floating point control (fpc) register of a traced
process is modified with the ptrace interface the new value is tested for
validity by temporarily loading it into the fpc register.
This may lead to corruption of the fpc register of the tracing process:
if an interrupt happens while the value is temporarily loaded into the
fpc register, and within interrupt context floating point or vector
registers are used, the current fp/vx registers are saved with
save_fpu_regs() assuming they belong to user space and will be loaded into
fp/vx registers when returning to user space.
test_fp_ctl() restores the original user space fpc register value, however
it will be discarded, when returning to user space.
In result the tracer will incorrectly continue to run with the value that
was supposed to be used for the traced process.
Fix this by saving fpu register contents with save_fpu_regs() before using
test_fp_ctl().
Security readout for executives and security teams
Plain-English summary
CVE-2023-52598 is a Linux kernel bug affecting IBM s390 systems using ptrace. A traced process setting a floating-point control register can corrupt the tracer process’s floating-point state during an interrupt. This appears to be a local correctness and stability issue, not a remote attack path.
Executive priority
Handle through normal kernel patch management, with higher priority for shared s390 hosts or environments allowing local user code. There is no sourced evidence of remote exploitation or active attacks.
Technical view
In Linux s390 ptrace handling, test_fp_ctl() temporarily loads a traced process fpc value for validation. If an interrupt uses floating-point or vector state during that window, save_fpu_regs() may save the wrong state for the tracer. Stable kernel fixes save FPU registers before testing the new fpc value.
Likely exposure
Exposure is limited to Linux kernels on s390 architecture where ptrace can modify traced process fpc state. General x86 or non-s390 Linux systems are not indicated by the provided sources.
Exploitation context
No cited source reports active exploitation, and this CVE is not marked KEV. Practical impact likely requires local ptrace capability over a process, making exposure narrower than network-reachable kernel flaws.
Researcher notes
The CVE record provides no CVSS, CWE, or exploit indicators. Affected-version data in the bundle is limited and commit-oriented. Treat vendor kernel advisories as authoritative for exact package exposure and fixed builds.
Mitigation direction
Update affected s390 Linux kernels using vendor or distribution guidance.
Apply the relevant upstream stable kernel commit for your maintained branch.
For Debian LTS systems, review and apply the June 2024 linux security update.
Prioritize systems where untrusted users can run or debug local processes.
Validation and detection
Inventory Linux systems running on s390 architecture.
Compare kernel version and vendor build against CVE-2023-52598 advisories.
Confirm the applicable upstream stable fix is present in the kernel source or package changelog.
Check Debian LTS hosts for the referenced June 2024 kernel update.
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-52598 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.