CVE-2023-27306
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Initialization in firmware for some Intel(R) Optane(TM) SSD products may allow an authenticated user to potentially enable denial of service via local access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper initialization in Intel Optane SSD firmware allows an authenticated local user to potentially cause a denial of service condition. The vulnerability stems from the firmware failing to properly initialize certain parameters or states during startup, which can be exploited to render the SSD unavailable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< u4110553-g004< e2010650< e2010650< e2010650< e2010650CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Intel Optane SSD model presentUse system inventory tools (e.g., device manager on Windows, lspci or nvme list on Linux) to enumerate installed SSDs and identify Intel Optane models. Look specifically for: Optane Memory H20, Optane SSD 900p, Optane SSD 905p, Optane SSD DC P4800x, or Optane SSD DC P4801xAffected if Any of the affected Intel Optane SSD models (H20, 900p, 905p, P4800x, P4801x) is present in the system
-
Retrieve current firmware versionQuery the SSD firmware version using Intel SSD Toolbox, Intel Memory and Storage Tool, or command-line tools such as 'nvme id-ctrl /dev/nvme0' on Linux. On Windows, use 'smartctl -a /dev/sda' or the Intel tool. Note the firmware revision field returnedAffected if Firmware version cannot be retrieved or the device does not report a firmware version
-
Compare version against vulnerability thresholdsCompare the installed firmware version to the affected ranges: For Optane H20, any version below u4110553-g004 is affected. For Optane 900p, 905p, DC P4800x, and DC P4801x, any version below e2010650 is affectedAffected if Installed firmware version is lower than u4110553-g004 (for H20) or lower than e2010650 (for 900p/905p/P4800x/P4801x)
If an Intel Optane SSD from the affected product list is present and its firmware version is below the specified thresholds, the environment is vulnerable to CVE-2023-27306
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the latest Intel Optane SSD firmware update from Intel's support website. Verify the firmware version on affected systems and test the update in a controlled environment before broad deployment.
Optane Memory H20: firmware u4110553-g004 or later | Optane SSD 900p/905p/DC P4800x/DC P4801x: firmware e2010650 or later
- 1. Identify the exact Intel Optane SSD model number on the affected system
- 2. Download the latest firmware version from Intel's support website (support.intel.com) for the specific Optane SSD model
- 3. Use Intel SSD Toolbox or Intel Memory and Storage Tool to apply the firmware update
- 4. Follow the firmware update wizard and ensure uninterrupted power during the update process
- 5. Reboot the system after the update completes
- 6. Verify the installed firmware version matches the fixed release (u4110553-g004 for H20, or e2010650 for 900p/905p/P4800x/P4801x)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-27306 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data