Linux KernelOperating system · Linux
CVE-2022-0400
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 · uneditedAn out-of-bounds read vulnerability was discovered in linux kernel in the smc protocol stack, causing remote dos.
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 confidenceAn out-of-bounds read vulnerability exists in the Linux kernel's SMC (Shared Memory Communications) protocol stack. The flaw allows a remote attacker to read memory outside allocated buffer boundaries, potentially leaking sensitive kernel data, and can trigger a denial of service by causing a kernel crash or hang.
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
Linux KernelOperating system
all versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine if SMC protocol support is compiled into the kernelCheck kernel configuration for SMC support by looking for CONFIG_SMC or CONFIG_SMC_DIAG in /boot/config-$(uname -r) or /proc/config.gz, or check if the smc or smc_diag kernel modules are loaded using 'lsmod | grep smc'Affected if SMC (smc or smc_diag) module is loaded or CONFIG_SMC is enabled in kernel config
-
Identify the running kernel versionRun 'uname -r' to get the exact kernel version and compare against the version that includes the fix for CVE-2022-0400Affected if The kernel version is older than the version that contains the upstream patch fixing this vulnerability
-
Check if SMC is actively in use on the systemLook for SMC-related processes or check /proc/net/smc/ directory for active SMC connections using 'ls -la /proc/net/smc/ 2>/dev/null'Affected if SMC connections or sockets are present and active on the system
-
Verify SMC kernel module statusRun 'modinfo smc' and 'modinfo smc_diag' to check if SMC modules are available, and 'systemctl status smc' if a systemd service exists for SMCAffected if SMC kernel modules are present and can be loaded
A system is affected by CVE-2022-0400 if it runs a vulnerable kernel version with SMC protocol support enabled or loaded, and the kernel version predates the fix.
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.
From vendor dataApply the upstream Linux kernel patch or update to a kernel version that includes the fix. If immediate patching is not possible, consider network-level filtering to restrict access to the SMC protocol service if it is exposed.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0400 — 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-2022-0400 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