What is CVE-2023-53825?

CVE-2023-53825 is a unscored severity Linux kernel vulnerability, affecting Linux kernel versions from 4.6 onward and patched in 4.14.326, 4.19.295, 5.4.257 and others. CVE-2023-53825 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2023-53825?

CVE-2023-53825 has a CVSS score of pending NVD analysis out of 10, rated awaiting scoring severity.

Is there a patch available for CVE-2023-53825?

Yes, CVE-2023-53825 has been patched. Fixed versions include 4.14.326, 4.19.295, 5.4.257 and others. If you are running Linux kernel 4.6 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2023-53825 actively exploited?

CVE-2023-53825 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2023-53825

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.

Package Linux Kernel

Published 2025-12-09

Last modified 2026-04-15

Patch available

Yes

Affected versions

Linux kernel versions 4.6 and later are affected. Fixed in 4.14.326, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.54, 6.5.4, 6.6 and their respective stable series.

Affected from

≥ 4.6

Fixed in

✓ 4.14.326 4.14.x ✓ 4.19.295 4.19.x ✓ 5.4.257 5.4.x ✓ 5.10.195 5.10.x ✓ 5.15.132 5.15.x ✓ 6.1.54 6.1.x ✓ 6.5.4 6.5.x ✓ 6.6

References

The following references provide additional information about CVE-2023-53825 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Kernel patch commit
https://git.kernel.org/stable/c/1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5b
Patch
Kernel patch commit
https://git.kernel.org/stable/c/21b467735b0888a8daa048f83d3b9b50fdab71ce
Patch
Kernel patch commit
https://git.kernel.org/stable/c/2e18493c421428a936946c452461b8e979088f17
Patch

8 patch commits total View all on NVD

Frequently asked questions

What is CVE-2023-53825?

CVE-2023-53825 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 4.6 onward and has been patched in 4.14.326, 4.19.295, 5.4.257 and others. CVE-2023-53825 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
Is there a patch available for CVE-2023-53825?

Yes — CVE-2023-53825 has been patched. Fixed versions include 4.14.326, 4.19.295, 5.4.257 and others. If you are running Linux kernel 4.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2023-53825 actively exploited?

No — CVE-2023-53825 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.