---
id: CVE-2026-46196
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()

  When a tracepoint goes through the 0 -> 1 transition, tracepoint_add_func()
  invokes the su…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()

  When a tracepoint goes through the 0 -> 1 transition, tracepoint_add_func()
  invokes the su…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 4.10, < 6.6.140'
  - 'linux_kernel >= 6.7, < 6.12.88'
  - 'linux_kernel >= 6.13, < 6.18.30'
  - 'linux_kernel >= 6.19, < 7.0.7'
patched:
  - linux_kernel 7.0.7
published: '2026-05-28'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T02:19:50.060'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-46196'
references:
  - url: 'https://git.kernel.org/stable/c/247ed8a969f981bfba3112fd4bb441eaa6cef59c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2c5b8eeea006eb694c81631cd5713d494b80be90'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/342829e042ac00f3d68d442ea92873fb6683f494'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/36ff362235307af95152d510b53c2d9b8773a342'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/4f1756d043e56ea2e9a6c858fb290a0cf6fc2251'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5787052e5f69beb649f3d6a80a8aa37d9e683e4e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7bcadb3c2bc1cf60690e931aadd35fb7bd646a49'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/fad217e16fded7f3c09f8637b0f6a224d58b5f2e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-784472.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00128
epssPercentile: 0.02174
ingestedAt: '2026-10-15T03:30:12.896Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()

When a tracepoint goes through the 0 -> 1 transition, tracepoint_add_func()
invokes the subsystem's ext->regfunc() before attempting to install the
new probe via func_add(). If func_add() then fails (for example, when
allocate_probes() cannot allocate a new probe array under memory pressure
and returns -ENOMEM), the function returns the error without calling the
matching ext->unregfunc(), leaving the side effects of regfunc() behind
with no installed probe to justify them.

For syscall tracepoints this is particularly unpleasant: syscall_regfunc()
bumps sys_tracepoint_refcount and sets SYSCALL_TRACEPOINT on every task.
After a leaked failure, the refcount is stuck at a non-zero value with no
consumer, and every task continues paying the syscall trace entry/exit
overhead until reboot. Other subsystems providing regfunc()/unregfunc()
pairs exhibit similarly scoped persistent state.

Mirror the existing 1 -> 0 cleanup and call ext->unregfunc() in the
func_add() error path, gated on the same condition used there so the
unwind is symmetric with the registration.

## Affected

- `linux_kernel >= 4.10, < 6.6.140`
- `linux_kernel >= 6.7, < 6.12.88`
- `linux_kernel >= 6.13, < 6.18.30`
- `linux_kernel >= 6.19, < 7.0.7`

## Remediation

Upgrade past the affected range:

- `linux_kernel 7.0.7`