CVE-2023-52597

KVM: s390: fix setting of fpc register

State
Published
Severity
4.0 Medium
Published
Mar 6, 2024
Updated
May 11, 2026
Reserved
Mar 2, 2024

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

KVM: s390: fix setting of fpc register

kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control (fpc) register of a guest cpu. 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 host 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 / host process fpc register value, however it will be discarded, when returning to user space.

In result the host process will incorrectly continue to run with the value that was supposed to be used for a guest cpu.

Fix this by simply removing the test. There is another test right before the SIE context is entered which will handles invalid values.

This results in a change of behaviour: invalid values will now be accepted instead of that the ioctl fails with -EINVAL. This seems to be acceptable, given that this interface is most likely not used anymore, and this is in addition the same behaviour implemented with the memory mapped interface (replace invalid values with zero) - see sync_regs() in kvm-s390.c.

Scores

CVSSScoreVectorSource
3.14.0 MediumCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LCISA-ADP

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before 3a04410b0bc7e056e0843ac598825dd359246d18Affected
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before 5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1Affected
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before 150a3a3871490e8c454ffbac2e60abeafcecff99Affected
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before 732a3bea7aba5b15026ea42d14953c3425cc7dc2Affected
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before 0671f42a9c1084db10d68ac347d08dbf6689ecb3Affected
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before c87d7d910775a025e230fd6359b60627e392460fAffected
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before 2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7Affected
  • 4725c86055f5bbdcdfe47199c0715881893a2c79 to before b988b1bb0053c0dcd26187d29ef07566a565cf55Affected
LinuxLinux
  • 3.13Affected
  • before 3.13Not affected
  • 4.19.307 through 4.19.*Not affected
  • 5.4.269 through 5.4.*Not affected
  • 5.10.210 through 5.10.*Not affected
  • 5.15.149 through 5.15.*Not affected
  • 6.1.77 through 6.1.*Not affected
  • 6.6.16 through 6.6.*Not affected
  • 6.7.4 through 6.7.*Not affected
  • 6.8 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.