# drm/amdgpu/cs: make commands with 0 chunks illegal behaviour.

CVE record · `CVE-2022-49335`

- **Identifiers:** `CVE-2022-49335`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-476](https://cwe.mitre.org/data/definitions/476.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 8189f44270db1be78169e11eec51a3eeb980bc63` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before aa25acbe96692e4bf8482311c293f72d8c6034c0` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 15c3bcc9b5349d40207e5f8d4d799b8b4b7d13b8` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before c12984cdb077b9042d2dc20ca18cb16a87bcc774` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before be585921f29df5422a39c952d188b418ad48ffab` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 70276460e914d560e96bfc208695a872fe9469c9` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 20b947e5a3c74c5084d661c097517a554989d462` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 7086a23890d255bb5761604e39174b20d06231a4` (git)
  - affected: `d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 31ab27b14daaa75541a415c6794d6f3567fea44a` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.2`
  - unaffected: `before 4.2` (semver)
  - unaffected: `4.9.318 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.283 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.247 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.198 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.121 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.46 to 5.15.*, inclusive` (semver)
  - unaffected: `5.17.14 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18.3 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 26 Feb 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2022-49335](https://www.cve.org/CVERecord?id=CVE-2022-49335)
- [NVD: CVE-2022-49335](https://nvd.nist.gov/vuln/detail/CVE-2022-49335)

### References from the CNA

- <https://git.kernel.org/stable/c/8189f44270db1be78169e11eec51a3eeb980bc63>
- <https://git.kernel.org/stable/c/aa25acbe96692e4bf8482311c293f72d8c6034c0>
- <https://git.kernel.org/stable/c/15c3bcc9b5349d40207e5f8d4d799b8b4b7d13b8>
- <https://git.kernel.org/stable/c/c12984cdb077b9042d2dc20ca18cb16a87bcc774>
- <https://git.kernel.org/stable/c/be585921f29df5422a39c952d188b418ad48ffab>
- <https://git.kernel.org/stable/c/70276460e914d560e96bfc208695a872fe9469c9>
- <https://git.kernel.org/stable/c/20b947e5a3c74c5084d661c097517a554989d462>
- <https://git.kernel.org/stable/c/7086a23890d255bb5761604e39174b20d06231a4>
- <https://git.kernel.org/stable/c/31ab27b14daaa75541a415c6794d6f3567fea44a>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49335>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49335/>. Everything for agents: <https://agentprime.io/llms.txt>.
