tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.6.140, Kernel 6.18.30, Kernel 7.0.7 and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=4.10 <6.6.140, >=6.13 <6.18.30, >=6.19 <7.0.7, >=6.7 <6.12.88, >=8cf868affdc459beee1a941df0cfaba1673740e3 <2c5b8eeea006eb694c81631cd5713d494b80be90, >=8cf868affdc459beee1a941df0cfaba1673740e3 <342829e042ac00f3d68d442ea92873fb6683f494, >=8cf868affdc459beee1a941df0cfaba1673740e3 <36ff362235307af95152d510b53c2d9b8773a342, >=8cf868affdc459beee1a941df0cfaba1673740e3 <4f1756d043e56ea2e9a6c858fb290a0cf6fc2251, >=8cf868affdc459beee1a941df0cfaba1673740e3 <5787052e5f69beb649f3d6a80a8aa37d9e683e4e, >=8cf868affdc459beee1a941df0cfaba1673740e3 <7bcadb3c2bc1cf60690e931aadd35fb7bd646a49, >=8cf868affdc459beee1a941df0cfaba1673740e3 <fad217e16fded7f3c09f8637b0f6a224d58b5f2e, =4.10, >=8cf868affdc459beee1a941df0cfaba1673740e3 <247ed8a969f981bfba3112fd4bb441eaa6cef59c | 6.6.140, 6.18.30, 7.0.7, 6.12.88, 2c5b8eeea006eb694c81631cd5713d494b80be90, 342829e042ac00f3d68d442ea92873fb6683f494, 36ff362235307af95152d510b53c2d9b8773a342, 4f1756d043e56ea2e9a6c858fb290a0cf6fc2251, 5787052e5f69beb649f3d6a80a8aa37d9e683e4e, 7bcadb3c2bc1cf60690e931aadd35fb7bd646a49, fad217e16fded7f3c09f8637b0f6a224d58b5f2e, 247ed8a969f981bfba3112fd4bb441eaa6cef59c |
| linux-kernel: Kernel | >=4.10.0 <5.10.259, >=5.11.0 <5.15.210, >=5.16.0 <6.1.176, >=6.13.0 <6.18.30, >=6.19.0 <7.0.7, >=6.2.0 <6.6.140, >=6.7.0 <6.12.88 | 5.10.259, 5.15.210, 6.1.176, 6.18.30, 7.0.7, 6.6.140, 6.12.88 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket