# CVE-2022-48865: linux: In the Linux kernel, the following vulnerability has been resolved:  tipc: fix kernel panic when enabling bearer  Whe...

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

- Web page: https://patchblox.com/security/cve/CVE-2022-48865
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0026
- 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:  tipc: fix kernel panic when enabling bearer  When enabling a bearer on a node, a kernel panic is observed:  [    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc] ... [    4.520030] Call Trace: [    4.520689]  <IRQ> [    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc] [    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc] [    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc] [    4.525292]  tipc_rcv+0x5da/0x730 [tipc] [    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0 [    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc] [    4.528737]  __netif_receive_skb_list_core+0x20b/0x260 [    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0 [    4.531450]  ? dev_gro_receive+0x4c2/0x680 [    4.532512]  napi_complete_done+0x6f/0x180 [    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net] ...  The node in question is receiving activate messages in another thread after changing bearer status to allow message sending/ receiving in current thread:           thread 1           |              thread 2          --------           |              --------                             | tipc_enable_bearer()        |   test_and_set_bit_lock()   |     tipc_bearer_xmit_skb()  |                             | tipc_l2_rcv_msg()                             |   tipc_rcv()                             |     __tipc_node_link_up()                             |       tipc_link_build_state_msg()                             |         tipc_link_build_proto_msg()                             |           tipc_mon_prep()                             |           {                             |             ...                             |             // null-pointer dereference                             |             u16 gen = mon->dom_gen;                             |             ...                             |           }   // Not being executed yet |   tipc_mon_create()         |   {                         |     ...                     |     // allocate             |     mon = kzalloc();        |     ...                     |   }                         |  Monitoring pointer in thread 2 is dereferenced before monitoring data is allocated in thread 1. This causes kernel panic.  This commit fixes it by allocating the monitoring data before enabling the bearer to receive messages.

## Where it's fixed

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