---
id: CVE-2025-37824
title: 'tipc: fix NULL pointer dereference in tipc_mon_reinit_self()'
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  tipc: fix NULL pointer dereference in tipc_mon_reinit_self()

  syzbot reported:

  tipc: Node number set to 1055423674
  Oops: general protection fault, probably for non-can…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 28845c28f842e9e55e75b2c116bff714bb039055 <
    a3df56010403b2cd26388096ebccf959d23c4dcc
  - >-
    Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 <
    e6613b6d41f4010c4d484cbc7bfca690d8d522a2
  - >-
    Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 <
    5fd464fd24de93d0eca377554bf0ff2548f76f30
  - >-
    Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 <
    e79e8e05aa46f90d21023f0ffe6f136ed6a20932
  - >-
    Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 <
    dd6cb0a8575b00fbd503e96903184125176f4fa3
  - >-
    Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 <
    0ceef62a328ce1288598c9242576292671f21e96
  - >-
    Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 <
    4d5e1e2d3e9d70beff7beab44fd6ce91405a405e
  - >-
    Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 <
    d63527e109e811ef11abb1c2985048fdb528b4cb
  - Linux 295c9b554f6dfcd2d368fae6e6fa22ee5b79c123
  - Linux >= 5.4.15 < 5.4.293
  - Linux >= 4.19.99 < 4.20
  - Linux 5.5
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T20:41:23.531716Z'
published: '2025-05-08'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T20:41:55.257Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2025-37824'
references:
  - url: 'https://git.kernel.org/stable/c/a3df56010403b2cd26388096ebccf959d23c4dcc'
  - url: 'https://git.kernel.org/stable/c/e6613b6d41f4010c4d484cbc7bfca690d8d522a2'
  - url: 'https://git.kernel.org/stable/c/5fd464fd24de93d0eca377554bf0ff2548f76f30'
  - url: 'https://git.kernel.org/stable/c/e79e8e05aa46f90d21023f0ffe6f136ed6a20932'
  - url: 'https://git.kernel.org/stable/c/dd6cb0a8575b00fbd503e96903184125176f4fa3'
  - url: 'https://git.kernel.org/stable/c/0ceef62a328ce1288598c9242576292671f21e96'
  - url: 'https://git.kernel.org/stable/c/4d5e1e2d3e9d70beff7beab44fd6ce91405a405e'
  - url: 'https://git.kernel.org/stable/c/d63527e109e811ef11abb1c2985048fdb528b4cb'
tags:
  - cve.org
epss: 0.00209
epssPercentile: 0.11144
ingestedAt: '2026-11-05T22:38:31.873Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

tipc: fix NULL pointer dereference in tipc_mon_reinit_self()

syzbot reported:

tipc: Node number set to 1055423674
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 3 UID: 0 PID: 6017 Comm: kworker/3:5 Not tainted 6.15.0-rc1-syzkaller-00246-g900241a5cc15 #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: events tipc_net_finalize_work
RIP: 0010:tipc_mon_reinit_self+0x11c/0x210 net/tipc/monitor.c:719
...
RSP: 0018:ffffc9000356fb68 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000003ee87cba
RDX: 0000000000000000 RSI: ffffffff8dbc56a7 RDI: ffff88804c2cc010
RBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000007
R13: fffffbfff2111097 R14: ffff88804ead8000 R15: ffff88804ead9010
FS:  0000000000000000(0000) GS:ffff888097ab9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000f720eb00 CR3: 000000000e182000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 tipc_net_finalize+0x10b/0x180 net/tipc/net.c:140
 process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3238
 process_scheduled_works kernel/workqueue.c:3319 [inline]
 worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400
 kthread+0x3c2/0x780 kernel/kthread.c:464
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:153
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
...
RIP: 0010:tipc_mon_reinit_self+0x11c/0x210 net/tipc/monitor.c:719
...
RSP: 0018:ffffc9000356fb68 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000003ee87cba
RDX: 0000000000000000 RSI: ffffffff8dbc56a7 RDI: ffff88804c2cc010
RBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000007
R13: fffffbfff2111097 R14: ffff88804ead8000 R15: ffff88804ead9010
FS:  0000000000000000(0000) GS:ffff888097ab9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000f720eb00 CR3: 000000000e182000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

There is a racing condition between workqueue created when enabling
bearer and another thread created when disabling bearer right after
that as follow:

enabling_bearer                          | disabling_bearer
---------------                          | ----------------
tipc_disc_timeout()                      |
{                                        | bearer_disable()
 ...                                     | {
 schedule_work(&tn->work);               |  tipc_mon_delete()
 ...                                     |  {
}                                        |   ...
                                         |   write_lock_bh(&mon->lock);
                                         |   mon->self = NULL;
                                         |   write_unlock_bh(&mon->lock);
                                         |   ...
                                         |  }
tipc_net_finalize_work()                 | }
{                                        |
 ...                                     |
 tipc_net_finalize()                     |
 {                                       |
  ...                                    |
  tipc_mon_reinit_self()                 |
  {                                      |
   ...                                   |
   write_lock_bh(&mon->lock);            |
   mon->self->addr = tipc_own_addr(net); |
   write_unlock_bh(&mon->lock);          |
   ...             
---truncated---

## Affected

- `Linux >= 28845c28f842e9e55e75b2c116bff714bb039055 < a3df56010403b2cd26388096ebccf959d23c4dcc`
- `Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 < e6613b6d41f4010c4d484cbc7bfca690d8d522a2`
- `Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 < 5fd464fd24de93d0eca377554bf0ff2548f76f30`
- `Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 < e79e8e05aa46f90d21023f0ffe6f136ed6a20932`
- `Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 < dd6cb0a8575b00fbd503e96903184125176f4fa3`
- `Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 < 0ceef62a328ce1288598c9242576292671f21e96`
- `Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 < 4d5e1e2d3e9d70beff7beab44fd6ce91405a405e`
- `Linux >= 46cb01eeeb86fca6afe24dda1167b0cb95424e29 < d63527e109e811ef11abb1c2985048fdb528b4cb`
- `Linux 295c9b554f6dfcd2d368fae6e6fa22ee5b79c123`
- `Linux >= 5.4.15 < 5.4.293`
- `Linux >= 4.19.99 < 4.20`
- `Linux 5.5`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.