# CVE-2022-48848: linux: In the Linux kernel, the following vulnerability has been resolved:  tracing/osnoise: Do not unregister events twice...

CVE-2022-48848 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-48848, released July 16, 2024. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2022-48848
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0022
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jul 16, 2024

## Description

In the Linux kernel, the following vulnerability has been resolved:  tracing/osnoise: Do not unregister events twice  Nicolas reported that using:   # trace-cmd record -e all -M 10 -p osnoise --poll  Resulted in the following kernel warning:   ------------[ cut here ]------------  WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370  [...]  CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19  RIP: 0010:tracepoint_probe_unregister+0x280/0x370  [...]  CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0  Call Trace:   <TASK>   osnoise_workload_stop+0x36/0x90   tracing_set_tracer+0x108/0x260   tracing_set_trace_write+0x94/0xd0   ? __check_object_size.part.0+0x10a/0x150   ? selinux_file_permission+0x104/0x150   vfs_write+0xb5/0x290   ksys_write+0x5f/0xe0   do_syscall_64+0x3b/0x90   entry_SYSCALL_64_after_hwframe+0x44/0xae  RIP: 0033:0x7ff919a18127  [...]  ---[ end trace 0000000000000000 ]---  The warning complains about an attempt to unregister an unregistered tracepoint.  This happens on trace-cmd because it first stops tracing, and then switches the tracer to nop. Which is equivalent to:    # cd /sys/kernel/tracing/   # echo osnoise > current_tracer   # echo 0 > tracing_on   # echo nop > current_tracer  The osnoise tracer stops the workload when no trace instance is actually collecting data. This can be caused both by disabling tracing or disabling the tracer itself.  To avoid unregistering events twice, use the existing trace_osnoise_callback_enabled variable to check if the events (and the workload) are actually active before trying to deactivate them.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 5.16.18-1 | [DEBIAN-CVE-2022-48848](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48848.md) | Jul 16, 2024 |
| Linux | linux Debian 13.5 (trixie) | 5.16.18-1 | [DEBIAN-CVE-2022-48848](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48848.md) | Jul 16, 2024 |
| Linux | linux Debian 14 | 5.16.18-1 | [DEBIAN-CVE-2022-48848](https://patchblox.com/security/data/fix/linux/debian-cve-2022-48848.md) | Jul 16, 2024 |

---

Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.