CVE-2022-41578
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 · uneditedThe MPTCP module has an out-of-bounds write vulnerability.Successful exploitation of this vulnerability may cause root privilege escalation attacks implemented by modifying program information.
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 confidenceA critical out-of-bounds write vulnerability exists in the Linux kernel's MPTCP (MultiPath TCP) module. This memory corruption flaw can be exploited to achieve root privilege escalation by allowing an attacker to modify program information through improper bounds checking when handling MPTCP operations.
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= 11.0.1= 12.0.0= 2.0= 2.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Verify MPTCP kernel module statusCheck if the mptcp kernel module is loaded or compiled into the kernel. On Linux systems, run 'lsmod | grep mptcp' or check /proc/config.gz for CONFIG_MPTCP options if available.Affected if MPTCP module is loaded or enabled in the kernel configuration
-
Identify the Huawei device OS versionOn the Huawei device, check the Emui or Harmonyos version by going to Settings > About Phone > Version, or run 'getprop ro.build.version.emui' for Emui or 'getprop ro.build.version.harmonyos' via ADB shell.Affected if The version is exactly 11.0.1 or 12.0.0 for Emui, or exactly 2.0 or 2.1 for Harmonyos
-
Confirm kernel version alignmentCheck the running kernel version via 'uname -r' or 'cat /proc/version'. Compare against the version typically shipped with the affected Emui/Harmonyos releases.Affected if Kernel version corresponds to the affected Emui 11.0.1/12.0.0 or Harmonyos 2.0/2.1 releases
-
Assess MPTCP exposureVerify if any applications or network configurations actively use MPTCP functionality. Check system logs and network configuration files for mptcp-related activity.Affected if MPTCP is actively in use by any running processes or network configurations
The environment is affected if MPTCP is enabled and the device runs Emui 11.0.1, 12.0.0, Harmonyos 2.0, or Harmonyos 2.1.
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 vendor-supplied kernel security patch for CVE-2022-41578 to the MPTCP module. Until patched, minimize attack surface by restricting access to MPTCP functionality to trusted processes only.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41578 — 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-41578 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