Is there a patch available for EUVD-2026-111915?

Yes, a patch is available for EUVD-2026-111915. Update the affected software to the latest version immediately.

Linux EUVD-2026-111915

| CVE-2026-99163

2026-10-28 Linux

GHSA-8cf9-783r-h9xg

View

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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

Affected VersionsENISA

Linux patch: 7.2.13

Linux 00cf3d672a9dd409418647e9f98784c339c3ff63 <1f36e4ddd05d540f363dbaa4c23042549f15b3ef

Linux patch: 6.18.59

Linux 5.15.124 <5.16

Linux patch: 0

Linux 5.10.237 <5.11

Linux 6.3

Linux 00cf3d672a9dd409418647e9f98784c339c3ff63 <a244c241593b5b38a08f0df2cb43c26574efbdcb

Linux 6.1.43 <6.2

Linux f3baa42afeea0d5f04ad31525e861199d02210cc

Linux b9453380c1c542fd095a4dbe9251eeba4022bbce

Linux patch: 7.3

Linux 5f52389bdd9eafb63b3a2f804e02aeb17b6a5f55

Linux 00cf3d672a9dd409418647e9f98784c339c3ff63 <deb336ae7c7b341591a6862cf6fcfeca97c77dfd

Affected Packages

euvd linux fix: 5.11, 5.16, 6.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Lifecycle Timeline

Patch available

Oct 28, 2026 - 11:02 EUVD

CVE Published

Oct 28, 2026 - 10:35 cve.org

UNKNOWN (no severity yet)

Threat Intelligence Overview

Data Quality

2 sources

Confidence: Low

EUVD

CVE.org

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity Not scored yet

CISA KEV No

Public POC No

EPSS N/A

Patch available Yes

Active threat No

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.