CVE-2023-53825kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().
- —Not scoredno CVSS score yet
- 0.27%Exploitation in 30 daysEPSS · top 80% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.27% · top 80% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 21b467735b0888a8daa048f83d3b9b50fdab71ce
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < d4b8f380b0a041ee6a84fdac14127d8fe1dcad7b
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5b
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 2e18493c421428a936946c452461b8e979088f17
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 55d2e7c1ab8eaa7b62575b8a4194132795d1f9fc
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < e5b28ce127a690f3acc49a6a342e6c9442c9edd6
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 992b2ac783aad360b98ed9d4686e86176a20f6f1
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < a22730b1b4bf437c6bbfdeff5feddf54be4aeada
- affected 4.6
- unaffected < 4.6
- unaffected 4.14.326 – ≤ 4.14.*
- unaffected 4.19.295 – ≤ 4.19.*
- unaffected 5.4.257 – ≤ 5.4.*
- unaffected 5.10.195 – ≤ 5.10.*
- unaffected 5.15.132 – ≤ 5.15.*
- unaffected 6.1.54 – ≤ 6.1.*
- unaffected 6.5.4 – ≤ 6.5.*
- unaffected 6.6 – ≤ *
References
References8
- https://git.kernel.org/stable/c/21b467735b0888a8daa048f83d3b9b50fdab71ce (opens in a new tab)
- https://git.kernel.org/stable/c/d4b8f380b0a041ee6a84fdac14127d8fe1dcad7b (opens in a new tab)
- https://git.kernel.org/stable/c/1ce8362b4ac6b8e65fd04a22ea37ec776ee1ec5b (opens in a new tab)
- https://git.kernel.org/stable/c/2e18493c421428a936946c452461b8e979088f17 (opens in a new tab)
- https://git.kernel.org/stable/c/55d2e7c1ab8eaa7b62575b8a4194132795d1f9fc (opens in a new tab)
- https://git.kernel.org/stable/c/e5b28ce127a690f3acc49a6a342e6c9442c9edd6 (opens in a new tab)
- https://git.kernel.org/stable/c/992b2ac783aad360b98ed9d4686e86176a20f6f1 (opens in a new tab)
- https://git.kernel.org/stable/c/a22730b1b4bf437c6bbfdeff5feddf54be4aeada (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-60171 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53825)Record last updated .