Vulnerability · Published Oct 28, 2026 · Assigned by Linux

CVE-2026-99141tracing: Fix crash in print_graph_function_event()

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 95.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash in print_graph_function_event() tracing_set_tracer() assigns the flags of the newly selected tracer with: tr->current_trace_flags = t->flags ? : t->tracer->flags; If the new tracer defines neither static flags nor default flags, like hwlat, irqsoff or wakeup, add_tracer() has no per instance flags copy for it, and both operands are NULL, so tr->current_trace_flags ends up being NULL as well. The ring buffer is not cleared when switching tracers: it is reset inside tracer_init(), after current_trace_flags was already assigned. If the buffer still holds function_graph entries of the previous tracer, printing one of them dereferences the NULL pointer. This was hit by cat trace during an ftrace stress test: BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode RIP: 0010:print_graph_function_event+0xe/0x20 Call Trace: s_show+0x4d/0x110 seq_read_iter+0x2d4/0x490 seq_read+0x130/0x170 vfs_read+0xb5/0x370 ksys_read+0x6d/0xe0 do_syscall_64+0xbc/0x450 The snapshot buffer is not reset at all, so this can be reproduced without a race: echo function_graph > /sys/kernel/tracing/current_tracer echo 1 > /sys/kernel/tracing/snapshot echo hwlat > /sys/kernel/tracing/current_tracer cat /sys/kernel/tracing/snapshot Rather than teaching every user of tr->current_trace_flags about this corner case, make sure it is never NULL: when the newly selected tracer has no flags at all, tracing_set_tracer() falls back to a static empty no_tracer_flags. run_tracer_selftest() can hit the same case, so the same fallback is added there too. The existing users already handle opts == NULL, so these tracers keep behaving as before.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.2.13-1DEBIAN-CVE-2026-99141
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux7.3.0-10.10UBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-aws7.3.0-1004.4UBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-azureno fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-gcp7.3.0-1004.4UBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-oracle7.3.0-1004.4UBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-raspi7.3.0-1004.4UBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-realtime7.3.0-10.10.1UBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99141
Ubuntu:26.10linux-riscv7.3.0-10.10.1UBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-99141
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-99141
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-99141

Affected products (as reported)

VendorProductVersions
Linux Linux e29aa918a928408c3e64b0d1025e4eb9f6fc549e – before b1547c6ba93b8863010aa324cd20c441f886f23ee29aa918a928408c3e64b0d1025e4eb9f6fc549e – before 3cc117514d69067a94d6c7479730dce41e678f50
Linux Linux 6.19

References