CVE-2026-99163

tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields

Published Oct 28, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields

In check_synth_field(), when a synthetic event field is a stacktrace
(field->is_stack) and the histogram field is not a "long[" stacktrace
array, validation falls through to the generic size and signedness
comparison.

Because parse_synth_field() sets a stacktrace field's type to
"__data_loc unsigned long[]", its size is sizeof(u64) and
synth_field_signed() marks it as signed. Consequently, any 8-byte
signed scalar histogram field passes the fallback check, and its scalar
value is subsequently dereferenced as a kernel stacktrace pointer in
get_field_size() and trace_stack().

Furthermore, checking strstr(hist_field->type, "long[") is insufficient
because tracepoint fields defined with __bitmask() or __rel_bitmask()
also have type "__data_loc unsigned long[]" or "__rel_loc unsigned
long[]", whilst create_hist_field() treats them as 4-byte scalar values
without HIST_FIELD_FL_STACKTRACE.

Propagate HIST_FIELD_FL_STACKTRACE to variable references and field
variables (whilst excluding variable aliases from per-element
stacktrace capture), and reject any mismatch between
HIST_FIELD_FL_STACKTRACE and field->is_stack in check_synth_field().

Analysis

AI-generated

Technical impact

The flaw occurs in the Linux kernel's tracepoint histogram handling. During synthetic event field validation, a stacktraced field that is marked as a stack can bypass proper type checks if its histogram counterpart is not a "long[" stacktrace array. This leads to the kernel interpreting an 8‑byte signed scalar value as a stack pointer. When trace_stack dereferences that value, the kernel may dereference an invalid address, causing an Oops and presenting an opportunity for a denial of service.

Affected Systems

Linux kernel builds that lack the recent commit series fixing the synthetic field validation. The issue is present in every kernel version prior to the inclusion of the commits referenced in the advisory. All architectures that rely on the tracing subsystem and accept user‑supplied synthetic events are affected.

Risk and Exploitability

Based on the description, it is inferred that the attack vector involves crafting a synthetic event with mismatched stacktrace definitions, which requires write access to synthetic events. The EPSS score is 0.00134, indicating a very low but nonzero exploitation probability, and the vulnerability is not flagged in the CISA KEV catalog. However, the flaw can be triggered by any user with permission to write synthetic events, which is a common capability for debugging or performance monitoring. The resulting Oops can crash the system, and because the exploit path is straightforward—crafting an event with mismatched stacktrace definitions—security teams should treat it as a moderate to high risk with a CVSS score of 7.8.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to version that includes the fix referenced by commits 1f36e4ddd05d540f363dbaa4c23042549f15b3ef, a244c241593b5b38a08f0df2cb43c26574efbdcb, or deb336ae7c7b341591a6862cf6fcfeca97c77dfd.
  • Apply the patch from the above commits to the running kernel and reboot to ensure the new module code takes effect.
  • Verify that all synthetic stacktrace fields are correctly marked and that no mismatched types are present in tracepoint definitions.

Generated by OpenCVE AI on November 10, 2026 at 08:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
History
Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Metrics cvssV3_1

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

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields In check_synth_field(), when a synthetic event field is a stacktrace (field->is_stack) and the histogram field is not a "long[" stacktrace array, validation falls through to the generic size and signedness comparison. Because parse_synth_field() sets a stacktrace field's type to "__data_loc unsigned long[]", its size is sizeof(u64) and synth_field_signed() marks it as signed. Consequently, any 8-byte signed scalar histogram field passes the fallback check, and its scalar value is subsequently dereferenced as a kernel stacktrace pointer in get_field_size() and trace_stack(). Furthermore, checking strstr(hist_field->type, "long[") is insufficient because tracepoint fields defined with __bitmask() or __rel_bitmask() also have type "__data_loc unsigned long[]" or "__rel_loc unsigned long[]", whilst create_hist_field() treats them as 4-byte scalar values without HIST_FIELD_FL_STACKTRACE. Propagate HIST_FIELD_FL_STACKTRACE to variable references and field variables (whilst excluding variable aliases from per-element stacktrace capture), and reject any mismatch between HIST_FIELD_FL_STACKTRACE and field->is_stack in check_synth_field().
Title tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-843

    Access of Resource Using Incompatible Type ('Type Confusion')

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 31, 2026, 12:44 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 31, 2026, 1:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 10:35 AM