CVE-2023-52597

一、漏洞信息
 漏洞编号：[CVE-2023-52597](https://nvd.nist.gov/vuln/detail/CVE-2023-52597)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0
 CVSS V2.0分值：
 BaseScore：0.0 Low
 Vector：CVSS：2.0/
 漏洞简述：
 In the Linux kernel, the following vulnerability has been resolved:KVM: s390: fix setting of fpc registerkvm_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 bytemporarily 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 fpcregister, and within interrupt context floating point or vector registersare 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 registerswhen returning to user space.test_fp_ctl() restores the original user space / host process fpc registervalue, however it will be discarded, when returning to user space.In result the host process will incorrectly continue to run with the valuethat was supposed to be used for a guest cpu.Fix this by simply removing the test. There is another test right beforethe SIE context is entered which will handles invalid values.This results in a change of behaviour: invalid values will now be acceptedinstead 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 inaddition the same behaviour implemented with the memory mapped interface(replace invalid values with zero) - see sync_regs() in kvm-s390.c.
 漏洞公开时间：2024-03-06 15:15:09
 漏洞创建时间：2024-03-06 23:41:14
 漏洞详情参考链接：
 https://nvd.nist.gov/vuln/detail/CVE-2023-52597
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52597 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52597 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| suse_bugzilla | https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99 | https://bugzilla.suse.com/show_bug.cgi?id=1221040 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52597-2ed6@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2268311 |
| ubuntu | https://git.kernel.org/linus/b988b1bb0053c0dcd26187d29ef07566a565cf55 (6.8-rc1) | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://ubuntu.com/security/notices/USN-6688-1 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52597 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52597 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52597 | https://ubuntu.com/security/CVE-2023-52597 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52597 | https://ubuntu.com/security/CVE-2023-52597 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2023-52597 |
| cve_search |  | https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18 |
| cve_search |  | https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1 |
| cve_search |  | https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99 |
| cve_search |  | https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2 |
| cve_search |  | https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3 |
| cve_search |  | https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f |
| cve_search |  | https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7 |
| cve_search |  | https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55 |
| ubuntu | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52597 | https://ubuntu.com/security/CVE-2023-52597 |

</details>

漏洞分析指导链接：
 https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
 openBrain开源漏洞感知系统
 漏洞补丁信息：
 <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/b988b1bb0053c0dcd26187d29ef07566a565cf55 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
      In the Linux kernel, the following vulnerability has been resolved:KVM: s390: fix setting of fpc registerkvm_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 bytemporarily 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 fpcregister, and within interrupt context floating point or vector registersare 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 registerswhen returning to user space.test_fp_ctl() restores the original user space / host process fpc registervalue, however it will be discarded, when returning to user space.In result the host process will incorrectly continue to run with the valuethat was supposed to be used for a guest cpu.Fix this by simply removing the test. There is another test right beforethe SIE context is entered which will handles invalid values.This results in a change of behaviour: invalid values will now be acceptedinstead 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 inaddition the same behaviour implemented with the memory mapped interface(replace invalid values with zero) - see sync_regs() in kvm-s390.c.  
 openEuler评分：
  4.7
 Vector：CVSS：2.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP1(4.19.90):受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
3.openEuler-22.03-LTS(5.10.0):受影响
4.openEuler-22.03-LTS-SP1(5.10.0):受影响
5.openEuler-22.03-LTS-SP2(5.10.0):受影响
6.openEuler-22.03-LTS-SP3(5.10.0):受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next(5.10.0):不受影响
9.openEuler-24.03-LTS:不受影响
10.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4(4.19.90):否
3.openEuler-22.03-LTS(5.10.0):否
4.openEuler-22.03-LTS-SP1(5.10.0):否
5.openEuler-22.03-LTS-SP2(5.10.0):否
6.openEuler-22.03-LTS-SP3(5.10.0):否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next(5.10.0):否
9.openEuler-24.03-LTS:否
10.openEuler-24.03-LTS-Next:否

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1487

@yangyingliang ,@gatieme ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 
**issue处理注意事项:** 
**1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;**
**2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;**
**3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.**
************************************************************************
影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响): 
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):

修复是否涉及abi变化(是/否)：
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):

-----------------------------------------------------------------------
issue处理具体操作请参考: 
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

<table><tr><th white-space: nowrap;>参考网址</th> <th white-space: nowrap;>关联pr</th> <th white-space: nowrap;>状态</th> <th white-space: nowrap;>补丁链接</th></tr><tr><td rowspan="1">https://nvd.nist.gov/vuln/detail/CVE-2023-52597</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18>https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18</a> <a href=https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f>https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f</a> <a href=https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1>https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1</a> <a href=https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55>https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55</a> <a href=https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99>https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99</a> <a href=https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7>https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7</a> <a href=https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3>https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3</a> <a href=https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2>https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2</a></td></tr><tr><td>https://ubuntu.com/security/CVE-2023-52597</td><td></td><td></td><td></td></tr><tr><td rowspan="1">https://www.opencve.io/cve/CVE-2023-52597</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18>https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18</a> <a href=https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f>https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f</a> <a href=https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1>https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1</a> <a href=https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55>https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55</a> <a href=https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99>https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99</a> <a href=https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7>https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7</a> <a href=https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3>https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3</a> <a href=https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2>https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2</a></td></tr><tr><td>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2023-52597</td><td></td><td></td><td></td></tr><tr><td rowspan="1">https://security-tracker.debian.org/tracker/CVE-2023-52597</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/linus/b988b1bb0053c0dcd26187d29ef07566a565cf55>https://git.kernel.org/linus/b988b1bb0053c0dcd26187d29ef07566a565cf55</a></td></tr></table>

> 说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用[CVE补丁工具](https://gitee.com/openeuler/cve-manager/blob/master/cve-agency-manager/cve_tracking/README.md)。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

CVE-2023-52597

影响性分析说明：
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.

openEuler评分:(评分和向量)
4.7
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1(4.19.90):受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS:受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:受影响
6.openEuler-22.03-LTS-SP3:受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next:受影响
9.openEuler-24.03-LTS:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS:否
4.openEuler-22.03-LTS-SP1:否
5.openEuler-22.03-LTS-SP2:否
6.openEuler-22.03-LTS-SP3:否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next:否
9.openEuler-24.03-LTS:否

@ 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:KVM: s390: fix setting of fpc registerkvm_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 bytemporarily 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 fpcregister, and within interrupt context floating point or vector registersare 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 registerswhen returning to user space.test_fp_ctl() restores the original user space / host process fpc registervalue, however it will be discarded, when returning to user space.In result the host process will incorrectly continue to run with the valuethat was supposed to be used for a guest cpu.Fix this by simply removing the test. There is another test right beforethe SIE context is entered which will handles invalid values.This results in a change of behaviour: invalid values will now be acceptedinstead 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 inaddition the same behaviour implemented with the memory mapped interface(replace invalid values with zero) - see sync_regs() in kvm-s390.c.|
|已分析|2.openEulerScore|4.7|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP2:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-Next:受影响,master:不受影响,openEuler-24.03-LTS:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否|

**请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.**

CVE-2023-52597

影响性分析说明：
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.

openEuler评分:(评分和向量)
4.7
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1:受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS:受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:受影响
6.openEuler-22.03-LTS-SP3:受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next:不受影响
9.openEuler-24.03-LTS:不受影响
10.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS:否
4.openEuler-22.03-LTS-SP1:否
5.openEuler-22.03-LTS-SP2:否
6.openEuler-22.03-LTS-SP3:否
7.master(6.1.0):否
8.openEuler-22.03-LTS-Next:否
9.openEuler-24.03-LTS:否
10.openEuler-24.03-LTS-Next:否

===========================================================