Skip to main content

Linux Kernel CVE-2026-68177

| EUVDEUVD-2026-55278 HIGH
2026-08-10 Linux GHSA-h49p-x9p9-q3f3
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Race condition between module unload and RCU-deferred trigger firing requires precise timing, warranting AC:H over the assigned AC:L; PR:L reflects typical tracefs access requirements.

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

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

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 14, 2026 - 03:41 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.8 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 11:59 cve.org
HIGH 7.8
CVE Published
Aug 10, 2026 - 11:59 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

tracing: Delay module ref count for "enable_event" trigger

Triggers are now delayed from freeing, but can still be triggered until after the RCU grace period has ended. The freeing of the enable_event data is put into the private_data_free() callback, but the put of the module refcount is done immediately.

It is possible that if a module is removed that has an event that would enable (or disable) it is still active, it can read the data of the module after it is removed causing a use-after-free bug.

Move the trace_event_put_ref() that releases the module into the delayed callback so that the module can not be removed until any reference to its events are finished.

AnalysisAI

Use-after-free in the Linux kernel tracing subsystem's enable_event trigger mechanism allows a local attacker to dereference freed module memory by racing module unloading against an active tracepoint trigger. Affected kernel versions span from commit 61d445af0a7c70018111919e47beaaee15653f2f up to the fix commits on stable branches; patched releases 7.1.6 and 7.2-rc5 are available. No public exploit is identified and EPSS is 0.19% (9th percentile), but the CVSS-rated impact is full compromise of confidentiality, integrity, and availability at the kernel level.

Technical ContextAI

The Linux kernel ftrace/tracefs infrastructure supports 'enable_event' triggers - rules that automatically enable or disable one tracepoint when another fires. The trigger lifecycle is managed using RCU (Read-Copy-Update) for safe deferred memory reclamation: memory is freed only after a full RCU grace period expires. The bug lies in the sequence of cleanup operations: when a trigger targeting a loadable kernel module's event is torn down, the module reference count was decremented via trace_event_put_ref() immediately - before the RCU grace period ended - while the trigger could still legally fire until the grace period elapsed. If the reference count dropped to zero during this window, the kernel module could be fully unloaded and its memory freed while the trigger still held a stale logical reference to the module's event data structures, constituting a classic use-after-free. The fix, applied in commits e091351b38818ef620d27f44f4bfd625f13afbff and 159fdc3e01dca5fdbc412fcd8b239895733a270d, moves trace_event_put_ref() into the private_data_free() delayed callback so the module cannot be fully unloaded until all RCU-deferred references are released. The affected CPE is cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*. No CWE is formally assigned, but the root cause class is unambiguously CWE-416 (Use After Free).

RemediationAI

The primary remediation is to upgrade to Linux kernel 7.1.6 (stable) or 7.2-rc5. The specific fix commits are available at https://git.kernel.org/stable/c/e091351b38818ef620d27f44f4bfd625f13afbff and https://git.kernel.org/stable/c/159fdc3e01dca5fdbc412fcd8b239895733a270d; downstream Linux distributions should be monitored for kernel security errata incorporating these commits. As a compensating control pending patching, administrators should restrict access to the tracefs mount point (typically /sys/kernel/debug/tracing) to root only via mount options or filesystem permissions, preventing non-privileged users from configuring enable_event triggers - note this disables non-root use of kernel tracing tools such as perf-trace-based workflows. Additionally, enforcing kernel lockdown mode (integrity or confidentiality) blocks unprivileged interaction with the tracing infrastructure entirely, but disables a broad range of kernel debugging capabilities as a trade-off. Restricting kernel module loading to trusted administrators via sysctl kernel.modules_disabled=1 after boot, or via LSM policy (SELinux/AppArmor), eliminates the module-unload half of the race and is a lower-impact compensating control. No patch version is independently verified against a formal kernel.org release announcement beyond the EUVD listing.

Vendor StatusVendor

SUSE

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

Share

CVE-2026-68177 vulnerability details – vuln.today

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