CVE-2026-74492

netfilter: ipset: do not update comments from kernel-side hash adds

HIGH
8.4
CVSS Score
Published: August 15, 2026 at 12:27 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.4
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4.245.5.85.65dd9488ae41070b69d2f4acb580f77db5705f9caa469bab3386aebff33c59506f3a95e35b91118fdf66ee0410b1c3481ee75e5db9b34547b4d582465
Vendor states this is fixed in 16bfa7be2d76ca1e0aacfa363482e1bf8ab5042a (fixed)
Vendor states this is fixed in 4ae701848e4ba9e9713375fb7d82218cbd309da2 (fixed)
Vendor states this is fixed in 661ff9c0cfbe07f8eed920dde9f7781491738207 (fixed)
Vendor states this is fixed in 6f13f4d52d06986c18f12e8bffaab944dd27ceab (fixed)
Vendor states this is fixed in 77dbb248a5cc7a5270cd37bbb0b635bf059a872a (fixed)
Vendor states this is fixed in c710e9bf38e4e71a8db85d26a0f70c0674664207 (fixed)
Vendor states this is fixed in f30415929be8aeb002d557c8d3f7ab2d2188003a (fixed)
Vendor states this is fixed in f9d6cabff1fca010562dcdb0d22b296bdca3ba5a (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.4HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card