Skip to main content

Linux Kernel CVE-2026-72171

| EUVDEUVD-2026-58929 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-rh82-4rxh-756x
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Local vector confirmed by driver context; PR:L accepted per kernel team rating; kernel memory corruption yields high C/I/A with no scope change.

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

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

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

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 07:24 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

mtd: slram: remove failed entries from the device list

register_device() links a new slram_mtdlist entry before allocating all of the state needed by the entry. If a later allocation, memremap(), or mtd_device_register() fails, the partially initialized entry remains on the global list. A later cleanup can then dereference or free invalid state from that failed entry.

Unwind the partially initialized entry and clear the list tail on each failure path after the entry has been linked.

AnalysisAI

Kernel memory corruption in the Linux kernel's MTD slram driver stems from a link-before-initialize race in register_device(), where new slram_mtdlist entries are inserted into the global device list before all required state (memory allocation, memremap(), and mtd_device_register()) is fully committed. When any of these subsequent operations fail, the partially initialized entry persists on the list, and later cleanup code dereferences or frees invalid kernel memory - enabling potential local privilege escalation from low-privileged access to full kernel compromise. EPSS is 0.22% (13th percentile), no CISA KEV listing exists, and no public exploit has been identified at time of analysis, collectively indicating low near-term exploitation likelihood despite the high CVSS score of 7.8.

Technical ContextAI

The affected subsystem is the slram (simulated RAM) driver within the Linux kernel's Memory Technology Device (MTD) framework, which exposes arbitrary physical memory regions as MTD block devices - primarily used in embedded systems and testing environments. The root cause is an improper error-path unwind in register_device(): the function appends a new slram_mtdlist entry to the tail of the global linked list *before* completing all three initialization steps (heap allocation, memremap() of the physical region, and mtd_device_register()). If any of those steps fail, the partially initialized entry is orphaned on the list with invalid or NULL internal state. Subsequent module unload or list-walking cleanup operations traverse this entry and dereference the invalid state, which can trigger use-after-free or null pointer dereference conditions in kernel context. No formal CWE is assigned, but this maps to CWE-459 (Incomplete Cleanup) and CWE-416 (Use After Free). The vulnerability has existed since Linux 2.6.12 (the initial kernel commit 1da177e4c3f4) and is patched via stable-tree commits across multiple branches, all referenced at https://git.kernel.org/stable/.

RemediationAI

Upgrade to a patched stable kernel: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 7.1.5, or 7.2-rc1 - patch commits are available at https://git.kernel.org/stable/c/200b8bc5b6065b02f3775cf131f14b8e1156a00a and related commits per stable branch. Distribution-maintained kernels (RHEL, Ubuntu, Debian, SUSE) should receive backported fixes through their standard security channels. If kernel upgrade is not immediately feasible, blacklist the slram module to eliminate the attack surface entirely: add blacklist slram to /etc/modprobe.d/blacklist.conf and execute depmod -a, then rmmod slram if currently loaded. This has zero functional impact unless the system is actively using slram for RAM-backed MTD devices, which is rare outside embedded or testing environments. Note that module blacklisting is bypassable by privileged users with CAP_SYS_MODULE, so it is effective primarily as a defense against low-privilege attackers on shared systems. On systems with user namespace restrictions enabled, additionally restrict CONFIG_USER_NS or apply seccomp/LSM policies to limit module loading.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-72171 vulnerability details – vuln.today

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