# CVE-2024-53922: Denial of service in Exynos 8890 firmware

> A missing length check in the buffer queue driver allows attackers to cause a kernel denial of service on Samsung Exynos automotive processors.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-hq64-jgxg-v8cf

## What is CVE-2024-53922?

CVE-2024-53922 is a medium-severity denial of service vulnerability in Samsung Exynos 8890 firmware, published on 13 Sep 2026. 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 the buffer queue driver in Samsung Automotive Processor Exynos Auto 8890, V7, V9, and V920. Lack of a length check leads to a Denial of Service in the kernel.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2024-53922?


## How do I fix CVE-2024-53922?

No fix has been published for CVE-2024-53922 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-53922 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53922 and fix it if it is affected.

What it is: CVE-2024-53922 is a medium-severity denial of service vulnerability in Samsung Exynos 8890 firmware, published on 13 Sep 2026. 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-2024-53922 in the wild and no public exploit code.

Affected product: Samsung Exynos 8890 firmware. 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-2024-53922/ (Markdown: https://insights.sbomify.com/CVE-2024-53922/index.md)
```

## Sources

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

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