In the Linux kernel, the following vulnerability has been resolved:
netfilter: ipset: enforce documented limit to prevent allocating huge memory
Daniel Xu reported that the hash:net,iface type of the ipset subsystem does
not limit adding the same network with different interfaces to a set, which
can lead to huge memory usage or allocation failure.
The quick reproducer is
$ ipset create ACL.IN.ALL_PERMIT hash:net,iface hashsize 1048576 timeout 0
$ for i in $(seq 0 100); do /sbin/ipset add ACL.IN.ALL_PERMIT 0.0.0.0/0,kaf_$i timeout 0 -exist; done
The backtrace when vmalloc fails:
[Tue Oct 25 00:13:08 2022] ipset: vmalloc error: size 1073741848, exceeds total pages
<...>
[Tue Oct 25 00:13:08 2022] Call Trace:
[Tue Oct 25 00:13:08 2022] <TASK>
[Tue Oct 25 00:13:08 2022] dump_stack_lvl+0x48/0x60
[Tue Oct 25 00:13:08 2022] warn_alloc+0x155/0x180
[Tue Oct 25 00:13:08 2022] __vmalloc_node_range+0x72a/0x760
[Tue Oct 25 00:13:08 2022] ? hash_netiface4_add+0x7c0/0xb20
[Tue Oct 25 00:13:08 2022] ? __kmalloc_large_node+0x4a/0x90
[Tue Oct 25 00:13:08 2022] kvmalloc_node+0xa6/0xd0
[Tue Oct 25 00:13:08 2022] ? hash_netiface4_resize+0x99/0x710
<...>
The fix is to enforce the limit documented in the ipset(8) manpage:
> The internal restriction of the hash:net,iface set type is that the same
> network prefix cannot be stored with more than 64 different interfaces
> in a single set.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can let ipset entries consume excessive memory when the same network is added with many interface names. The likely business impact is denial of service or instability on systems using this netfilter feature. Public sources do not provide a CVSS score or active exploitation evidence.
Executive priority
Prioritize normal patching for Linux firewall or network-control hosts. Escalate if affected systems expose ipset management to tenants, customers, or untrusted automation. No source provided evidence of active exploitation or remote unauthenticated compromise.
Technical view
The ipset hash:net,iface type failed to enforce its documented cap of 64 interfaces per network prefix in one set. Repeated entries could trigger very large allocations or allocation failure in kernel memory paths. The kernel fix enforces the documented limit.
Likely exposure
Exposure is most likely on Linux systems using netfilter ipset hash:net,iface sets. Risk is higher where untrusted users, automation, or management interfaces can add ipset entries. The source bundle does not prove broad default exposure.
Exploitation context
The source includes a reproducer and kernel allocation failure trace, but no evidence of exploitation in the wild. CISA KEV status is false in the bundle. Treat this as a resource-exhaustion risk rather than a confirmed active attack campaign.
Researcher notes
The key condition is exceeding the documented 64-interface-per-prefix restriction for hash:net,iface. The fix is behavioral enforcement of that limit. The source bundle lacks CVSS, CWE mapping, detailed version range semantics, and distribution-specific fixed versions.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
Check distribution advisories for fixed package versions.
Limit who can create or modify ipset sets.
Review firewall automation that writes hash:net,iface entries.
Monitor hosts for abnormal ipset growth or memory pressure.
Validation and detection
Inventory Linux kernels and distribution package versions.
Identify systems using ipset hash:net,iface sets.
Confirm whether vendor fixes include the referenced kernel commits.
Review permissions for services or users that manage ipset.
Check logs for vmalloc or memory allocation failures tied to ipset.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49911 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 1, 2025, 14:10 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.