CVE-2022-49153

wireguard: socket: free skb in send6 when ipv6 is disabled

MEDIUM

5.5

CVSS Score

Published: February 26, 2025 at 01:55 AM UTC

Updated: June 17, 2026 at 05:17 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: wireguard: socket: free skb in send6 when ipv6 is disabled I got a memory leak report: unreferenced object 0xffff8881191fc040 (size 232): comm "kworker/u17:0", pid 23193, jiffies 4295238848 (age 3464.870s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff814c3ef4>] slab_post_alloc_hook+0x84/0x3b0 [<ffffffff814c8977>] kmem_cache_alloc_node+0x167/0x340 [<ffffffff832974fb>] __alloc_skb+0x1db/0x200 [<ffffffff82612b5d>] wg_socket_send_buffer_to_peer+0x3d/0xc0 [<ffffffff8260e94a>] wg_packet_send_handshake_initiation+0xfa/0x110 [<ffffffff8260ec81>] wg_packet_handshake_send_worker+0x21/0x30 [<ffffffff8119c558>] process_one_work+0x2e8/0x770 [<ffffffff8119ca2a>] worker_thread+0x4a/0x4b0 [<ffffffff811a88e0>] kthread+0x120/0x160 [<ffffffff8100242f>] ret_from_fork+0x1f/0x30 In function wg_socket_send_buffer_as_reply_to_skb() or wg_socket_send_ buffer_to_peer(), the semantics of send6() is required to free skb. But when CONFIG_IPV6 is disable, kfree_skb() is missing. This patch adds it to fix this bug.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.11 ≤ v < 5.15.335.16 ≤ v < 5.16.195.17 ≤ v < 5.17.25.6 ≤ v < 5.10.1105.6 ≤ v < 5.15.335.6 ≤ v < 5.16.195.6 ≤ v < 5.17.25.6 ≤ v < 5.185.6e7096c131e5161fa3b8e52a650d7719d2857adfd

Vendor states this is fixed in 096f9d35cac0a0c95ffafc00db84786b665a4837 (fixed)

Vendor states this is fixed in 0b19bcb753dbfb74710d12bb2761ec5ed706c726 (fixed)

Vendor states this is fixed in 402991a9771587acc2947cf6c4d689c5397f2258 (fixed)

Vendor states this is fixed in bbbf962d9460194993ee1943a793a0a0af4a7fbf (fixed)

Vendor states this is fixed in ebcc492f4ba14bae54b898f1016a37b4282558d1 (fixed)

Vendor states this is fixed in 5.10.110 (unaffected)

Vendor states this is fixed in 5.15.33 (unaffected)

Vendor states this is fixed in 5.16.19 (unaffected)

Vendor states this is fixed in 5.17.2 (unaffected)

Vendor states this is fixed in 5.18 (unaffected)

Vendor states this is fixed in 5.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references