CVE-2023-53376 remediation guide

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Use number of bits to manage bitmap sizes To allocate bitmaps, the mpi3mr driver calculates sizes of bitmaps using byte as unit. However, bitmap helper functions assume that bitmaps are allocated using unsigned long as unit. This gap causes memory access beyond the bitmap sizes and results in "BUG: KASAN: slab-out-of-bounds". The BUG was observed at firmware download to eHBA-9600. Call trace indicated that the out-of-bounds access happened in find_first_zero_bit() called from mpi3mr_send_event_ack() for miroc-...

Open CVE record

ProductLinux Linux, linux kernel

Affected versions>= 824a156633dfdb0e17979a0d0bb2c757d1bb949c < 6a675a6d57d31da43d8da576465c1cd5d5b0bd3d, >= 824a156633dfdb0e17979a0d0bb2c757d1bb949c < 8ac713d2e9845e9234bb12ae5903040685d5aff9, >= 824a156633dfdb0e17979a0d0bb2c757d1bb949c < 339e61565f81a6534afdc18fd854b2e2628bf5db, >= 5.14, >= 5.14 < 6.1.18, >= 6.2 < 6.2.5

Fixed versions6.1.18, 6.2.5

Priority basisReview · CVSS 7.1 · EPSS 0.15%

Identify the affected asset

Confirm whether Linux Linux, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 824a156633dfdb0e17979a0d0bb2c757d1bb949c < 6a675a6d57d31da43d8da576465c1cd5d5b0bd3d, >= 824a156633dfdb0e17979a0d0bb2c757d1bb949c < 8ac713d2e9845e9234bb12ae5903040685d5aff9, >= 824a156633dfdb0e17979a0d0bb2c757d1bb949c < 339e61565f81a6534afdc18fd854b2e2628bf5db, >= 5.14, >= 5.14 < 6.1.18, >= 6.2 < 6.2.5. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.1.18, 6.2.5. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.