LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52597: KVM: s390: fix setting of fpc register

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.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52597 is a Linux kernel KVM issue specific to s390 virtualization. A guest CPU floating-point control register operation could accidentally affect the host process state under interrupt timing. The expected business impact is limited integrity or availability disruption on affected s390 KVM hosts, not broad remote compromise.

Executive priority

Treat as a moderate maintenance priority for organizations operating s390 KVM virtualization. It does not currently warrant emergency response absent vendor escalation or exploitation evidence, but kernel updates should be scheduled promptly for affected hosts.

Technical view

In kvm_arch_vcpu_ioctl_set_fpu() for KVM s390, the kernel temporarily loaded a guest fpc value to validate it. If interrupted while floating-point or vector state was saved, the host process could later resume with the guest-intended fpc value. The fix removes that validation test and relies on later SIE-entry handling.

Likely exposure

Exposure is likely limited to Linux systems on s390/s390x using KVM. The CVE record lists Linux kernel versions including 3.13 and stable series up to 6.8 as affected, with multiple stable commits referenced. Non-s390 environments are not described as affected in the provided sources.

Exploitation context

The CVSS vector is local, high complexity, no privileges, no user interaction, with low integrity and availability impact. CISA KEV status is false in the provided data, and the sources do not report active exploitation or public exploit availability.

Researcher notes

The key race involves temporary fpc loading during ioctl validation and interrupt-time fp/vx state handling. The fix changes behavior: invalid values may be accepted at ioctl time and handled later before SIE entry, aligning with the memory-mapped interface behavior described in the CVE text.

Mitigation direction

  • Apply Linux kernel stable or vendor packages containing the referenced KVM s390 fix.
  • Prioritize s390 KVM hosts running affected 3.13 through listed stable branches.
  • If using Debian LTS, review the June 2024 advisory and update packages.
  • Where patch timing is unclear, follow your Linux vendor's CVE-2023-52597 guidance.

Validation and detection

  • Identify IBM s390/s390x Linux systems with KVM enabled.
  • Record running kernel release and vendor package version.
  • Check whether the referenced stable commit or equivalent backport is present.
  • Verify updated hosts boot into the fixed kernel.
  • Review virtualization workloads for unusual host process instability if exposure existed.
Prepared
Confidence
high
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52597 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L1.42.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

4Medium
CVSS 3.1 vector shape for CVE-2023-52597Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4725c86055f5bbdcdfe47199c0715881893a2c79, 4725c86055f5bbdcdfe47199c0715881893a2c79, 4725c86055f5bbdcdfe47199c0715881893a2c79, 4725c86055f5bbdcdfe47199c0715881893a2c79, 4725c86055f5bbdcdfe47199c0715881893a2c79, 4725c86055f5bbdcdfe47199c0715881893a2c79, 4725c86055f5bbdcdfe47199c0715881893a2c79, 4725c86055f5bbdcdfe47199c0715881893a2c79unaffected
LinuxLinux3.13, 0, 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.