# CVE-2023-53360: NFSv4.2: Rework scratch handling for READ_PLUS (again)

> A double-free vulnerability in the Linux kernel's NFSv4.2 READ_PLUS handling can cause a system crash when decoding hole segments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-53360, DEBIAN-CVE-2023-53360, GHSA-4v4w-685q-cqmx, UBUNTU-CVE-2023-53360

## What is CVE-2023-53360?

CVE-2023-53360 is a critical use after free vulnerability in Linux kernel, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

NFSv4.2: Rework scratch handling for READ_PLUS (again)

I found that the read code might send multiple requests using the same
nfs_pgio_header, but nfs4_proc_read_setup() is only called once. This is
how we ended up occasionally double-freeing the scratch buffer, but also
means we set a NULL pointer but non-zero length to the xdr scratch
buffer. This results in an oops the first time decoding needs to copy
something to scratch, which frequently happens when decoding READ_PLUS
hole segments.

I fix this by moving scratch handling into the pageio read code. I
provide a function to allocate scratch space for decoding read replies,
and free the scratch buffer when the nfs_pgio_header is freed.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2023-53360?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-53360?

Apply the vendor's patch.

## Is CVE-2023-53360 being exploited?

There is no known exploitation of CVE-2023-53360 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53360 and fix it if it is affected.

What it is: CVE-2023-53360 is a critical use after free vulnerability in Linux kernel, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-53360 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2023-53360/ (Markdown: https://insights.sbomify.com/CVE-2023-53360/index.md)
```

## Sources

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

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