CVE-2023-52598: s390/ptrace: handle setting of fpc register correctly
Noroxi assessment
Priority: Monitor (action score 28/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.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 02c6bbfb08bad78dd014e24c7b893723c15ec7a1, 28a1f492cb527f64593457a0a0f0d809b3f36c25, 6ccf904aac0292e1f6b1a1be6c407c414f7cf713.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 02c6bbfb08bad78dd014e24c7b893723c15ec7a1, 28a1f492cb527f64593457a0a0f0d809b3f36c25, 6ccf904aac0292e1f6b1a1be6c407c414f7cf713 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: 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().
- Published
- Mar 6, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-125
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 4.3affected
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before 6ccf904aac0292e1f6b1a1be6c407c414f7cf713affected · git
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before 6d0822f2cc9b153bf2df49a84599195a2e0d21a8affected · git
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before 856caf2730ea18cb39e95833719c02a02447dc0aaffected · git
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before 28a1f492cb527f64593457a0a0f0d809b3f36c25affected · git
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before 7a4d6481fbdd661f9e40e95febb95e3dee82bad3affected · git
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before 02c6bbfb08bad78dd014e24c7b893723c15ec7a1affected · git
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before bdce67df7f12fb0409fbc604ce7c4254703f56d4affected · git
- 9977e886cbbc758b4b601a160b5825ba573b5ca8 and later · before 8b13601d19c541158a6e18b278c00ba69ae37829affected · git
- before 4.3not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.307
- linux linux kernel4.20 and later · before 5.4.269
- linux linux kernel5.5 and later · before 5.10.210
- linux linux kernel5.11 and later · before 5.15.149
- linux linux kernel5.16 and later · before 6.1.77
- linux linux kernel6.2 and later · before 6.6.16
- linux linux kernel6.7 and later · before 6.7.4
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.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.7.7-1 | 6.7.7-1 |
| Red Hat:rhel_eus:9.4::appstream | bpftool-debuginfo | before 0:7.3.0-427.85.1.el9_4 | 0:7.3.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel-matched | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-doc | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-427.85.1.el9_4 | 0:5.14.0-427.85.1.el9_4 |
+56
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52596Mar 6, 2024 · sysctl: Fix out of bounds access for empty sysctl registers22Monitor
- ← EarlierCVE-2023-52597Mar 6, 2024 · KVM: s390: fix setting of fpc register16Monitor
- Later →CVE-2023-52599Mar 6, 2024 · jfs: fix array-index-out-of-bounds in diNewExt31Monitor
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 | 02c6bbfb08bad78dd014e24c7b893723c15ec7a1 | Vendor (CNA) |
| Linux Linux | 28a1f492cb527f64593457a0a0f0d809b3f36c25 | Vendor (CNA) |
| Linux Linux | 6ccf904aac0292e1f6b1a1be6c407c414f7cf713 | Vendor (CNA) |
| Linux Linux | 6d0822f2cc9b153bf2df49a84599195a2e0d21a8 | Vendor (CNA) |
| Linux Linux | 7a4d6481fbdd661f9e40e95febb95e3dee82bad3 | Vendor (CNA) |
| Linux Linux | 856caf2730ea18cb39e95833719c02a02447dc0a | Vendor (CNA) |
| Linux Linux | 8b13601d19c541158a6e18b278c00ba69ae37829 | Vendor (CNA) |
| Linux Linux | bdce67df7f12fb0409fbc604ce7c4254703f56d4 | Vendor (CNA) |
| debian:linux | 6.1.82-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.85.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
- TR-24-0176 · Mar 6, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/28a1f492cb527f64593457a0a0f0d809b3f36c25
- git.kernel.org/stable/c/6ccf904aac0292e1f6b1a1be6c407c414f7cf713
- git.kernel.org/stable/c/6d0822f2cc9b153bf2df49a84599195a2e0d21a8
- git.kernel.org/stable/c/7a4d6481fbdd661f9e40e95febb95e3dee82bad3
- git.kernel.org/stable/c/856caf2730ea18cb39e95833719c02a02447dc0a
- git.kernel.org/stable/c/8b13601d19c541158a6e18b278c00ba69ae37829
- git.kernel.org/stable/c/bdce67df7f12fb0409fbc604ce7c4254703f56d4
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.