# CVE-2022-49935: dma-buf/dma-resv: check if the new fence is really later

> A use-after-free vulnerability in the Linux kernel's dma-resv subsystem allows local attackers to trigger memory corruption, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 18 Jun 2025
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-70208, DEBIAN-CVE-2022-49935, GHSA-rj36-vf3r-744c, ROOT-OS-DEBIAN-11-CVE-2022-49935, ROOT-OS-UBUNTU-2204-CVE-2022-49935, UBUNTU-CVE-2022-49935

## What is CVE-2022-49935?

CVE-2022-49935 is a high-severity use after free vulnerability in Linux kernel, published on 18 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

dma-buf/dma-resv: check if the new fence is really later

Previously when we added a fence to a dma_resv object we always
assumed the the newer than all the existing fences.

With Jason's work to add an UAPI to explicit export/import that's not
necessary the case any more. So without this check we would allow
userspace to force the kernel into an use after free error.

Since the change is very small and defensive it's probably a good
idea to backport this to stable kernels as well just in case others
are using the dma_resv object in the same way.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2022-49935 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-49935 is a high-severity use after free vulnerability in Linux kernel, published on 18 Jun 2025. 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-49935 in the wild and no public exploit code.

Affected product: Linux kernel. 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-49935/ (Markdown: https://insights.sbomify.com/CVE-2022-49935/index.md)
```

## Sources

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

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