# CVE-2025-37927: iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid

> A buffer overflow in the Linux kernel's AMD IOMMU driver allows attackers to potentially execute arbitrary code or escalate privileges via crafted ACPI data.

- **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:** 20 May 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-37927, DEBIAN-CVE-2025-37927, GHSA-jrcg-ffmc-qfvv, ROOT-OS-DEBIAN-11-CVE-2025-37927, ROOT-OS-DEBIAN-12-CVE-2025-37927, ROOT-OS-UBUNTU-2204-CVE-2025-37927, ROOT-OS-UBUNTU-2404-CVE-2025-37927, UBUNTU-CVE-2025-37927

## What is CVE-2025-37927?

CVE-2025-37927 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 20 May 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:

iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid

There is a string parsing logic error which can lead to an overflow of hid
or uid buffers. Comparing ACPIID_LEN against a total string length doesn't
take into account the lengths of individual hid and uid buffers so the
check is insufficient in some cases. For example if the length of hid
string is 4 and the length of the uid string is 260, the length of str
will be equal to ACPIID_LEN + 1 but uid string will overflow uid buffer
which size is 256.

The same applies to the hid string with length 13 and uid string with
length 250.

Check the length of hid and uid strings separately to prevent
buffer overflow.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-37927?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2025-37927?

Apply the vendor's patch.

## Is CVE-2025-37927 being exploited?

There is no known exploitation of CVE-2025-37927 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-2025-37927 and fix it if it is affected.

What it is: CVE-2025-37927 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 20 May 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-2025-37927 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-2025-37927/ (Markdown: https://insights.sbomify.com/CVE-2025-37927/index.md)
```

## Sources

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

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