CVE-2023-53606
Last modified
CVE-2023-53606 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: nfsd: clean up potential nfsd_file refcount leaks in COPY codepath There are two different flavors of the nfsd4_copy struct. One is embedded in the compound and is used directly in synchronous copies. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: nfsd: clean up potential nfsd_file refcount leaks in COPY codepath There are two different flavors of the nfsd4_copy struct. One is embedded in the compound and is used directly in synchronous copies. The other is dynamically allocated, refcounted and tracked in the client struture. For the embedded one, the cleanup just involves releasing any nfsd_files held on its behalf. For the async one, the cleanup is a bit more involved, and we need to dequeue it from lists, unhash it, etc. There is at least one potential refcount leak in this code now. If the kthread_create call fails, then both the src and dst nfsd_files in the original nfsd4_copy object are leaked. The cleanup in this codepath is also sort of weird. In the async copy case, we'll have up to four nfsd_file references (src and dst for both flavors of copy structure). They are both put at the end of nfsd4_do_async_copy, even though the ones held on behalf of the embedded one outlive that structure. Change it so that we always clean up the nfsd_file refs held by the embedded copy structure before nfsd4_copy returns. Rework cleanup_async_copy to handle both inter and intra copies. Eliminate nfsd4_cleanup_intra_ssc since it now becomes a no-op.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.20, < 5.10.220 |
| Linux | Linux Kernel | >= 5.11, < 5.15.154 |
| Linux | Linux Kernel | >= 5.16, < 6.1.16 |
| Linux | Linux Kernel | >= 6.2, < 6.2.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53606?
How severe is CVE-2023-53606?
How do I fix CVE-2023-53606?
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-53600In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53601In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53602In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53603In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53604In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53605In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53607In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53608In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53609In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5361Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-53610In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53611In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53606?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
