{"api_version":"1","generated_at":"2026-06-02T01:59:40+00:00","cve":"CVE-2026-46196","urls":{"html":"https://cve.report/CVE-2026-46196","api":"https://cve.report/api/cve/CVE-2026-46196.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46196","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46196"},"summary":{"title":"tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()\n\nWhen a tracepoint goes through the 0 -> 1 transition, tracepoint_add_func()\ninvokes the subsystem's ext->regfunc() before attempting to install the\nnew probe via func_add(). If func_add() then fails (for example, when\nallocate_probes() cannot allocate a new probe array under memory pressure\nand returns -ENOMEM), the function returns the error without calling the\nmatching ext->unregfunc(), leaving the side effects of regfunc() behind\nwith no installed probe to justify them.\n\nFor syscall tracepoints this is particularly unpleasant: syscall_regfunc()\nbumps sys_tracepoint_refcount and sets SYSCALL_TRACEPOINT on every task.\nAfter a leaked failure, the refcount is stuck at a non-zero value with no\nconsumer, and every task continues paying the syscall trace entry/exit\noverhead until reboot. Other subsystems providing regfunc()/unregfunc()\npairs exhibit similarly scoped persistent state.\n\nMirror the existing 1 -> 0 cleanup and call ext->unregfunc() in the\nfunc_add() error path, gated on the same condition used there so the\nunwind is symmetric with the registration.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-28 10:16:35","updated_at":"2026-05-28 13:44:01"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/247ed8a969f981bfba3112fd4bb441eaa6cef59c","name":"https://git.kernel.org/stable/c/247ed8a969f981bfba3112fd4bb441eaa6cef59c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/342829e042ac00f3d68d442ea92873fb6683f494","name":"https://git.kernel.org/stable/c/342829e042ac00f3d68d442ea92873fb6683f494","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/fad217e16fded7f3c09f8637b0f6a224d58b5f2e","name":"https://git.kernel.org/stable/c/fad217e16fded7f3c09f8637b0f6a224d58b5f2e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2c5b8eeea006eb694c81631cd5713d494b80be90","name":"https://git.kernel.org/stable/c/2c5b8eeea006eb694c81631cd5713d494b80be90","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7bcadb3c2bc1cf60690e931aadd35fb7bd646a49","name":"https://git.kernel.org/stable/c/7bcadb3c2bc1cf60690e931aadd35fb7bd646a49","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46196","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46196","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8cf868affdc459beee1a941df0cfaba1673740e3 247ed8a969f981bfba3112fd4bb441eaa6cef59c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8cf868affdc459beee1a941df0cfaba1673740e3 7bcadb3c2bc1cf60690e931aadd35fb7bd646a49 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8cf868affdc459beee1a941df0cfaba1673740e3 2c5b8eeea006eb694c81631cd5713d494b80be90 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8cf868affdc459beee1a941df0cfaba1673740e3 342829e042ac00f3d68d442ea92873fb6683f494 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8cf868affdc459beee1a941df0cfaba1673740e3 fad217e16fded7f3c09f8637b0f6a224d58b5f2e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.140 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.88 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.30 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.7 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"46196","cve":"CVE-2026-46196","epss":"0.000180000","percentile":"0.050770000","score_date":"2026-06-01","updated_at":"2026-06-02 00:05:20"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/tracepoint.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"247ed8a969f981bfba3112fd4bb441eaa6cef59c","status":"affected","version":"8cf868affdc459beee1a941df0cfaba1673740e3","versionType":"git"},{"lessThan":"7bcadb3c2bc1cf60690e931aadd35fb7bd646a49","status":"affected","version":"8cf868affdc459beee1a941df0cfaba1673740e3","versionType":"git"},{"lessThan":"2c5b8eeea006eb694c81631cd5713d494b80be90","status":"affected","version":"8cf868affdc459beee1a941df0cfaba1673740e3","versionType":"git"},{"lessThan":"342829e042ac00f3d68d442ea92873fb6683f494","status":"affected","version":"8cf868affdc459beee1a941df0cfaba1673740e3","versionType":"git"},{"lessThan":"fad217e16fded7f3c09f8637b0f6a224d58b5f2e","status":"affected","version":"8cf868affdc459beee1a941df0cfaba1673740e3","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/tracepoint.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.10"},{"lessThan":"4.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.140","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.88","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.30","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.140","versionStartIncluding":"4.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.88","versionStartIncluding":"4.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.30","versionStartIncluding":"4.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.7","versionStartIncluding":"4.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1-rc1","versionStartIncluding":"4.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()\n\nWhen a tracepoint goes through the 0 -> 1 transition, tracepoint_add_func()\ninvokes the subsystem's ext->regfunc() before attempting to install the\nnew probe via func_add(). If func_add() then fails (for example, when\nallocate_probes() cannot allocate a new probe array under memory pressure\nand returns -ENOMEM), the function returns the error without calling the\nmatching ext->unregfunc(), leaving the side effects of regfunc() behind\nwith no installed probe to justify them.\n\nFor syscall tracepoints this is particularly unpleasant: syscall_regfunc()\nbumps sys_tracepoint_refcount and sets SYSCALL_TRACEPOINT on every task.\nAfter a leaked failure, the refcount is stuck at a non-zero value with no\nconsumer, and every task continues paying the syscall trace entry/exit\noverhead until reboot. Other subsystems providing regfunc()/unregfunc()\npairs exhibit similarly scoped persistent state.\n\nMirror the existing 1 -> 0 cleanup and call ext->unregfunc() in the\nfunc_add() error path, gated on the same condition used there so the\nunwind is symmetric with the registration."}],"providerMetadata":{"dateUpdated":"2026-05-28T09:36:49.293Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/247ed8a969f981bfba3112fd4bb441eaa6cef59c"},{"url":"https://git.kernel.org/stable/c/7bcadb3c2bc1cf60690e931aadd35fb7bd646a49"},{"url":"https://git.kernel.org/stable/c/2c5b8eeea006eb694c81631cd5713d494b80be90"},{"url":"https://git.kernel.org/stable/c/342829e042ac00f3d68d442ea92873fb6683f494"},{"url":"https://git.kernel.org/stable/c/fad217e16fded7f3c09f8637b0f6a224d58b5f2e"}],"title":"tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46196","datePublished":"2026-05-28T09:36:49.293Z","dateReserved":"2026-05-13T15:03:33.104Z","dateUpdated":"2026-05-28T09:36:49.293Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-28 10:16:35","lastModifiedDate":"2026-05-28 13:44:01","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46196","Ordinal":"1","Title":"tracepoint: balance regfunc() on func_add() failure in tracepoin","CVE":"CVE-2026-46196","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46196","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()\n\nWhen a tracepoint goes through the 0 -> 1 transition, tracepoint_add_func()\ninvokes the subsystem's ext->regfunc() before attempting to install the\nnew probe via func_add(). If func_add() then fails (for example, when\nallocate_probes() cannot allocate a new probe array under memory pressure\nand returns -ENOMEM), the function returns the error without calling the\nmatching ext->unregfunc(), leaving the side effects of regfunc() behind\nwith no installed probe to justify them.\n\nFor syscall tracepoints this is particularly unpleasant: syscall_regfunc()\nbumps sys_tracepoint_refcount and sets SYSCALL_TRACEPOINT on every task.\nAfter a leaked failure, the refcount is stuck at a non-zero value with no\nconsumer, and every task continues paying the syscall trace entry/exit\noverhead until reboot. Other subsystems providing regfunc()/unregfunc()\npairs exhibit similarly scoped persistent state.\n\nMirror the existing 1 -> 0 cleanup and call ext->unregfunc() in the\nfunc_add() error path, gated on the same condition used there so the\nunwind is symmetric with the registration.","Type":"Description","Title":"tracepoint: balance regfunc() on func_add() failure in tracepoin"}]}}}