# CVE-2022-39188: Race condition in n/a

> A race condition in the Linux kernel allows device drivers to free pages with stale TLB entries, potentially leading to undefined behavior or memory corruption.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2022
- **Updated:** 14 Oct 2026
- **Also known as:** AZL-10858, DEBIAN-CVE-2022-39188, GHSA-4qqj-hc3p-xwfg, OESA-2022-1968, SUSE-SU-2022:3346-1, SUSE-SU-2022:3362-1, SUSE-SU-2022:3372-1, SUSE-SU-2022:3379-1, SUSE-SU-2022:3406-1, UBUNTU-CVE-2022-39188

## What is CVE-2022-39188?

CVE-2022-39188 is a medium-severity vulnerability in Debian Debian Linux, published on 2 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in include/asm-generic/tlb.h in the Linux kernel before 5.19. Because of a race condition (unmap_mapping_range versus munmap), a device driver can free a page while it still has stale TLB entries. This only occurs in situations with VM_PFNMAP VMAs.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2022-39188?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP4_Update_27` | SUSE:Linux Enterprise Live Patching 12 SP4 | All versions | 5-2.2 |
| `kgraft-patch-SLE12-SP4_Update_28` | SUSE:Linux Enterprise Live Patching 12 SP4 | All versions | 3-2.2 |
| `kgraft-patch-SLE12-SP4_Update_29` | SUSE:Linux Enterprise Live Patching 12 SP4 | All versions | 3-2.2 |
| `kgraft-patch-SLE12-SP4_Update_30` | SUSE:Linux Enterprise Live Patching 12 SP4 | All versions | 2-2.2 |
| `kgraft-patch-SLE12-SP5_Update_35` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 2-2.2 |
| `kernel-livepatch-SLE15_Update_30` | SUSE:Linux Enterprise Live Patching 15 | All versions | 5-150000.2.2 |
| `kernel-livepatch-SLE15_Update_31` | SUSE:Linux Enterprise Live Patching 15 | All versions | 3-150000.2.2 |
| `kernel-livepatch-SLE15_Update_32` | SUSE:Linux Enterprise Live Patching 15 | All versions | 3-150000.2.2 |
| `kernel-livepatch-SLE15-SP4_Update_2` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 3-150400.2.2 |

Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2022-39188?

Apply the vendor's patch.

## Is CVE-2022-39188 being exploited?

There is no known exploitation of CVE-2022-39188 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39188 and fix it if it is affected.

What it is: CVE-2022-39188 is a medium-severity vulnerability in Debian Debian Linux, published on 2 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39188 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39188/ (Markdown: https://insights.sbomify.com/CVE-2022-39188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39188
- OSV: https://osv.dev/vulnerability/CVE-2022-39188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39188/
Summaries are generated and may contain mistakes; the official description above is the record.