CVE-2022-4139: High severity Linux Linux kernel vulnerability

Published Nov 24, 2022
·
Updated

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.

Other sources

Incorrect GPU TLB flush code has been discovered in i915 kernel driver. In some cases (Gen12 hardware with specific types of engine) the engine's TLB is not flushed at all. Depending on whether the GPU is running behind an active IOMMU there are two possible scenarios which can happen, due to stale TLB mapping:

1. Without IOMMU - GPU can still access physical memory which could be already assigned by OS to different process. 2. With IOMMU - GPU can access any memory, if the malicious process is able to create/reuse necessary IOMMU mappings.

It is currently not known if specific memory could be targeted, but random memory corruption or data leaks are a known possibility. All Intel integrated and discrete GPUs Gen12 are affected, including Tiger Lake, Rocket Lake, Alder Lake, DG1, Raptor Lake, DG2, Arctic Sound, Meteor Lake.

This vulnerability has similar impact as CVE-2022-0330: https://access.redhat.com/security/cve/CVE-2022-0330.

Reference: https://www.openwall.com/lists/oss-security/2022/11/30/1

Red Hat

Linux Kernel is vulnerable to a denial of service, caused by an incorrect GPU TLB flush code flaw in the i915 kernel driver. By sending a specially-crafted request, a local attacker could exploit this vulnerability to cause a random memory corruption or data leaks.

IBM

Affected Software

21 affected componentsFixes available
redhat/kernel<6.1
6.1
Linux Linux kernel>=5.4<5.4.226
Linux Linux kernel>=5.5<5.10.157
Linux Linux kernel>=5.11<5.15.81
Linux Linux kernel>=5.16<6.0.11
Linux Linux kernel=6.1
Linux Linux kernel=6.1-rc1
Linux Linux kernel=6.1-rc2
Linux Linux kernel=6.1-rc3
Linux Linux kernel=6.1-rc4
Linux Linux kernel=6.1-rc5
Linux Linux kernel=6.1-rc6
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.27-1
IBM Data Virtualization on Cloud Pak for Data<=3.0
IBM Watson Query on Cloud Pak for Data<=2.2
IBM Watson Query on Cloud Pak for Data<=2.1
IBM Watson Query on Cloud Pak for Data<=2.0
IBM Data Virtualization on Cloud Pak for Data<=1.8
IBM Data Virtualization on Cloud Pak for Data<=1.7
Microsoft cm1 kernel 5.10.168.1-1
Microsoft cbl2 kernel 5.15.92.1-2

Event History

Nov 24, 2022
Data Sourced
via Red Hat·10:26 AM
DescriptionSeverityAffected Software
Jan 27, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Jan 12, 2024
Data Sourced
via Launchpad·12:11 AM
Description
May 2, 2025
Data Sourced
via Ubuntu·05:03 AM
RemedyDescriptionSeverityAffected Software
Aug 15, 2025
Data Sourced
via IBM·03:29 PM
DescriptionAffected Software
Oct 1, 2025
Data Sourced
via Microsoft·11:11 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·11:11 PM
Affected Software
Updated
via Microsoft·11:11 PM
Affected Software
Updated
via Microsoft·11:11 PM
DescriptionSeverity

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2022-4139?

CVE-2022-4139 is considered a high severity vulnerability due to its potential for privilege escalation and system crashes.

2

How do I fix CVE-2022-4139?

To fix CVE-2022-4139, upgrade to the recommended Linux kernel versions or apply patches provided by your distribution.

3

What software is affected by CVE-2022-4139?

CVE-2022-4139 affects multiple versions of the Linux kernel, specifically those from 5.4.x to 6.1.

4

Who can exploit CVE-2022-4139?

CVE-2022-4139 can be exploited by local users who have access to the affected system.

5

What are potential impacts of CVE-2022-4139?

The impacts of CVE-2022-4139 include random memory corruption, data leaks, system crashes, and potential privilege escalation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203