CVE-2022-32230Public exploitNetwork attack vector

Kernel crash via unchecked SMBv3 device pointer

Published Jun 14, 2022 · Updated Sep 16, 2024

NULL pointer dereference in Windows SMBv3 before the April 2022 patches allows attackers to crash and reboot the Windows kernel. The srv2!Smb2ValidateVolumeObjectsMatch function dereferences a nullable PDEVICE_OBJECT and passes it to IoGetBaseFileSystemDeviceObject while handling a crafted FileNormalizedNameInformation query on a named pipe. Access normally requires an authenticated IPC$ named-pipe session or non-default guest access, but domain controllers expose anonymously openable pipes; exploitation causes a BSOD and normally an automatic reboot.

CVSS severity7.5
High
EPSS probability7.53%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

NULL pointer dereference in Windows SMBv3 before the April 2022 patches allows attackers to crash and reboot the Windows kernel. The srv2!Smb2ValidateVolumeObjectsMatch function dereferences a nullable PDEVICE_OBJECT and passes it to IoGetBaseFileSystemDeviceObject while handling a crafted FileNormalizedNameInformation query on a named pipe. Access normally requires an authenticated IPC$ named-pipe session or non-default guest access, but domain controllers expose anonymously openable pipes; exploitation causes a BSOD and normally an automatic reboot.

The record

CVE
CVE-2022-32230
Published
Jun 14, 2022
Updated
Sep 16, 2024
Vendor
Microsoft
Product
Windows 10 Version 21H1
Classifications
CWE-476, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 14, 2022CVE publishedPublication date reported by the CVE source.
  2. Sep 16, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=19042.1706 <19042.1706
  2. Affected versionversion=19043.1706 <19043.1706
  3. Affected versionversion=19044.1706 <19044.1706

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Microsoft · Windows 10 Version 21H1version=19042.1706 <19042.1706; version=19043.1706 <19043.1706; version=19044.1706 <19044.1706
Microsoft · Windows 10 Version 21H2version=19042.1706 <19042.1706; version=19043.1706 <19043.1706; version=19044.1706 <19044.1706
Microsoft · Windows 10 Version 20H2version=19042.1706 <19042.1706; version=19043.1706 <19043.1706; version=19044.1706 <19043.1706
Microsoft · Windows Server version 20H2version=19042.1706 <19042.1706; version=19043.1706 <19043.1706; version=19044.1706 <19044.1706

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-476NULL Pointer Dereference
T1499.004Endpoint Denial of Service: Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo