CVE-2023-53501
Last modified
CVE-2023-53501 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.15, < 5.15.132 |
| Linux | Linux Kernel | >= 5.16, < 6.1.53 |
| Linux | Linux Kernel | >= 6.2, < 6.4.16 |
| Linux | Linux Kernel | >= 6.5, < 6.5.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2023-53501?
How severe is CVE-2023-53501?
How do I fix CVE-2023-53501?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53496In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53497In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53498In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53499In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5350 SQL Injection in GitHub repository salesagility/suitecrm pr…9.1
- CVE-2023-53500In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53502Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-53503In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53504In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53505In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53506In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53507In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2023-53501?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
