Skip to main content

Linux Kernel EUVDEUVD-2026-38889

| CVE-2026-53021 MEDIUM
Integer Overflow or Wraparound (CWE-190)
2026-06-24 Linux GHSA-mw2m-v92w-q9ww
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local access with low privileges required to issue SCSI UNMAP commands; impact is kernel crash only, no confidentiality or integrity loss.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
7.0 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 15, 2026 - 16:31 vuln.today
CVSS changed
Jul 15, 2026 - 14:22 NVD
5.5 (MEDIUM)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:29 nvd
MEDIUM 5.5
CVE Published
Jun 24, 2026 - 16:29 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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

scsi: target: core: Fix integer overflow in UNMAP bounds check

sbc_execute_unmap() checks LBA + range does not exceed the device capacity, but does not guard against LBA + range wrapping around on 64-bit overflow.

Add an overflow check matching the pattern already used for WRITE_SAME in the same file.

AnalysisAI

Integer overflow in the Linux kernel SCSI target core allows a local attacker with low privileges to crash the kernel via crafted UNMAP commands. The sbc_execute_unmap() function performs a capacity bounds check on LBA + range but fails to guard against 64-bit wraparound, meaning an attacker can supply values that overflow to bypass the check and trigger a kernel panic. No public exploit code or CISA KEV listing exists; EPSS is 0.18% (7th percentile), reflecting the niche attack surface limited to systems actively running SCSI target daemons. Patches are confirmed available across all supported stable kernel branches.

Technical ContextAI

The flaw resides in sbc_execute_unmap() within the Linux kernel's SCSI target core subsystem (LIO / target_core_sbc.c). The SCSI UNMAP command is the SCSI equivalent of TRIM/DISCARD, used to deallocate storage blocks in thin-provisioned environments such as iSCSI targets. The function computes LBA + range to verify the requested unmap region does not exceed device capacity, but this addition uses plain arithmetic without overflow protection. On 64-bit systems, if both values are attacker-controlled and their sum wraps past 2^64, the result appears small and passes the bounds check. CWE-190 (Integer Overflow or Wraparound) is the root cause. The CVE description explicitly notes that a correct overflow check already exists in the same file for WRITE_SAME; this fix brings UNMAP into parity with that pattern. CPE data confirms the affected product as cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*, spanning kernel versions from the introduction commit (traced to the 3.10 era per EUVD) through all unpatched stable branches.

RemediationAI

The primary fix is to upgrade the Linux kernel to one of the patched stable releases: 5.10.258+, 5.15.209+, 6.1.175+, 6.6.141+, 6.12.91+, 6.18.33+, 7.0.10+, or 7.1+. Distribution vendors (RHEL, Debian, Ubuntu, SUSE, etc.) will backport these fixes into their kernel packages; consult vendor security advisories for distribution-specific patch availability. Fix commits are available at https://git.kernel.org/stable/c/c08ab702c4699c6efb9d60bdb15b73e7a627ee7e and sibling commits for other stable branches. If patching is not immediately feasible, a viable compensating control is to disable or unload the SCSI target kernel module (modprobe -r target_core_mod) on systems that do not need iSCSI or SCSI target functionality - note this will disable storage target serving if in use. Restricting local user access to SCSI target interfaces via namespace isolation or reduced privilege levels reduces the attack surface but does not eliminate it.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.177 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.155 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.206 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.152 Affected
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected
Image SLES15-SP7-BYOS-Azure Image SLES15-SP7-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-Aliyun Image SLES15-SP7-CHOST-BYOS-Azure Image SLES15-SP7-CHOST-BYOS-EC2 Image SLES15-SP7-CHOST-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-GDC Image SLES15-SP7-CHOST-BYOS-SAP-CCloud Image SLES15-SP7-EC2 Image SLES15-SP7-EC2-ECS-HVM Image SLES15-SP7-GCE Image SLES15-SP7-HPC-BYOS-Azure Image SLES15-SP7-HPC-BYOS-EC2 Image SLES15-SP7-HPC-BYOS-GCE Image SLES15-SP7-Hardened-BYOS-Azure Image SLES15-SP7-Hardened-BYOS-EC2 Image SLES15-SP7-Hardened-BYOS-GCE Image SLES15-SP7-SAPCAL-Azure Image SLES15-SP7-SAPCAL-EC2 Image SLES15-SP7-SAPCAL-GCE Affected
Image SLES15-SP7-SAP-Azure Image SLES15-SP7-SAP-Azure-3P Image SLES15-SP7-SAP-BYOS-Azure Image SLES15-SP7-SAP-BYOS-EC2 Image SLES15-SP7-SAP-BYOS-GCE Image SLES15-SP7-SAP-EC2 Image SLES15-SP7-SAP-GCE Image SLES15-SP7-SAP-Hardened-Azure Image SLES15-SP7-SAP-Hardened-BYOS-Azure Image SLES15-SP7-SAP-Hardened-BYOS-EC2 Image SLES15-SP7-SAP-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Hardened-GCE Affected

Share

EUVD-2026-38889 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy