Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Authoritative record:CVE-2026-99163

Not known to be exploited · fixed in deb336ae7c7b341591a6862cf6fcfeca97c77dfd : update Linux kernel when convenient.

Data as of 28 Oct 2026, 13:57 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in deb336ae7c7b341591a6862cf6fcfeca97c77dfd, a244c241593b5b38a08f0df2cb43c26574efbdcb, 6.2 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.10.237 <5.11
  • >=5.15.124 <5.16
  • >=6.1.43 <6.2
Fixed in
  • deb336ae7c7b341591a6862cf6fcfeca97c77dfd
  • a244c241593b5b38a08f0df2cb43c26574efbdcb
  • 6.2
  • 5.16
  • 5.11
  • 1f36e4ddd05d540f363dbaa4c23042549f15b3ef
LinuxLinuxAffected
  • =6.3
Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel to properly validate synthetic stacktrace fields and reject invalid histogram fields. Users should update to a kernel version that includes this fix once available.

Description

A vulnerability in the Linux kernel tracing subsystem allows improper handling of synthetic stacktrace fields in histograms. Specifically, non-stacktrace fields can be incorrectly accepted as stacktrace fields due to insufficient type validation, potentially leading to dereferencing scalar values as kernel stacktrace pointers. This issue has been resolved by improving validation to reject mismatches between stacktrace flags and field types.

References

Community reviews

Loading reviews…