CVE-2026-74492

CVE CVE-2026-74492EUVD EUVD-2026-59685Published 2026-08-15T12:27:21.000ZLast changed 2026-08-19T16:37:48.000ZCVSS 8.4

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: do not update comments from kernel-side hash adds mtype_resize() copies comment pointers with memcpy(), not the comment objects themselves. During the window after an entry has been copied but before the table swap and backlog replay, the old table is still published for packet-side updates while the replacement-table entry already holds the same ip_set_comment_rcu pointer. If xt_SET --add-set ... --exist hits that old entry in this window, mtype_add() calls ip_set_init_comment() even though packet-side adds carry no comment payload. That call frees the shared comment through the old entry, so the replacement-table entry now holds a stale pointer. When the queued add is replayed on the new table, mtype_add() calls ip_set_init_comment() again and strlen() dereferences the stale pointer. Fix this in mtype_add() by skipping ip_set_init_comment() when ext->target marks a packet-side add. Userspace adds still update comments, while packet-side adds can no longer free comment storage shared with a resize copy.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux a469bab3386aebff33c59506f3a95e35b91118fd; patch: 6.6.151; f66ee0410b1c3481ee75e5db9b34547b4d582465 <4ae701848e4ba9e9713375fb7d82218cbd309da2; patch: 7.1.8; f66ee0410b1c3481ee75e5db9b34547b4d582465 <16bfa7be2d76ca1e0aacfa363482e1bf8ab5042a; patch: 6.1.183; f66ee0410b1c3481ee75e5db9b34547b4d582465 <77dbb248a5cc7a5270cd37bbb0b635bf059a872a; 5.5.8 <5.6; 5.6; patch: 7.2; f66ee0410b1c3481ee75e5db9b34547b4d582465 <c710e9bf38e4e71a8db85d26a0f70c0674664207; f66ee0410b1c3481ee75e5db9b34547b4d582465 <f30415929be8aeb002d557c8d3f7ab2d2188003a; patch: 5.10.265; f66ee0410b1c3481ee75e5db9b34547b4d582465 <661ff9c0cfbe07f8eed920dde9f7781491738207; f66ee0410b1c3481ee75e5db9b34547b4d582465 <6f13f4d52d06986c18f12e8bffaab944dd27ceab; patch: 6.12.103; patch: 6.18.44; f66ee0410b1c3481ee75e5db9b34547b4d582465 <f9d6cabff1fca010562dcdb0d22b296bdca3ba5a; 5dd9488ae41070b69d2f4acb580f77db5705f9ca; patch: 5.15.216; 5.4.24 <5.5; patch: 0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.