Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99163tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields

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

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 3 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-99163, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected b9453380c1c542fd095a4dbe9251eeba4022bbce – < eba0a6365a0f38f7598a02fc7f9ee341c7efe7f5
    • affected 5f52389bdd9eafb63b3a2f804e02aeb17b6a5f55 – < 326c45c9e201e3ff4c9e9e0e14c2c91364d6c8be
    • affected f3baa42afeea0d5f04ad31525e861199d02210cc – < 6c4e4946febb585d2fc93a02a0cd12cec715bb32
    • affected 00cf3d672a9dd409418647e9f98784c339c3ff63 – < 7e0d05a6234a984ac23b8a563fb7f66f2572b668
    • affected 00cf3d672a9dd409418647e9f98784c339c3ff63 – < 648687f2b448d8527cd7b112fe5d4bd0fec85a87
    • affected 00cf3d672a9dd409418647e9f98784c339c3ff63 – < 1f36e4ddd05d540f363dbaa4c23042549f15b3ef
    • affected 00cf3d672a9dd409418647e9f98784c339c3ff63 – < deb336ae7c7b341591a6862cf6fcfeca97c77dfd
    • affected 00cf3d672a9dd409418647e9f98784c339c3ff63 – < a244c241593b5b38a08f0df2cb43c26574efbdcb
    • affected 5.10.237 – < 5.10.273
    • affected 5.15.124 – < 5.15.224
    • affected 6.1.43 – < 6.1.191
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99163 badge
[![CVE-2026-99163](https://cveledger.app/badge/CVE-2026-99163.svg)](https://cveledger.app/cve/CVE-2026-99163)

Record last updated .