ghsa-wx74-4w24-9hwf
Vulnerability from github
Published
2025-05-01 15:31
Modified
2025-05-01 15:31
Details

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.

Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2022-49911"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-05-01T15:16:16Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ipset: enforce documented limit to prevent allocating huge memory\n\nDaniel Xu reported that the hash:net,iface type of the ipset subsystem does\nnot limit adding the same network with different interfaces to a set, which\ncan lead to huge memory usage or allocation failure.\n\nThe quick reproducer is\n\n$ ipset create ACL.IN.ALL_PERMIT hash:net,iface hashsize 1048576 timeout 0\n$ 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\n\nThe backtrace when vmalloc fails:\n\n        [Tue Oct 25 00:13:08 2022] ipset: vmalloc error: size 1073741848, exceeds total pages\n        \u003c...\u003e\n        [Tue Oct 25 00:13:08 2022] Call Trace:\n        [Tue Oct 25 00:13:08 2022]  \u003cTASK\u003e\n        [Tue Oct 25 00:13:08 2022]  dump_stack_lvl+0x48/0x60\n        [Tue Oct 25 00:13:08 2022]  warn_alloc+0x155/0x180\n        [Tue Oct 25 00:13:08 2022]  __vmalloc_node_range+0x72a/0x760\n        [Tue Oct 25 00:13:08 2022]  ? hash_netiface4_add+0x7c0/0xb20\n        [Tue Oct 25 00:13:08 2022]  ? __kmalloc_large_node+0x4a/0x90\n        [Tue Oct 25 00:13:08 2022]  kvmalloc_node+0xa6/0xd0\n        [Tue Oct 25 00:13:08 2022]  ? hash_netiface4_resize+0x99/0x710\n        \u003c...\u003e\n\nThe fix is to enforce the limit documented in the ipset(8) manpage:\n\n\u003e  The internal restriction of the hash:net,iface set type is that the same\n\u003e  network prefix cannot be stored with more than 64 different interfaces\n\u003e  in a single set.",
  "id": "GHSA-wx74-4w24-9hwf",
  "modified": "2025-05-01T15:31:52Z",
  "published": "2025-05-01T15:31:52Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49911"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/42d20d5e24575c9afa2d66d9a51e7386db9514f5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/510841da1fcc16f702440ab58ef0b4d82a9056b7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a37ef32fe5956fe9248df68f6a61997845ba047e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading...

Loading...

Loading...
  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.