CVE-2022-49696: tipc: fix use-after-free Read in tipc_named_reinit
First published: Wed Feb 26 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: tipc: fix use-after-free Read in tipc_named_reinit syzbot found the following issue on: ================================================================== BUG: KASAN: use-after-free in tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 Read of size 8 at addr ffff88805299a000 by task kworker/1:9/23764 CPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted 5.18.0-rc4-syzkaller-00878-g17d49e6e8012 #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events tipc_net_finalize_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0xeb/0x495 mm/kasan/report.c:313 print_report mm/kasan/report.c:429 [inline] kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491 tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138 process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 </TASK> [...] ================================================================== In the commit d966ddcc3821 ("tipc: fix a deadlock when flushing scheduled work"), the cancel_work_sync() function just to make sure ONLY the work tipc_net_finalize_work() is executing/pending on any CPU completed before tipc namespace is destroyed through tipc_exit_net(). But this function is not guaranteed the work is the last queued. So, the destroyed instance may be accessed in the work which will try to enqueue later. In order to completely fix, we re-order the calling of cancel_work_sync() to make sure the work tipc_net_finalize_work() was last queued and it must be completed by calling cancel_work_sync().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| Linux Kernel | >=5.4.83<5.5 | |
| Linux Kernel | >=5.9.14<5.10.127 | |
| Linux Kernel | >=5.11<5.15.51 | |
| Linux Kernel | >=5.16<5.18.8 | |
| Linux Kernel | =5.19-rc1 | |
| Linux Kernel | =5.19-rc2 | |
| Linux Kernel | =5.19-rc3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-49696?
CVE-2022-49696 has been classified with high severity due to the potential for exploitation leading to a use-after-free vulnerability.
How do I fix CVE-2022-49696?
Fixing CVE-2022-49696 requires updating the Linux kernel to the latest patched version that addresses the use-after-free issue in tipc_named_reinit.
What systems are affected by CVE-2022-49696?
CVE-2022-49696 affects the Linux kernel across various distributions that utilize the vulnerable components.
What type of vulnerability is CVE-2022-49696?
CVE-2022-49696 is categorized as a use-after-free vulnerability, which can lead to memory corruption.
When was CVE-2022-49696 disclosed?
CVE-2022-49696 was disclosed on December 12, 2022.
- agent/first-publish-date
- agent/type
- agent/title
- agent/references
- agent/author
- agent/source
- agent/description
- agent/severity
- agent/guess-ai
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/event
- agent/remedy
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.4.83
- version/linux kernel/5.9.14
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/5.19-rc1
- version/linux kernel/5.19-rc2
- version/linux kernel/5.19-rc3