Tracer state corruption via interrupt-driven FPC race
Published Mar 6, 2024 · Updated May 11, 2026
Race condition in Linux kernel 4.3 through 6.7.3 allows local users on s390 systems to corrupt a tracer's floating-point control state. In arch/s390/kernel/ptrace.c, test_fp_ctl() loads the traced process's FPC value before preserving the tracer's FP/VX registers, so an interrupt can save the wrong state. Exploitation requires ptrace access and an interrupt that uses floating-point or vector registers; the tracer then resumes with attacker-supplied FPC state, exposing data or interrupting service.
Summary
What happened
Race condition in Linux kernel 4.3 through 6.7.3 allows local users on s390 systems to corrupt a tracer's floating-point control state. In arch/s390/kernel/ptrace.c, test_fp_ctl() loads the traced process's FPC value before preserving the tracer's FP/VX registers, so an interrupt can save the wrong state. Exploitation requires ptrace access and an interrupt that uses floating-point or vector registers; the tracer then resumes with attacker-supplied FPC state, exposing data or interrupting service.
The record
- CVE
- CVE-2023-52598
- Published
- Mar 6, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.3
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <02c6bbfb08bad78dd014e24c7b893723c15ec7a1
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <28a1f492cb527f64593457a0a0f0d809b3f36c25
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <6ccf904aac0292e1f6b1a1be6c407c414f7cf713
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <6d0822f2cc9b153bf2df49a84599195a2e0d21a8
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <7a4d6481fbdd661f9e40e95febb95e3dee82bad3
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <856caf2730ea18cb39e95833719c02a02447dc0a
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <8b13601d19c541158a6e18b278c00ba69ae37829
- Affected versionversion=9977e886cbbc758b4b601a160b5825ba573b5ca8 <bdce67df7f12fb0409fbc604ce7c4254703f56d4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo