Skip to main content
CVE-2025-65001VulnerabilityPublished Updated

CVE-2025-65001: Fujitsu fbiosdrv.sys · Out-of-bounds Write

Affects Fujitsu fbiosdrv.sysSource CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.2High
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:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Fujitsu fbiosdrv.sysAffected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2025-65001, organizations should implement the following specific measures: 1) Immediately inventory and identify all systems running vulnerable versions of the Fujitsu fbiosdrv.sys driver. 2) Restrict local administrative access to trusted personnel only, minimizing the risk of privilege abuse. 3) Employ strict access controls and monitoring on systems with the vulnerable driver to detect unusual activities indicative of exploitation attempts. 4) Use endpoint detection and response (EDR) tools capable of identifying anomalous behavior related to memory corruption or driver manipulation. 5) Apply vendor patches or updates as soon as they become available; if patches are not yet released, consider temporary workarounds such as disabling or restricting the driver if feasible without impacting critical operations. 6) Conduct regular security audits and penetration tests focusing on privilege escalation vectors. 7) Educate system administrators about the risks of local privilege misuse and the importance of maintaining least privilege principles. 8) Maintain up-to-date backups and incident response plans to recover quickly in case of exploitation.

Description

Fujitsu fbiosdrv.sys before 2.5.0.0 allows an attacker to potentially affect system confidentiality, integrity, and availability.

References

Community reviews

Loading reviews…