VulnerabilityPublished 16 Oct 2025Updated 17 Oct 2025

CVE-2025-61554: Divide By Zero

Source CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor official BitVisor channels for patches addressing CVE-2025-61554 and apply updates promptly once available. 2. Restrict local access to hypervisor management interfaces and hosts running BitVisor to trusted personnel only, minimizing the risk of local exploitation. 3. Implement strict access controls and auditing on systems hosting BitVisor to detect and prevent unauthorized local activities. 4. Consider network segmentation and isolation of hypervisor hosts to limit exposure to potentially malicious local users. 5. Employ runtime monitoring tools capable of detecting abnormal PCI configuration space accesses or unusual hypervisor behavior. 6. Develop and test incident response plans for hypervisor crashes to reduce downtime and data loss. 7. Evaluate the necessity of using BitVisor in production environments and consider alternative hypervisors with broader support and security track records if appropriate. 8. Educate system administrators and security teams about the vulnerability and the importance of local access controls.

Description

A divide-by-zero in VirtIO network device emulation in BitVisor from commit 108df6 (2020-05-20) to commit 480907 (2025-07-06) allows local attackers to cause a denial of service (host hypervisor crash) via a crafted PCI configuration space access.

Impact

For European organizations, the primary impact of CVE-2025-61554 is the potential for denial of service on systems running BitVisor hypervisor with VirtIO network device emulation. This can lead to unplanned downtime of virtualized environments, affecting business continuity, especially in sectors relying on virtualization for critical workloads such as finance, telecommunications, and research institutions. Although the vulnerability does not compromise data confidentiality or integrity, the loss of availability can disrupt services and operations. Organizations using BitVisor in development, testing, or production environments could experience hypervisor crashes triggered by malicious or accidental crafted PCI configuration space accesses. Given the local attack vector, insider threats or compromised local accounts pose a significant risk. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as the vulnerability is publicly known and may attract attackers. The impact is heightened in environments where BitVisor is used to isolate sensitive workloads or where rapid recovery from hypervisor crashes is challenging.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Oct 2025, 00:50 UTC

WeaknessesCWE-369

Technical details

References

Community reviews

Related threats