# iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind

CVE record · `CVE-2023-53501`

- **Identifiers:** `CVE-2023-53501`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 Oct 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 Oct 2025, 11:45 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: `8bc54824da4e8fcf0ed679cf09ac32f23d83254a to before a50d60b8f2aff46dd7c7edb4a5835cdc4d432c22` (git)
  - affected: `8bc54824da4e8fcf0ed679cf09ac32f23d83254a to before 13ed255248dfbbb7f23f9170c7a537fb9ca22c73` (git)
  - affected: `8bc54824da4e8fcf0ed679cf09ac32f23d83254a to before 9ccc51be3126b25cfe9351dbffde946c925cc28a` (git)
  - affected: `8bc54824da4e8fcf0ed679cf09ac32f23d83254a to before 98d86bf32187db27946ca817c2467a5f2f7aa02f` (git)
  - affected: `8bc54824da4e8fcf0ed679cf09ac32f23d83254a to before 534103bcd52ca9c1fecbc70e717b4a538dc4ded8` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.15`
  - unaffected: `before 5.15` (semver)
  - unaffected: `5.15.132 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.53 to 6.1.*, inclusive` (semver)
  - unaffected: `6.4.16 to 6.4.*, inclusive` (semver)
  - unaffected: `6.5.3 to 6.5.*, inclusive` (semver)
  - unaffected: `6.6 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th 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 1 Oct 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/a50d60b8f2aff46dd7c7edb4a5835cdc4d432c22>
- <https://git.kernel.org/stable/c/13ed255248dfbbb7f23f9170c7a537fb9ca22c73>
- <https://git.kernel.org/stable/c/9ccc51be3126b25cfe9351dbffde946c925cc28a>
- <https://git.kernel.org/stable/c/98d86bf32187db27946ca817c2467a5f2f7aa02f>
- <https://git.kernel.org/stable/c/534103bcd52ca9c1fecbc70e717b4a538dc4ded8>

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-2023-53501>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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