ghsa-vmcx-j4f5-gfcv
Vulnerability from github
Published
2024-04-17 12:32
Modified
2024-04-17 12:32
Details

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

wifi: wfx: fix memory leak when starting AP

Kmemleak reported this error:

unreferenced object 0xd73d1180 (size 184):
  comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.245s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 1e 00 01 00 00 00 00 00  ................
  backtrace:
    [<5ca11420>] kmem_cache_alloc+0x20c/0x5ac
    [<127bdd74>] __alloc_skb+0x144/0x170
    [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180
    [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211]
    [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211]
    [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx]
    [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211]
    [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211]
    [<47bd8b68>] genl_rcv_msg+0x198/0x378
    [<453ef796>] netlink_rcv_skb+0xd0/0x130
    [<6b7c977a>] genl_rcv+0x34/0x44
    [<66b2d04d>] netlink_unicast+0x1b4/0x258
    [<f965b9b6>] netlink_sendmsg+0x1e8/0x428
    [<aadb8231>] ____sys_sendmsg+0x1e0/0x274
    [<d2b5212d>] ___sys_sendmsg+0x80/0xb4
    [<69954f45>] __sys_sendmsg+0x64/0xa8
unreferenced object 0xce087000 (size 1024):
  comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.246s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00  ...@............
  backtrace:
    [<9a993714>] __kmalloc_track_caller+0x230/0x600
    [<f83ea192>] kmalloc_reserve.constprop.0+0x30/0x74
    [<a2c61343>] __alloc_skb+0xa0/0x170
    [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180
    [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211]
    [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211]
    [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx]
    [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211]
    [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211]
    [<47bd8b68>] genl_rcv_msg+0x198/0x378
    [<453ef796>] netlink_rcv_skb+0xd0/0x130
    [<6b7c977a>] genl_rcv+0x34/0x44
    [<66b2d04d>] netlink_unicast+0x1b4/0x258
    [<f965b9b6>] netlink_sendmsg+0x1e8/0x428
    [<aadb8231>] ____sys_sendmsg+0x1e0/0x274
    [<d2b5212d>] ___sys_sendmsg+0x80/0xb4

However, since the kernel is build optimized, it seems the stack is not accurate. It appears the issue is related to wfx_set_mfp_ap(). The issue is obvious in this function: memory allocated by ieee80211_beacon_get() is never released. Fixing this leak makes kmemleak happy.

Show details on source website

To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2024-26896"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-125"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-04-17T11:15:10Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wfx: fix memory leak when starting AP\n\nKmemleak reported this error:\n\n    unreferenced object 0xd73d1180 (size 184):\n      comm \"wpa_supplicant\", pid 1559, jiffies 13006305 (age 964.245s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n        00 00 00 00 00 00 00 00 1e 00 01 00 00 00 00 00  ................\n      backtrace:\n        [\u003c5ca11420\u003e] kmem_cache_alloc+0x20c/0x5ac\n        [\u003c127bdd74\u003e] __alloc_skb+0x144/0x170\n        [\u003cfb8a5e38\u003e] __netdev_alloc_skb+0x50/0x180\n        [\u003c0f9fa1d5\u003e] __ieee80211_beacon_get+0x290/0x4d4 [mac80211]\n        [\u003c7accd02d\u003e] ieee80211_beacon_get_tim+0x54/0x18c [mac80211]\n        [\u003c41e25cc3\u003e] wfx_start_ap+0xc8/0x234 [wfx]\n        [\u003c93a70356\u003e] ieee80211_start_ap+0x404/0x6b4 [mac80211]\n        [\u003ca4a661cd\u003e] nl80211_start_ap+0x76c/0x9e0 [cfg80211]\n        [\u003c47bd8b68\u003e] genl_rcv_msg+0x198/0x378\n        [\u003c453ef796\u003e] netlink_rcv_skb+0xd0/0x130\n        [\u003c6b7c977a\u003e] genl_rcv+0x34/0x44\n        [\u003c66b2d04d\u003e] netlink_unicast+0x1b4/0x258\n        [\u003cf965b9b6\u003e] netlink_sendmsg+0x1e8/0x428\n        [\u003caadb8231\u003e] ____sys_sendmsg+0x1e0/0x274\n        [\u003cd2b5212d\u003e] ___sys_sendmsg+0x80/0xb4\n        [\u003c69954f45\u003e] __sys_sendmsg+0x64/0xa8\n    unreferenced object 0xce087000 (size 1024):\n      comm \"wpa_supplicant\", pid 1559, jiffies 13006305 (age 964.246s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n        10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00  ...@............\n      backtrace:\n        [\u003c9a993714\u003e] __kmalloc_track_caller+0x230/0x600\n        [\u003cf83ea192\u003e] kmalloc_reserve.constprop.0+0x30/0x74\n        [\u003ca2c61343\u003e] __alloc_skb+0xa0/0x170\n        [\u003cfb8a5e38\u003e] __netdev_alloc_skb+0x50/0x180\n        [\u003c0f9fa1d5\u003e] __ieee80211_beacon_get+0x290/0x4d4 [mac80211]\n        [\u003c7accd02d\u003e] ieee80211_beacon_get_tim+0x54/0x18c [mac80211]\n        [\u003c41e25cc3\u003e] wfx_start_ap+0xc8/0x234 [wfx]\n        [\u003c93a70356\u003e] ieee80211_start_ap+0x404/0x6b4 [mac80211]\n        [\u003ca4a661cd\u003e] nl80211_start_ap+0x76c/0x9e0 [cfg80211]\n        [\u003c47bd8b68\u003e] genl_rcv_msg+0x198/0x378\n        [\u003c453ef796\u003e] netlink_rcv_skb+0xd0/0x130\n        [\u003c6b7c977a\u003e] genl_rcv+0x34/0x44\n        [\u003c66b2d04d\u003e] netlink_unicast+0x1b4/0x258\n        [\u003cf965b9b6\u003e] netlink_sendmsg+0x1e8/0x428\n        [\u003caadb8231\u003e] ____sys_sendmsg+0x1e0/0x274\n        [\u003cd2b5212d\u003e] ___sys_sendmsg+0x80/0xb4\n\nHowever, since the kernel is build optimized, it seems the stack is not\naccurate. It appears the issue is related to wfx_set_mfp_ap(). The issue\nis obvious in this function: memory allocated by ieee80211_beacon_get()\nis never released. Fixing this leak makes kmemleak happy.",
  "id": "GHSA-vmcx-j4f5-gfcv",
  "modified": "2024-04-17T12:32:05Z",
  "published": "2024-04-17T12:32:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-26896"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/12f00a367b2b62756e0396f14b54c2c15524e1c3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3a71ec74e5e3478d202a1874f085ca3ef40be49b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a1f57a0127b89a6b6620514564aa7eaec16d9af3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b8cfb7c819dd39965136a66fe3a7fde688d976fc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dadbb5d29d6c5f571a50272fce8c1505a9559487"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • 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.