CVE-2023-53825

kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().

N/A
Published: December 9, 2025 at 01:29 AM UTC
Updated: June 17, 2026 at 06:46 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
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg(). syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 ("kcm: Fix memory leak in error path of kcm_sendmsg()") suppressed it by updating kcm_tx_msg(head)->last_skb if partial data is copied so that the following sendmsg() will resume from the skb. However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue. When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames(). Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely. Note this does not change SOCK_SEQPACKET behaviour.

Affected

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

4.6 ≤ v < 4.14.3264.6 ≤ v < 4.19.2954.6 ≤ v < 5.10.1954.6 ≤ v < 5.15.1324.6 ≤ v < 5.4.2574.6 ≤ v < 6.1.544.6 ≤ v < 6.5.44.6 ≤ v < 6.64.6ab7ac4eb9832e32a09f4e8042705484d2fb0aad3
Vendor states this is fixed in 1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5b (fixed)
Vendor states this is fixed in 21b467735b0888a8daa048f83d3b9b50fdab71ce (fixed)
Vendor states this is fixed in 2e18493c421428a936946c452461b8e979088f17 (fixed)
Vendor states this is fixed in 55d2e7c1ab8eaa7b62575b8a4194132795d1f9fc (fixed)
Vendor states this is fixed in 992b2ac783aad360b98ed9d4686e86176a20f6f1 (fixed)
Vendor states this is fixed in a22730b1b4bf437c6bbfdeff5feddf54be4aeada (fixed)
Vendor states this is fixed in d4b8f380b0a041ee6a84fdac14127d8fe1dcad7b (fixed)
Vendor states this is fixed in e5b28ce127a690f3acc49a6a342e6c9442c9edd6 (fixed)
Vendor states this is fixed in 4.14.326 (unaffected)
Vendor states this is fixed in 4.19.295 (unaffected)
Vendor states this is fixed in 4.6 (unaffected)
Vendor states this is fixed in 5.10.195 (unaffected)
Vendor states this is fixed in 5.15.132 (unaffected)
Vendor states this is fixed in 5.4.257 (unaffected)
Vendor states this is fixed in 6.1.54 (unaffected)
Vendor states this is fixed in 6.5.4 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card