CVE-2023-5676

Eclipse OpenJ9 possible infinite busy hang

Description

In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal (SIGTERM, SIGINT or SIGHUP) is received before the JVM has finished initializing.

Categories

4.1
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.04%
Vendor Advisory eclipse.org
Affected: Eclipse Foundation OpenJ9
Published at:
Updated at:

References

Link Tags
https://github.com/eclipse-openj9/openj9/pull/18085 patch issue tracking
https://gitlab.eclipse.org/security/cve-assignement/-/issues/13 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2023-5676?
CVE-2023-5676 has been scored as a medium severity vulnerability.
How to fix CVE-2023-5676?
To fix CVE-2023-5676, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-5676 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-5676 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-5676?
CVE-2023-5676 affects Eclipse Foundation OpenJ9.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.