CVE-2023-53320 Affecting kernel-rt-64k-debug-devel-matched package, versions *


Severity

Recommended
low

Based on CentOS security rating.

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 IDSNYK-CENTOS9-KERNELRT64KDEBUGDEVELMATCHED-12830853
  • published17 Sept 2025
  • disclosed16 Sept 2025

Introduced: 16 Sep 2025

NewCVE-2023-53320  (opens in a new tab)

How to fix?

There is no fixed version for Centos:9 kernel-rt-64k-debug-devel-matched.

NVD Description

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

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

scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info()

The function mpi3mr_get_all_tgt_info() has four issues:

  1. It calculates valid entry length in alltgt_info assuming the header part of the struct mpi3mr_device_map_info would equal to sizeof(u32). The correct size is sizeof(u64).

  2. When it calculates the valid entry length kern_entrylen, it excludes one entry by subtracting 1 from num_devices.

  3. It copies num_device by calling memcpy(). Substitution is enough.

  4. It does not specify the calculated length to sg_copy_from_buffer(). Instead, it specifies the payload length which is larger than the alltgt_info size. It causes "BUG: KASAN: slab-out-of-bounds".

Fix the issues by using the correct header size, removing the subtraction from num_devices, replacing the memcpy() with substitution and specifying the correct length to sg_copy_from_buffer().

CVSS Base Scores

version 3.1