CVE-2023-53241

nfsd: call op_release, even when op_func returns an error

MEDIUM
5.5
CVSS Score
Published: September 15, 2025 at 02:23 PM UTC
Updated: June 17, 2026 at 06:44 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: call op_release, even when op_func returns an error For ops with "trivial" replies, nfsd4_encode_operation will shortcut most of the encoding work and skip to just marshalling up the status. One of the things it skips is calling op_release. This could cause a memory leak in the layoutget codepath if there is an error at an inopportune time. Have the compound processing engine always call op_release, even when op_func sets an error in op->status. With this change, we also need nfsd4_block_get_device_info_scsi to set the gd_device pointer to NULL on error to avoid a double free.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14 ≤ v < 5.10.2204.14 ≤ v < 5.15.1544.14 ≤ v < 6.1.244.14 ≤ v < 6.2.114.14 ≤ v < 6.35.11 ≤ v < 5.15.1545.16 ≤ v < 6.1.246.2 ≤ v < 6.2.1134b1744c91ccd44811005822106945fa80ecbff24.146.3 rc16.3 rc26.3 rc36.3 rc46.3 rc5
Vendor states this is fixed in 15a8b55dbb1ba154d82627547c5761cac884d810 (fixed)
Vendor states this is fixed in 3d0dcada384af22dec764c8374a2997870ec86ae (fixed)
Vendor states this is fixed in 65a33135e91e6dd661ecdf1194b9d90c49ae3570 (fixed)
Vendor states this is fixed in b11d8162c24af4a351d21e2c804d25ca493305e3 (fixed)
Vendor states this is fixed in b623a8e5d38a69a3ef8644acb1030dd7c7bc28b3 (fixed)
Vendor states this is fixed in 4.14 (unaffected)
Vendor states this is fixed in 5.10.220 (unaffected)
Vendor states this is fixed in 5.15.154 (unaffected)
Vendor states this is fixed in 6.1.24 (unaffected)
Vendor states this is fixed in 6.2.11 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/15a8b55dbb1ba154d82627547c5761cac884d810
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3d0dcada384af22dec764c8374a2997870ec86ae
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/65a33135e91e6dd661ecdf1194b9d90c49ae3570
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b11d8162c24af4a351d21e2c804d25ca493305e3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b623a8e5d38a69a3ef8644acb1030dd7c7bc28b3

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card