CVE-2023-53676

Description

A flaw was found in the Linux kernel's iSCSI target subsystem. When displaying session details for multiple active connections through the configuration filesystem interface, the kernel does not enforce buffer boundaries. A privileged local user can exploit this issue by reading the affected configuration attributes, triggering a buffer overflow that can lead to memory corruption and a Denial of Service (DoS) via system crash.

Statement

A buffer overflow in lio_target_nacl_info_show() (configfs path) used sprintf() in a loop, allowing writes past the sysfs buffer when many iSCSI connections exist. The fix switches to sysfs_emit_at() which enforces bounds. For the CVSS the PR:H because triggering requires local access to the iSCSI target’s configfs attributes—typically restricted to root/CAP_SYS_ADMIN or dedicated management users.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.77.88.8
Attack VectorLocalLocalNetwork
Attack ComplexityLowLowLow
Privileges RequiredHighLowNone
User InteractionNoneNoneRequired
ScopeUnchangedUnchangedUnchanged
ConfidentialityHighHighHigh
Integrity ImpactHighHighHigh
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.