CVE-2026-99247 json
tracing: Do not initialize tracefs work if tracing is disabled
published 2026-11-03 5 d ago modified 2026-11-03 5 d ago also EUVD-2026-115777
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.161, 6.12.115, 6.18.59, 7.2.13, 7.3
- linux Debian 13 6.12.115-1
- linux Debian 14 7.2.13-1
debian advisories DEBIAN-CVE-2026-99247
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99247
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-112601
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/e8665e884e076d894f3eed8b9ea28e37a6448604 commit
- git.kernel.org/stable/c/e8cfcd7e60eaa3b0dea4d71c64499604e7081736 commit
- git.kernel.org/stable/c/afd38b10b1c6a5c5d6952b15b990596dab9684e6 commit
- git.kernel.org/stable/c/813e18881c6472eb229a63180ff42c808e3e949b commit
- git.kernel.org/stable/c/7539c61f522ff693d9565a0411386c2236e776cd commit
- git.kernel.org/stable/c/b3b974008388ab59e44d764ba7a63c988fec2524 commit
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/e8665e884e076d894f3eed8b9ea28e37a6448604
- git.kernel.org /stable/c/e8cfcd7e60eaa3b0dea4d71c64499604e7081736
- git.kernel.org /stable/c/afd38b10b1c6a5c5d6952b15b990596dab9684e6
- git.kernel.org /stable/c/813e18881c6472eb229a63180ff42c808e3e949b
- git.kernel.org /stable/c/7539c61f522ff693d9565a0411386c2236e776cd
- git.kernel.org /stable/c/b3b974008388ab59e44d764ba7a63c988fec2524
Sources
- CVE List CVE-2026-99247
- NVD CVE-2026-99247
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.