CVE-2026-97922

tracing: Free histogram var refs regardless of how often they are referenced

N/A
Published: September 25, 2026 at 10:22 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Free histogram var refs regardless of how often they are referenced Using the same variable three or more times in one hist trigger leaks the variable reference and its strings when the trigger is removed. commit 656fe2ba85e8 ("tracing: Use hist trigger's var_ref array to destroy var_refs") made a trigger's var_refs[] array the only owner of a var ref: destroy_hist_field() returns early for HIST_FIELD_FL_VAR_REF, so the field expressions never destroy one. One entry, freed once, no count needed. commit 8bcebc77e85f ("tracing: Fix histogram code when expression has same var as value") then made repeated references share one object and added a count of them. Only the increment side exists, since those expressions still return early and never drop a reference, so __destroy_hist_field() sees how many references were created rather than how many are left. It frees when the decremented count is 0 or 1, so two references work and three or more leak. Sharing kept one array entry per object, and create_var_ref() searches and appends within a single trigger, so nothing outside it holds the object. Removing a trigger whose variables are still referenced is already refused by check_var_refs() with -EBUSY. Drop the count and free unconditionally.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.1005.4.165.58bcebc77e85f3d7536f96845a0fe94b1dddb6af0bf470f051556b610265ea02ad2102de75e8e619cce28d664054df01997baace61d1defca77689798
Vendor states this is fixed in 4bddcb346a6cf4615ca77f69a589623b877ca267 (fixed)
Vendor states this is fixed in 4cff53bb19412c6f2d90b50678de5c3903f7f96a (fixed)
Vendor states this is fixed in 94bbd65da4ae26592fa1977a74ee94218ab02a26 (fixed)
Vendor states this is fixed in a1f1d64a0a9791c842c4646253daf6ac0313eac7 (fixed)
Vendor states this is fixed in b513a4c60a7aa1f4b4c2a48544ab003cb36f1e94 (fixed)
Vendor states this is fixed in e7b6d67b43caee9183a4374d23641578ea556e6c (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.5 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card