Is there a patch available for CVE-2026-99247?

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

Linux CVE-2026-99247

EUVD-2026-115777

2026-11-03 Linux

GHSA-92rv-c2p9-qp48

Denial Of Service Linux

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: Do not initialize tracefs work if tracing is disabled

If trace buffer allocation fails during early boot (e.g. in early_trace_init() -> allocate_trace_buffers()), tracing_disabled is left set to 1 and the global trace array events list remains uninitialized.

Later during boot, tracer_init_tracefs() (invoked via fs_initcall) queues tracerfs_init_work asynchronously without checking if tracing was disabled. When tracer_init_tracefs_work_func() runs, it calls event_trace_init() and init_tracer_tracefs(&global_trace, NULL) unconditionally. This leads to __find_event_file() dereferencing an uninitialized tr->events list, causing an early boot NULL pointer dereference Oops:

BUG: Kernel NULL pointer dereference on read at 0x00000010 Faulting instruction address: 0xc000000000485be0 Oops: Kernel access of bad area, sig: 7 [#1] ... NIP [c000000000485be0] __find_event_file+0x70/0x3c0 LR [c000000000448874] init_tracer_tracefs+0x274/0xc80 Call Trace: init_tracer_tracefs+0x274/0xc80 tracer_init_tracefs_work_func+0x50/0x320 process_one_work+0x1e8/0x5c0 worker_thread+0x1dc/0x3d0 kthread+0x194/0x1b0 start_kernel_thread+0x14/0x18

Check tracing_disabled at the beginning of tracer_init_tracefs_work_func() and return immediately if tracing is disabled or failed to initialize, preventing the crash.

Affected VersionsENISA

Linux patch: 6.1.191

Linux 6621a7004684bfcff5af4c8e4d37989941f42a6b <e8665e884e076d894f3eed8b9ea28e37a6448604

Linux patch: 6.6.161

Linux 6621a7004684bfcff5af4c8e4d37989941f42a6b <813e18881c6472eb229a63180ff42c808e3e949b

Linux 6621a7004684bfcff5af4c8e4d37989941f42a6b <afd38b10b1c6a5c5d6952b15b990596dab9684e6

Linux 5.19

Linux patch: 7.3

Linux 6621a7004684bfcff5af4c8e4d37989941f42a6b <7539c61f522ff693d9565a0411386c2236e776cd

Linux patch: 0

Linux patch: 7.2.13

Linux 6621a7004684bfcff5af4c8e4d37989941f42a6b <e8cfcd7e60eaa3b0dea4d71c64499604e7081736

Linux patch: 6.12.115

Linux 6621a7004684bfcff5af4c8e4d37989941f42a6b <b3b974008388ab59e44d764ba7a63c988fec2524

Linux patch: 6.18.59

Affected Packages

euvd linux no fix

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

Nov 03, 2026 - 12:16 EUVD

CVE Published

Nov 03, 2026 - 11:18 cve.org

UNKNOWN (no severity yet)

Threat Intelligence Overview

Data Quality

1 sources

Confidence: Low

EUVD

CVE.org

VulDB

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.