GHSA-62G8-53XP-7372

Vulnerability from github – Published: 2025-09-15 15:31 – Updated: 2025-12-02 03:31
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

vxlan: Fix memory leaks in error path

The memory allocated by vxlan_vnigroup_init() is not freed in the error path, leading to memory leaks [1]. Fix by calling vxlan_vnigroup_uninit() in the error path.

The leaks can be reproduced by annotating gro_cells_init() with ALLOW_ERROR_INJECTION() and then running:

# echo "100" > /sys/kernel/debug/fail_function/probability # echo "1" > /sys/kernel/debug/fail_function/times # echo "gro_cells_init" > /sys/kernel/debug/fail_function/inject # printf %#x -12 > /sys/kernel/debug/fail_function/gro_cells_init/retval # ip link add name vxlan0 type vxlan dstport 4789 external vnifilter RTNETLINK answers: Cannot allocate memory

[1] unreferenced object 0xffff88810db84a00 (size 512): comm "ip", pid 330, jiffies 4295010045 (age 66.016s) hex dump (first 32 bytes): f8 d5 76 0e 81 88 ff ff 01 00 00 00 00 00 00 02 ..v............. 03 00 04 00 48 00 00 00 00 00 00 01 04 00 01 00 ....H........... backtrace: [] kmalloc_trace+0x2a/0x60 [] vxlan_vnigroup_init+0x4c/0x160 [] vxlan_init+0x1ae/0x280 [] register_netdevice+0x57a/0x16d0 [] __vxlan_dev_create+0x7c7/0xa50 [] vxlan_newlink+0xd6/0x130 [] __rtnl_newlink+0x112b/0x18a0 [] rtnl_newlink+0x6c/0xa0 [] rtnetlink_rcv_msg+0x43f/0xd40 [] netlink_rcv_skb+0x170/0x440 [] netlink_unicast+0x53f/0x810 [] netlink_sendmsg+0x958/0xe70 [] ____sys_sendmsg+0x78f/0xa90 [] ___sys_sendmsg+0x13a/0x1e0 [] __sys_sendmsg+0x11c/0x1f0 [] do_syscall_64+0x38/0x80 unreferenced object 0xffff88810e76d5f8 (size 192): comm "ip", pid 330, jiffies 4295010045 (age 66.016s) hex dump (first 32 bytes): 04 00 00 00 00 00 00 00 db e1 4f e7 00 00 00 00 ..........O..... 08 d6 76 0e 81 88 ff ff 08 d6 76 0e 81 88 ff ff ..v.......v..... backtrace: [] __kmalloc_node+0x4e/0x90 [] kvmalloc_node+0xa6/0x1f0 [] bucket_table_alloc.isra.0+0x83/0x460 [] rhashtable_init+0x43b/0x7c0 [] vxlan_vnigroup_init+0x6c/0x160 [] vxlan_init+0x1ae/0x280 [] register_netdevice+0x57a/0x16d0 [] __vxlan_dev_create+0x7c7/0xa50 [] vxlan_newlink+0xd6/0x130 [] __rtnl_newlink+0x112b/0x18a0 [] rtnl_newlink+0x6c/0xa0 [] rtnetlink_rcv_msg+0x43f/0xd40 [] netlink_rcv_skb+0x170/0x440 [] netlink_unicast+0x53f/0x810 [] netlink_sendmsg+0x958/0xe70 [] ____sys_sendmsg+0x78f/0xa90

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-53190"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-401"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-09-15T14:15:41Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Fix memory leaks in error path\n\nThe memory allocated by vxlan_vnigroup_init() is not freed in the error\npath, leading to memory leaks [1]. Fix by calling\nvxlan_vnigroup_uninit() in the error path.\n\nThe leaks can be reproduced by annotating gro_cells_init() with\nALLOW_ERROR_INJECTION() and then running:\n\n # echo \"100\" \u003e /sys/kernel/debug/fail_function/probability\n # echo \"1\" \u003e /sys/kernel/debug/fail_function/times\n # echo \"gro_cells_init\" \u003e /sys/kernel/debug/fail_function/inject\n # printf %#x -12 \u003e /sys/kernel/debug/fail_function/gro_cells_init/retval\n # ip link add name vxlan0 type vxlan dstport 4789 external vnifilter\n RTNETLINK answers: Cannot allocate memory\n\n[1]\nunreferenced object 0xffff88810db84a00 (size 512):\n  comm \"ip\", pid 330, jiffies 4295010045 (age 66.016s)\n  hex dump (first 32 bytes):\n    f8 d5 76 0e 81 88 ff ff 01 00 00 00 00 00 00 02  ..v.............\n    03 00 04 00 48 00 00 00 00 00 00 01 04 00 01 00  ....H...........\n  backtrace:\n    [\u003cffffffff81a3097a\u003e] kmalloc_trace+0x2a/0x60\n    [\u003cffffffff82f049fc\u003e] vxlan_vnigroup_init+0x4c/0x160\n    [\u003cffffffff82ecd69e\u003e] vxlan_init+0x1ae/0x280\n    [\u003cffffffff836858ca\u003e] register_netdevice+0x57a/0x16d0\n    [\u003cffffffff82ef67b7\u003e] __vxlan_dev_create+0x7c7/0xa50\n    [\u003cffffffff82ef6ce6\u003e] vxlan_newlink+0xd6/0x130\n    [\u003cffffffff836d02ab\u003e] __rtnl_newlink+0x112b/0x18a0\n    [\u003cffffffff836d0a8c\u003e] rtnl_newlink+0x6c/0xa0\n    [\u003cffffffff836c0ddf\u003e] rtnetlink_rcv_msg+0x43f/0xd40\n    [\u003cffffffff83908ce0\u003e] netlink_rcv_skb+0x170/0x440\n    [\u003cffffffff839066af\u003e] netlink_unicast+0x53f/0x810\n    [\u003cffffffff839072d8\u003e] netlink_sendmsg+0x958/0xe70\n    [\u003cffffffff835c319f\u003e] ____sys_sendmsg+0x78f/0xa90\n    [\u003cffffffff835cd6da\u003e] ___sys_sendmsg+0x13a/0x1e0\n    [\u003cffffffff835cd94c\u003e] __sys_sendmsg+0x11c/0x1f0\n    [\u003cffffffff8424da78\u003e] do_syscall_64+0x38/0x80\nunreferenced object 0xffff88810e76d5f8 (size 192):\n  comm \"ip\", pid 330, jiffies 4295010045 (age 66.016s)\n  hex dump (first 32 bytes):\n    04 00 00 00 00 00 00 00 db e1 4f e7 00 00 00 00  ..........O.....\n    08 d6 76 0e 81 88 ff ff 08 d6 76 0e 81 88 ff ff  ..v.......v.....\n  backtrace:\n    [\u003cffffffff81a3162e\u003e] __kmalloc_node+0x4e/0x90\n    [\u003cffffffff81a0e166\u003e] kvmalloc_node+0xa6/0x1f0\n    [\u003cffffffff8276e1a3\u003e] bucket_table_alloc.isra.0+0x83/0x460\n    [\u003cffffffff8276f18b\u003e] rhashtable_init+0x43b/0x7c0\n    [\u003cffffffff82f04a1c\u003e] vxlan_vnigroup_init+0x6c/0x160\n    [\u003cffffffff82ecd69e\u003e] vxlan_init+0x1ae/0x280\n    [\u003cffffffff836858ca\u003e] register_netdevice+0x57a/0x16d0\n    [\u003cffffffff82ef67b7\u003e] __vxlan_dev_create+0x7c7/0xa50\n    [\u003cffffffff82ef6ce6\u003e] vxlan_newlink+0xd6/0x130\n    [\u003cffffffff836d02ab\u003e] __rtnl_newlink+0x112b/0x18a0\n    [\u003cffffffff836d0a8c\u003e] rtnl_newlink+0x6c/0xa0\n    [\u003cffffffff836c0ddf\u003e] rtnetlink_rcv_msg+0x43f/0xd40\n    [\u003cffffffff83908ce0\u003e] netlink_rcv_skb+0x170/0x440\n    [\u003cffffffff839066af\u003e] netlink_unicast+0x53f/0x810\n    [\u003cffffffff839072d8\u003e] netlink_sendmsg+0x958/0xe70\n    [\u003cffffffff835c319f\u003e] ____sys_sendmsg+0x78f/0xa90",
  "id": "GHSA-62g8-53xp-7372",
  "modified": "2025-12-02T03:31:35Z",
  "published": "2025-09-15T15:31:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53190"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/06bf62944144a92d83dd14fd1378d2a288259561"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5896f55810680391a32652ca2b91245a05c11e22"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/75c1ab900f7cf0485f0be1607c79c55f51faaa90"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.