Bug 2517027 (CVE-2026-74492) - CVE-2026-74492 kernel: netfilter: ipset: do not update comments from kernel-side hash adds
Summary: CVE-2026-74492 kernel: netfilter: ipset: do not update comments from kernel-s...
Keywords:
Status: NEW
Alias: CVE-2026-74492
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-15 12:45 UTC by OSIDB Bzimport
Modified: 2026-08-20 18:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-15 12:45:20 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-08-20 18:28:05 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081539-CVE-2026-74492-a089@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.