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

tracing: Take the reference before publishing the named histogram trigger

event_hist_trigger_named_init() puts the trigger on the global
named_triggers list and only then takes the reference on the trigger it
shares its histogram with:

data->ref++;

save_named_trigger(data->named_data->name, data);

ret = event_hist_trigger_init(data->named_data);
if (ret < 0) {
kfree(data->cmd_ops);
data->cmd_ops = &trigger_hist_cmd;
}

return ret;

event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and
nothing takes the trigger back off the list on the way out.
event_hist_trigger_parse() frees it, and the next lookup by name reads the
freed object:

BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0
Read of size 8 at addr ffff888009346860 by task init/1
find_named_trigger+0xac/0xc0
hist_register_trigger+0xc1/0xa00
event_hist_trigger_parse+0x3146/0x6af0
event_trigger_write+0xce/0x160
Freed by task 67:
kfree+0x154/0x420
trigger_kthread_fn+0xfd/0x160

Do the reference first and publish once it has succeeded, so that nothing
which can fail runs after the trigger becomes findable.
Published: 2026-09-25
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel use‑after‑free in tracing subsystem
Action: Apply Patch
AI Analysis

Impact

The flaw occurs when a named histogram trigger is inserted into the global list before its reference count is safely incremented. If the trigger’s initialization fails, the trigger is freed while still present in the list, causing subsequent lookups to access freed memory. This results in a use‑after‑free (CWE‑825) that can crash the kernel. Based on the description, an attacker who can control the trigger data could potentially trigger a kernel panic, which might allow escalation of privileges if the attacker already has local code execution.

Affected Systems

All Linux kernel releases that have not applied the maintainer’s patch are vulnerable. The affected code resides in the upstream kernel, so every distribution built from a vulnerable kernel version is impacted, regardless of specific distribution. No explicit version range is provided, so users should assume any kernel containing the legacy tracing implementation is at risk.

Risk and Exploitability

EPSS score is < 1% and the vulnerability is not listed in CISA KEV, implying no publicly documented exploits. The bug exposes no externally reachable interface; an attacker needs local or privileged access to create a named histogram trigger. While the flaw permits a kernel crash that might lead to privilege escalation, the low EPSS suggests exploitation is unlikely. The CVSS score of 5.5 indicates a medium severity use‑after‑free, but the lack of widespread exploitation data still warrants timely patching.

Generated by OpenCVE AI on October 1, 2026 at 05:35 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to the latest version that includes the tracing use‑after‑free fix
  • Reboot the system after applying the update to ensure the kernel patch takes effect
  • If an immediate kernel update is not possible, disable named histogram triggers or avoid using any affected tracing features until a patch is available

Generated by OpenCVE AI on October 1, 2026 at 05:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-6568-1 linux security update
History

Wed, 21 Oct 2026 13:15:00 +0000


Sat, 03 Oct 2026 11:15:00 +0000


Wed, 30 Sep 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 25 Sep 2026 10:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger event_hist_trigger_named_init() puts the trigger on the global named_triggers list and only then takes the reference on the trigger it shares its histogram with: data->ref++; save_named_trigger(data->named_data->name, data); ret = event_hist_trigger_init(data->named_data); if (ret < 0) { kfree(data->cmd_ops); data->cmd_ops = &trigger_hist_cmd; } return ret; event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and nothing takes the trigger back off the list on the way out. event_hist_trigger_parse() frees it, and the next lookup by name reads the freed object: BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0 Read of size 8 at addr ffff888009346860 by task init/1 find_named_trigger+0xac/0xc0 hist_register_trigger+0xc1/0xa00 event_hist_trigger_parse+0x3146/0x6af0 event_trigger_write+0xce/0x160 Freed by task 67: kfree+0x154/0x420 trigger_kthread_fn+0xfd/0x160 Do the reference first and publish once it has succeeded, so that nothing which can fail runs after the trigger becomes findable.
Title tracing: Take the reference before publishing the named histogram trigger
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-21T12:53:38.904Z

Reserved: 2026-09-25T10:18:58.202Z

Link: CVE-2026-97919

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-25T11:17:18.923

Modified: 2026-10-21T13:21:16.177

Link: CVE-2026-97919

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-25T00:00:00Z

Links: CVE-2026-97919 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T05:45:17Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference