fkie_cve-2022-49801
Vulnerability from fkie_nvd
Published
2025-05-01 15:16
Modified
2025-05-02 13:53
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix memory leak in tracing_read_pipe()
kmemleak reports this issue:
unreferenced object 0xffff888105a18900 (size 128):
comm "test_progs", pid 18933, jiffies 4336275356 (age 22801.766s)
hex dump (first 32 bytes):
25 73 00 90 81 88 ff ff 26 05 00 00 42 01 58 04 %s......&...B.X.
03 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000560143a1>] __kmalloc_node_track_caller+0x4a/0x140
[<000000006af00822>] krealloc+0x8d/0xf0
[<00000000c309be6a>] trace_iter_expand_format+0x99/0x150
[<000000005a53bdb6>] trace_check_vprintf+0x1e0/0x11d0
[<0000000065629d9d>] trace_event_printf+0xb6/0xf0
[<000000009a690dc7>] trace_raw_output_bpf_trace_printk+0x89/0xc0
[<00000000d22db172>] print_trace_line+0x73c/0x1480
[<00000000cdba76ba>] tracing_read_pipe+0x45c/0x9f0
[<0000000015b58459>] vfs_read+0x17b/0x7c0
[<000000004aeee8ed>] ksys_read+0xed/0x1c0
[<0000000063d3d898>] do_syscall_64+0x3b/0x90
[<00000000a06dda7f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
iter->fmt alloced in
tracing_read_pipe() -> .. ->trace_iter_expand_format(), but not
freed, to fix, add free in tracing_release_pipe()
References
Impacted products
| Vendor | Product | Version |
|---|
{
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix memory leak in tracing_read_pipe()\n\nkmemleak reports this issue:\n\nunreferenced object 0xffff888105a18900 (size 128):\n comm \"test_progs\", pid 18933, jiffies 4336275356 (age 22801.766s)\n hex dump (first 32 bytes):\n 25 73 00 90 81 88 ff ff 26 05 00 00 42 01 58 04 %s......\u0026...B.X.\n 03 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................\n backtrace:\n [\u003c00000000560143a1\u003e] __kmalloc_node_track_caller+0x4a/0x140\n [\u003c000000006af00822\u003e] krealloc+0x8d/0xf0\n [\u003c00000000c309be6a\u003e] trace_iter_expand_format+0x99/0x150\n [\u003c000000005a53bdb6\u003e] trace_check_vprintf+0x1e0/0x11d0\n [\u003c0000000065629d9d\u003e] trace_event_printf+0xb6/0xf0\n [\u003c000000009a690dc7\u003e] trace_raw_output_bpf_trace_printk+0x89/0xc0\n [\u003c00000000d22db172\u003e] print_trace_line+0x73c/0x1480\n [\u003c00000000cdba76ba\u003e] tracing_read_pipe+0x45c/0x9f0\n [\u003c0000000015b58459\u003e] vfs_read+0x17b/0x7c0\n [\u003c000000004aeee8ed\u003e] ksys_read+0xed/0x1c0\n [\u003c0000000063d3d898\u003e] do_syscall_64+0x3b/0x90\n [\u003c00000000a06dda7f\u003e] entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\niter-\u003efmt alloced in\n tracing_read_pipe() -\u003e .. -\u003etrace_iter_expand_format(), but not\nfreed, to fix, add free in tracing_release_pipe()"
},
{
"lang": "es",
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tracing: Fix memory leakage in tracing_read_pipe() kmemleak informa de este problema: unreferenced object 0xffff888105a18900 (size 128): comm \"test_progs\", pid 18933, jiffies 4336275356 (age 22801.766s) hex dump (first 32 bytes): 25 73 00 90 81 88 ff ff 26 05 00 00 42 01 58 04 %s......\u0026amp;...BX 03 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [\u0026lt;00000000560143a1\u0026gt;] __kmalloc_nodo_rastreador_llamador+0x4a/0x140 [\u0026lt;000000006af00822\u0026gt;] krealloc+0x8d/0xf0 [\u0026lt;00000000c309be6a\u0026gt;] trace_iter_expand_format+0x99/0x150 [\u0026lt;000000005a53bdb6\u0026gt;] trace_check_vprintf+0x1e0/0x11d0 [\u0026lt;0000000065629d9d\u0026gt;] trace_event_printf+0xb6/0xf0 [\u0026lt;000000009a690dc7\u0026gt;] trace_raw_output_bpf_trace_printk+0x89/0xc0 [\u0026lt;00000000d22db172\u0026gt;] imprimir_l\u00ednea_de_seguimiento+0x73c/0x1480 [\u0026lt;00000000cdba76ba\u0026gt;] conducto_de_lectura_de_seguimiento+0x45c/0x9f0 [\u0026lt;0000000015b58459\u0026gt;] lectura_vfs+0x17b/0x7c0 [\u0026lt;000000004aeee8ed\u0026gt;] lectura_ksys+0xed/0x1c0 [\u0026lt;0000000063d3d898\u0026gt;] hacer_llamada_al_sistema_64+0x3b/0x90 [\u0026lt;00000000a06dda7f\u0026gt;] entrada_SYSCALL_64_despu\u00e9s_de_hwframe+0x63/0xcd iter-\u0026gt;fmt asignado en conducto_de_lectura_de_seguimiento() -\u0026gt; .. -\u0026gt;trace_iter_expand_format(), pero no se libera, para solucionarlo, agregue free en tracing_release_pipe()"
}
],
"id": "CVE-2022-49801",
"lastModified": "2025-05-02T13:53:20.943",
"metrics": {},
"published": "2025-05-01T15:16:03.407",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2c21ee020ce43d744ecd7f3e9bddfcaafef270ce"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/649e72070cbbb8600eb823833e4748f5a0815116"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a7d3f8f33c113478737bc61bb32ec5f9a987da7d"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Awaiting Analysis"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…