You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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().
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
OR
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 4.19.307
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.269
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.210
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.149
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.77
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.16
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.7.4
Changed
Reference Type
https://git.kernel.org/stable/c/02c6bbfb08bad78dd014e24c7b893723c15ec7a1 No Types Assigned
New CVE Received from kernel.org3/06/2024 2:15:09 AM
Action
Type
Old Value
New Value
Added
Description
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().
Added
Reference
Linux https://git.kernel.org/stable/c/02c6bbfb08bad78dd014e24c7b893723c15ec7a1 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/28a1f492cb527f64593457a0a0f0d809b3f36c25 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/6ccf904aac0292e1f6b1a1be6c407c414f7cf713 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/6d0822f2cc9b153bf2df49a84599195a2e0d21a8 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/7a4d6481fbdd661f9e40e95febb95e3dee82bad3 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/856caf2730ea18cb39e95833719c02a02447dc0a [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/8b13601d19c541158a6e18b278c00ba69ae37829 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/bdce67df7f12fb0409fbc604ce7c4254703f56d4 [No types assigned]
Quick Info
CVE Dictionary Entry: CVE-2023-52598 NVD
Published Date: 03/06/2024 NVD
Last Modified: 06/17/2026
Source: kernel.org