CVE-2024-40983: tipc: force a dst refcount before doing decryption

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.9% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-07-12 · updated 2026-08-04

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: force a dst refcount before doing decryption As it says in commit 3bc07321ccc2 ("xfrm: Force a dst refcount before entering the xfrm type handlers"): "Crypto requests might return asynchronous. In this case we leave the rcu protected region, so force a refcount on the skb's destination entry before we enter the xfrm type input/output handlers." On TIPC decryption path it has the same problem, and skb_dst_force() should be called before doing decryption to avoid a possible crash. Shuang reported this issue when this warning is triggered: [] WARNING: include/net/dst.h:337 tipc_sk_rcv+0x1055/0x1ea0 [tipc] [] Kdump: loaded Tainted: G W --------- - - 4.18.0-496.el8.x86_64+debug [] Workqueue: crypto cryptd_queue_worker [] RIP: 0010:tipc_sk_rcv+0x1055/0x1ea0 [tipc] [] Call Trace: [] tipc_sk_mcast_rcv+0x548/0xea0 [tipc] [] tipc_rcv+0xcf5/0x1060 [tipc] [] tipc_aead_decrypt_done+0x215/0x2e0 [tipc] [] cryptd_aead_crypt+0xdb/0x190 [] cryptd_queue_worker+0xed/0x190 [] process_one_work+0x93d/0x17e0

Affected products

Linux kernel: from 5.5 before 5.10.221; from 5.11 before 5.15.162; from 5.16 before 6.1.96; from 6.2 before 6.6.36; from 6.7 before 6.9.7; 6.10-rc1, 6.10-rc2, 6.10-rc3, 6.10-rc4 — fixed in 5.10.221, 5.15.162, 6.1.96, 6.6.36, 6.9.7

How to fix

Upgrade to a fixed version: Linux kernel 5.10.221, 5.15.162, 6.1.96, 6.6.36. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-40983 or the next vulnerability affects your stack