cveboard RSS feed

CVE-2026-43244

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

kcm: fix zero-frag skb in frag_list on partial sendmsg error

In the Linux kernel, the following vulnerability has been resolved: kcm: fix zero-frag skb in frag_list on partial sendmsg error Syzkaller reported a warning in kcm_write_msgs() when processing a message with a zero-fragment skb in the frag_list. When kcm_sendmsg() fills MAX_SKB_FRAGS fragments in the current skb, it allocates a new skb (tskb) and links it into the frag_list before copying data. If the copy subsequently fails (e.g. -EFAULT from user memory), tskb remains in the frag_list with zero fragments: head skb (msg being assembled, NOT yet in sk_write_queue) +-----------+ | frags[17] | (MAX_SKB_FRAGS, all filled with data) | frag_list-+--> tskb +-----------+ +----------+ | frags[0] | (empty! copy failed before filling) +----------+ For SOCK_SEQPACKET with partial data already copied, the error path saves this message via partial_message for later completion. For SOCK_SEQPACKET, sock_write_iter() automatically sets MSG_EOR, so a subsequent zero-length write(fd, NULL, 0) completes the message and queues it to sk_write_queue. kcm_write_msgs() then walks the frag_list and hits: WARN_ON(!skb_shinfo(skb)->nr_frags) TCP has a similar pattern where skbs are enqueued before data copy and cleaned up on failure via tcp_remove_empty_skb(). KCM was missing the equivalent cleanup. Fix this by tracking the predecessor skb (frag_prev) when allocating a new frag_list entry. On error, if the tail skb has zero frags, use frag_prev to unlink and free it in O(1) without walking the singly-linked frag_list. frag_prev is safe to dereference because the entire message chain is only held locally (or in kcm->seq_skb) and is not added to sk_write_queue until MSG_EOR, so the send path cannot free it underneath us. Also change the WARN_ON to WARN_ON_ONCE to avoid flooding the log if the condition is somehow hit repeatedly. There are currently no KCM selftests in the kernel tree; a simple reproducer is available at [1]. [1] https://gist.github.com/mrpre/a94d431c757e8d6f168f4dd1a3749daa

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
ab7ac4eb9832e32a09f4e8042705484d2fb0aad3affectedgit6f129a251c2795ba55dd5cc1fdf7e0af3098d848UnavailableNone listed
ab7ac4eb9832e32a09f4e8042705484d2fb0aad3affectedgit9ea3671d70ee07480d80bebe86696397c4e99fb7UnavailableNone listed
ab7ac4eb9832e32a09f4e8042705484d2fb0aad3affectedgitb1e3edf688a88c1a3ac41657055d9c136a08cd25UnavailableNone listed
ab7ac4eb9832e32a09f4e8042705484d2fb0aad3affectedgit7af58f76e4b404a74c836881a845e6652db8a09fUnavailableNone listed
ab7ac4eb9832e32a09f4e8042705484d2fb0aad3affectedgitca220141fa8ebae09765a242076b2b77338106b0UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.6affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.6UnavailableNone listed
6.6.160unaffectedsemverUnavailable6.6.*None listed
6.12.75unaffectedsemverUnavailable6.12.*None listed
6.18.16unaffectedsemverUnavailable6.18.*None listed
6.19.6unaffectedsemverUnavailable6.19.*None listed
7.0unaffectedoriginal_commit_for_fixUnavailable*None listed