ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-99163

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

Published Oct 28, 2026 · catalog updated Oct 30, 2026 · tracing/histograms: Reject non-stacktrace fields

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-99163. EPSS is 0.13%. Act only if a listed version of tracing/histograms: Reject non-stacktrace fields is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (tracing/histograms: Reject non-stacktrace fields).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.13%
Remediation
Advisory link
Affected products
Linux Kernel

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().

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Linux Kernel6.3.0 → 6.18.59; 6.19.0 → 7.2.13

How to fix CVE-2026-99163

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-99163. EPSS is 0.13%. Act only if a listed version of tracing/histograms: Reject non-stacktrace fields is installed.

Which versions are affected?

Compare what you have installed with Kernel 6.3.0 → 6.18.59; 6.19.0 → 7.2.13. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 28, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    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

  2. Oct 30, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    Kernel fixed in 6.18.59; Kernel fixed in 7.2.13

  3. Oct 30, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    Kernel fixed in 6.18.59; 6.19.0

  4. Oct 30, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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

Sources

  • BSI CERT-BundGovernment advisoryCVE-2026-99163

    Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

    wid.cert-bund.de
  • CVE.orgVulnerability recordCVE-2026-99163

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-99163

    30-day exploitation probability 0.13%

    first.org
  • OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-99163

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

    osv.dev
  • Tenable CVE DatabaseVulnerability recordCVE-2026-99163

    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

    tenable.com

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 7, 2026
  • Tenable CVE DatabaseNov 1, 2026
  • CVE.orgOct 30, 2026
  • BSI CERT-BundOct 30, 2026
  • OpenSSF OSV / OSV ScannerOct 30, 2026