dbcve.org
Linux KernelOperating system · Linux

CVE-2022-28390

HIGH · 7.8 CVSS v3.1 Published 2022-04-03
Fix available
A fix is available. Upgrade to after 5.17.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 · unedited
ems_usb_start_xmit in drivers/net/can/usb/ems_usb.c in the Linux kernel through 5.17.1 has a double free.

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
How this class of weakness works · CWE-415

The same block of memory is freed twice, corrupting the allocator's bookkeeping in ways an attacker can shape toward code execution. It usually stems from tangled ownership of a pointer. The fix is clear, single ownership of each allocation and clearing pointers once they are freed.

General guidance for the double free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Affected:>= 2.6.32, <= 5.17.1
FedoraOperating system
Affected:= 34= 35= 36
Debian LinuxOperating system
Affected:= 9.0= 10.0= 11.0
Hci Baseboard Management ControllerApplication
Affected:= h300e= h300s= h410c= h410s= h500e= h500s= h700e= h700s

CVSS 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
High
Integrity
High
Availability
High

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

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 · scoped
Upgrade available Upgrade to a release after 5.17.1
Vendor patch github.com →
Recommended fix High confidence

Linux Kernel 5.17.2 or later; or vendor-provided patched kernel for Fedora 34/35/36, Debian 9/10/11

  1. Identify the current kernel version using 'uname -r' or 'cat /proc/version'
  2. For upstream Linux: Upgrade to kernel version 5.17.2 or later which contains the fix for the double free in ems_usb.c
  3. For Fedora systems: Run 'dnf update kernel' to install the patched kernel for versions 34, 35, or 36
  4. For Debian systems: Run 'apt-get update && apt-get upgrade' to install the patched kernel for versions 9, 10, or 11
  5. Reboot the system to load the patched kernel
  6. Verify the fix is applied by checking the kernel version and confirming the ems_usb.c changes are present
Caveat Kernel upgrades may require system reboot and could have compatibility implications with custom kernel modules or specific hardware drivers

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28390 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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