CVE-2023-53501
published 2025-10-01CVE-2023-53501: In the Linux kernel, the following vulnerability has been resolved: iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind When…
PriorityP415medium4.7CVSS 3.1
AVLACHPRLUINSUCNINAH
EPSS
0.14%
3.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind
When unbinding pasid - a race condition exists vs outstanding page faults.
To prevent this, the pasid_state object contains a refcount.
* set to 1 on pasid bind
* incremented on each ppr notification start
* decremented on each ppr notification done
* decremented on pasid unbind
Since refcount_dec assumes that refcount will never reach 0:
the current implementation causes the following to be invoked on
pasid unbind:
REFCOUNT_WARN("decrement hit 0; leaking memory")
Fix this issue by changing refcount_dec to refcount_dec_and_test
to explicitly handle refcount=1.Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.55-1 (bookworm) | linux 6.1.55-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8bc54824da4e8fcf0ed679cf09ac32f23d83254a < a50d60b8f2aff46dd7c7edb4a5835cdc4d432c22 | a50d60b8f2aff46dd7c7edb4a5835cdc4d432c22 |
| linux | linux | >= 8bc54824da4e8fcf0ed679cf09ac32f23d83254a < 13ed255248dfbbb7f23f9170c7a537fb9ca22c73 | 13ed255248dfbbb7f23f9170c7a537fb9ca22c73 |
| linux | linux | >= 8bc54824da4e8fcf0ed679cf09ac32f23d83254a < 9ccc51be3126b25cfe9351dbffde946c925cc28a | 9ccc51be3126b25cfe9351dbffde946c925cc28a |
| linux | linux | >= 8bc54824da4e8fcf0ed679cf09ac32f23d83254a < 98d86bf32187db27946ca817c2467a5f2f7aa02f | 98d86bf32187db27946ca817c2467a5f2f7aa02f |
| linux | linux | >= 8bc54824da4e8fcf0ed679cf09ac32f23d83254a < 534103bcd52ca9c1fecbc70e717b4a538dc4ded8 | 534103bcd52ca9c1fecbc70e717b4a538dc4ded8 |
| linux | linux_kernel | >= 0 < 6.1.55-1 | 6.1.55-1 |
| linux | linux_kernel | >= 0 < 6.5.3-1 | 6.5.3-1 |
| linux | linux_kernel | >= 0 < 6.5.3-1 | 6.5.3-1 |
| linux | linux_kernel | >= 5.15 < 5.15.132 | 5.15.132 |
| linux | linux_kernel | >= 5.16 < 6.1.53 | 6.1.53 |
| linux | linux_kernel | >= 6.2 < 6.4.16 | 6.4.16 |
| linux | linux_kernel | >= 6.5 < 6.5.3 | 6.5.3 |
CVSS provenance
nvdv3.14.7MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
osv4.7MEDIUM
vendor_debian4.7MEDIUM
vendor_redhat4.7MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: Linux kernel: Denial of Service due to race condition in IOMMU pasid unbinding
vendor_redhat·2025-10-01·CVSS 4.7
CVE-2023-53501 [MEDIUM] CWE-911 kernel: Linux kernel: Denial of Service due to race condition in IOMMU pasid unbinding
kernel: Linux kernel: Denial of Service due to race condition in IOMMU pasid unbinding
In the Linux kernel, the following vulnerability has been resolved:
iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind
When unbinding pasid - a race condition exists vs outstanding page faults.
To prevent this, the pasid_state object contains a refcount.
* set to 1 on pasid bind
* incremented on each ppr notification start
* decremented on each ppr notification done
* decremented on pasid unbind
Since refcount_dec assumes that refcount will never reach 0:
the current implementation causes the following to be invoked on
pasid unbind:
REFCOUNT_WARN("decrement hit 0; leaking memory")
Fix this issue by changing refcount_dec to refcount_dec_and_test
to explicitly handle refcount=1
Debian
CVE-2023-53501: linux - In the Linux kernel, the following vulnerability has been resolved: iommu/amd/i...
vendor_debian·2023·CVSS 4.7
CVE-2023-53501 [MEDIUM] CVE-2023-53501: linux - In the Linux kernel, the following vulnerability has been resolved: iommu/amd/i...
In the Linux kernel, the following vulnerability has been resolved: iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind When unbinding pasid - a race condition exists vs outstanding page faults. To prevent this, the pasid_state object contains a refcount. * set to 1 on pasid bind * incremented on each ppr notification start * decremented on each ppr notification done * decremented on pasid unbind Since refcount_dec assumes that refcount will never reach 0: the current implementation causes the following to be invoked on pasid unbind: REFCOUNT_WARN("decrement hit 0; leaking memory") Fix this issue by changing refcount_dec to refcount_dec_and_test to explicitly handle refcount=1.
Scope: local
bookworm: resolved (fixed in 6.1.55-1)
bullseye: resolved
forky: resolved
GHSA
GHSA-76q6-633x-65vj: In the Linux kernel, the following vulnerability has been resolved:
iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind
W
ghsa_unreviewed·2025-10-01
CVE-2023-53501 [MEDIUM] GHSA-76q6-633x-65vj: In the Linux kernel, the following vulnerability has been resolved:
iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind
W
In the Linux kernel, the following vulnerability has been resolved:
iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind
When unbinding pasid - a race condition exists vs outstanding page faults.
To prevent this, the pasid_state object contains a refcount.
* set to 1 on pasid bind
* incremented on each ppr notification start
* decremented on each ppr notification done
* decremented on pasid unbind
Since refcount_dec assumes that refcount will never reach 0:
the current implementation causes the following to be invoked on
pasid unbind:
REFCOUNT_WARN("decrement hit 0; leaking memory")
Fix this issue by changing refcount_dec to refcount_dec_and_test
to explicitly handle refcount=1.
OSV
CVE-2023-53501: In the Linux kernel, the following vulnerability has been resolved: iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind Whe
osv·2025-10-01·CVSS 4.7
CVE-2023-53501 [MEDIUM] CVE-2023-53501: In the Linux kernel, the following vulnerability has been resolved: iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind Whe
In the Linux kernel, the following vulnerability has been resolved: iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind When unbinding pasid - a race condition exists vs outstanding page faults. To prevent this, the pasid_state object contains a refcount. * set to 1 on pasid bind * incremented on each ppr notification start * decremented on each ppr notification done * decremented on pasid unbind Since refcount_dec assumes that refcount will never reach 0: the current implementation causes the following to be invoked on pasid unbind: REFCOUNT_WARN("decrement hit 0; leaking memory") Fix this issue by changing refcount_dec to refcount_dec_and_test to explicitly handle refcount=1.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/13ed255248dfbbb7f23f9170c7a537fb9ca22c73https://git.kernel.org/stable/c/534103bcd52ca9c1fecbc70e717b4a538dc4ded8https://git.kernel.org/stable/c/98d86bf32187db27946ca817c2467a5f2f7aa02fhttps://git.kernel.org/stable/c/9ccc51be3126b25cfe9351dbffde946c925cc28ahttps://git.kernel.org/stable/c/a50d60b8f2aff46dd7c7edb4a5835cdc4d432c22
2025-10-01
Published