dbcve.org
Linux KernelOperating system · Linux

CVE-2022-4139

HIGH · 7.8 CVSS v3.1 Published 2023-01-27
Fix available
A fix is available. Upgrade to 5.4.226 / 5.10.157 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
An incorrect TLB flush issue was found in the Linux kernel’s GPU i915 kernel driver, potentially leading to random memory corruption or data leaks. This flaw could allow a local user to crash the system or escalate their privileges on the system.

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

A detailed technical summary for this CVE is being prepared.

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:>= 5.4, < 5.4.226>= 5.5, < 5.10.157>= 5.11, < 5.15.81>= 5.16, < 6.0.11= 6.1

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 5.4.226 / 5.10.157 / 5.15.81 or later
Fixed in 5.4.2265.10.1575.15.81
Vendor patch bugzilla.redhat.com →
Recommended fix High confidence

Upgrade to kernel version 5.4.226 or higher (5.4.x branch), 5.10.157 or higher (5.10.x branch), 5.15.81 or higher (5.15.x branch), or 6.0.11 or higher (6.0.x branch); preferably upgrade to the latest stable LTS kernel (e.g., 6.1.x or 6.6.x for long-term support)

  1. 1. Identify the currently running kernel version using 'uname -r'
  2. 2. Check if the system is running a vulnerable version (5.4 < version < 5.4.226, 5.5 <= version < 5.10.157, 5.11 <= version < 5.15.81, or 5.16 <= version < 6.0.11)
  3. 3. Back up critical data and create a system snapshot or backup before kernel upgrade
  4. 4. Update the package manager and install the latest kernel: for Debian/Ubuntu run 'apt update && apt install linux-image-generic', for RHEL/CentOS run 'yum update kernel', for Fedora run 'dnf update kernel'
  5. 5. Verify the new kernel version is installed (e.g., 'rpm -qa | grep kernel' or 'dpkg -l | grep linux-image')
  6. 6. Reboot the system to load the new kernel: 'systemctl reboot'
  7. 7. After reboot, verify the system is running a patched kernel version using 'uname -r'
  8. 8. Confirm the i915 driver loads correctly and graphics functionality works as expected
Caveat Kernel upgrades may require rebuilding third-party kernel modules (like NVIDIA drivers); ensure compatibility or rebuild after upgrade; some older hardware drivers may not be supported in newer kernels

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 $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-4139 — 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-4139 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