Strix
26.1K

CVE-2023-53825

UnknownEPSS 0.22%

Last modified

CVE-2023-53825 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.22%

12.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < 21b467735b0888a8daa048f83d3b9b50fdab71ce; >= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < d4b8f380b0a041ee6a84fdac14127d8fe1dcad7b; >= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < 1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5b; >= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < 2e18493c421428a936946c452461b8e979088f17; >= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < 55d2e7c1ab8eaa7b62575b8a4194132795d1f9fc; >= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < e5b28ce127a690f3acc49a6a342e6c9442c9edd6; >= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < 992b2ac783aad360b98ed9d4686e86176a20f6f1; >= ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, < a22730b1b4bf437c6bbfdeff5feddf54be4aeada
LinuxLinux4.6

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is 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.
How severe is CVE-2023-53825?
Severity scoring for CVE-2023-53825 is pending analysis. The EPSS model estimates a 0.22% probability of exploitation in the next 30 days.
How do I fix CVE-2023-53825?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2023

View all 2023CVEs →

Are you affected by CVE-2023-53825?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST