Double Free Affecting kernel-rt-64k-debug-modules-internal package, versions *


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.02% (4th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Double Free vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL9-KERNELRT64KDEBUGMODULESINTERNAL-12882139
  • published18 Sept 2025
  • disclosed17 Sept 2025

Introduced: 17 Sep 2025

NewCVE-2023-53360  (opens in a new tab)
CWE-415  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 kernel-rt-64k-debug-modules-internal.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-64k-debug-modules-internal package and not the kernel-rt-64k-debug-modules-internal package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1