dbcve.org
Linux KernelOperating system · Linux

CVE-2019-10126

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-14
Fix available
A fix is available. Upgrade to 4.4.186 / 4.9.186 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
A flaw was found in the Linux kernel. A heap based buffer overflow in mwifiex_uap_parse_tail_ies function in drivers/net/wireless/marvell/mwifiex/ie.c might lead to memory corruption and possibly other consequences.

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-122

Data overflows a buffer allocated on the heap, corrupting neighbouring heap structures and allocator metadata that a patient attacker can groom into control of execution. It is subtler than a stack overflow but just as dangerous. The fix is validating lengths before every write and using safe allocators and bounded operations.

General guidance for the heap-based buffer overflow 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:>= 4.2, < 4.4.186>= 4.5, < 4.9.186>= 4.10, < 4.14.134>= 4.15, < 4.19.59>= 4.20, < 5.1.18
VirtualizationApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 8.0
Enterprise Linux AusOperating system
Affected:= 8.2= 8.4
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux EusOperating system
Affected:= 7.7= 8.1= 8.2= 8.4
Enterprise Linux For Real TimeOperating system
Affected:= 7= 8
Enterprise Linux For Real Time For NfvOperating system
Affected:= 7

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
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

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 4.4.186 / 4.9.186 / 4.14.134 or later
Fixed in 4.4.1864.9.1864.14.134
Vendor patch packetstormsecurity.com →
Recommended fix High confidence

Upgrade to kernel >= 4.4.186 (for 4.4.x), >= 4.9.186 (for 4.9.x), >= 4.14.134 (for 4.14.x), or >= 4.19.59 (for 4.19.x). For RHEL 7.x use vendor RHSA advisory, for RHEL 8.x use RHSA advisory.

  1. Identify the currently running kernel version using 'uname -r'
  2. Determine which version branch you are on (e.g., 4.4.x, 4.9.x, 4.14.x, 4.19.x)
  3. For RHEL/CentOS systems: run 'yum update kernel' or 'dnf update kernel' to install patched kernel
  4. For Debian/Ubuntu systems: run 'apt-get update && apt-get upgrade linux-image-generic'
  5. For SUSE systems: run 'zypper patch' or 'zypper update kernel-*'
  6. Verify the new kernel package is installed: 'rpm -qa | grep kernel' or 'dpkg -l | grep linux-image'
  7. Reboot the system to load the patched kernel: 'systemctl reboot'
  8. After reboot, verify the running kernel is fixed: 'uname -r' and confirm version is >= the fixed version for your branch
Caveat Kernel upgrade requires system reboot and may require updating out-of-tree kernel modules or drivers.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10126 — 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-2019-10126 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