ghsa-ccvx-m3xj-rqw7
Vulnerability from github
Published
2025-06-18 12:30
Modified
2025-06-18 12:30
Details

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

mwifiex: fix sleep in atomic context bugs caused by dev_coredumpv

There are sleep in atomic context bugs when uploading device dump data in mwifiex. The root cause is that dev_coredumpv could not be used in atomic contexts, because it calls dev_set_name which include operations that may sleep. The call tree shows execution paths that could lead to bugs:

(Interrupt context) fw_dump_timer_fn mwifiex_upload_device_dump dev_coredumpv(..., GFP_KERNEL) dev_coredumpm() kzalloc(sizeof(*devcd), gfp); //may sleep dev_set_name kobject_set_name_vargs kvasprintf_const(GFP_KERNEL, ...); //may sleep kstrdup(s, GFP_KERNEL); //may sleep

The corresponding fail log is shown below:

[ 135.275938] usb 1-1: == mwifiex dump information to /sys/class/devcoredump start [ 135.281029] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:265 ... [ 135.293613] Call Trace: [ 135.293613] [ 135.293613] dump_stack_lvl+0x57/0x7d [ 135.293613] __might_resched.cold+0x138/0x173 [ 135.293613] ? dev_coredumpm+0xca/0x2e0 [ 135.293613] kmem_cache_alloc_trace+0x189/0x1f0 [ 135.293613] ? devcd_match_failing+0x30/0x30 [ 135.293613] dev_coredumpm+0xca/0x2e0 [ 135.293613] ? devcd_freev+0x10/0x10 [ 135.293613] dev_coredumpv+0x1c/0x20 [ 135.293613] ? devcd_match_failing+0x30/0x30 [ 135.293613] mwifiex_upload_device_dump+0x65/0xb0 [ 135.293613] ? mwifiex_dnld_fw+0x1b0/0x1b0 [ 135.293613] call_timer_fn+0x122/0x3d0 [ 135.293613] ? msleep_interruptible+0xb0/0xb0 [ 135.293613] ? lock_downgrade+0x3c0/0x3c0 [ 135.293613] ? __next_timer_interrupt+0x13c/0x160 [ 135.293613] ? lockdep_hardirqs_on_prepare+0xe/0x220 [ 135.293613] ? mwifiex_dnld_fw+0x1b0/0x1b0 [ 135.293613] __run_timers.part.0+0x3f8/0x540 [ 135.293613] ? call_timer_fn+0x3d0/0x3d0 [ 135.293613] ? arch_restore_msi_irqs+0x10/0x10 [ 135.293613] ? lapic_next_event+0x31/0x40 [ 135.293613] run_timer_softirq+0x4f/0xb0 [ 135.293613] __do_softirq+0x1c2/0x651 ... [ 135.293613] RIP: 0010:default_idle+0xb/0x10 [ 135.293613] RSP: 0018:ffff888006317e68 EFLAGS: 00000246 [ 135.293613] RAX: ffffffff82ad8d10 RBX: ffff888006301cc0 RCX: ffffffff82ac90e1 [ 135.293613] RDX: ffffed100d9ff1b4 RSI: ffffffff831ad140 RDI: ffffffff82ad8f20 [ 135.293613] RBP: 0000000000000003 R08: 0000000000000000 R09: ffff88806cff8d9b [ 135.293613] R10: ffffed100d9ff1b3 R11: 0000000000000001 R12: ffffffff84593410 [ 135.293613] R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff11000c62fd2 ... [ 135.389205] usb 1-1: == mwifiex dump information to /sys/class/devcoredump end

This patch uses delayed work to replace timer and moves the operations that may sleep into a delayed work in order to mitigate bugs, it was tested on Marvell 88W8801 chip whose port is usb and the firmware is usb8801_uapsta.bin. The following is the result after using delayed work to replace timer.

[ 134.936453] usb 1-1: == mwifiex dump information to /sys/class/devcoredump start [ 135.043344] usb 1-1: == mwifiex dump information to /sys/class/devcoredump end

As we can see, there is no bug now.

Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2022-50150"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-06-18T11:15:45Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmwifiex: fix sleep in atomic context bugs caused by dev_coredumpv\n\nThere are sleep in atomic context bugs when uploading device dump\ndata in mwifiex. The root cause is that dev_coredumpv could not\nbe used in atomic contexts, because it calls dev_set_name which\ninclude operations that may sleep. The call tree shows execution\npaths that could lead to bugs:\n\n   (Interrupt context)\nfw_dump_timer_fn\n  mwifiex_upload_device_dump\n    dev_coredumpv(..., GFP_KERNEL)\n      dev_coredumpm()\n        kzalloc(sizeof(*devcd), gfp); //may sleep\n        dev_set_name\n          kobject_set_name_vargs\n            kvasprintf_const(GFP_KERNEL, ...); //may sleep\n            kstrdup(s, GFP_KERNEL); //may sleep\n\nThe corresponding fail log is shown below:\n\n[  135.275938] usb 1-1: == mwifiex dump information to /sys/class/devcoredump start\n[  135.281029] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:265\n...\n[  135.293613] Call Trace:\n[  135.293613]  \u003cIRQ\u003e\n[  135.293613]  dump_stack_lvl+0x57/0x7d\n[  135.293613]  __might_resched.cold+0x138/0x173\n[  135.293613]  ? dev_coredumpm+0xca/0x2e0\n[  135.293613]  kmem_cache_alloc_trace+0x189/0x1f0\n[  135.293613]  ? devcd_match_failing+0x30/0x30\n[  135.293613]  dev_coredumpm+0xca/0x2e0\n[  135.293613]  ? devcd_freev+0x10/0x10\n[  135.293613]  dev_coredumpv+0x1c/0x20\n[  135.293613]  ? devcd_match_failing+0x30/0x30\n[  135.293613]  mwifiex_upload_device_dump+0x65/0xb0\n[  135.293613]  ? mwifiex_dnld_fw+0x1b0/0x1b0\n[  135.293613]  call_timer_fn+0x122/0x3d0\n[  135.293613]  ? msleep_interruptible+0xb0/0xb0\n[  135.293613]  ? lock_downgrade+0x3c0/0x3c0\n[  135.293613]  ? __next_timer_interrupt+0x13c/0x160\n[  135.293613]  ? lockdep_hardirqs_on_prepare+0xe/0x220\n[  135.293613]  ? mwifiex_dnld_fw+0x1b0/0x1b0\n[  135.293613]  __run_timers.part.0+0x3f8/0x540\n[  135.293613]  ? call_timer_fn+0x3d0/0x3d0\n[  135.293613]  ? arch_restore_msi_irqs+0x10/0x10\n[  135.293613]  ? lapic_next_event+0x31/0x40\n[  135.293613]  run_timer_softirq+0x4f/0xb0\n[  135.293613]  __do_softirq+0x1c2/0x651\n...\n[  135.293613] RIP: 0010:default_idle+0xb/0x10\n[  135.293613] RSP: 0018:ffff888006317e68 EFLAGS: 00000246\n[  135.293613] RAX: ffffffff82ad8d10 RBX: ffff888006301cc0 RCX: ffffffff82ac90e1\n[  135.293613] RDX: ffffed100d9ff1b4 RSI: ffffffff831ad140 RDI: ffffffff82ad8f20\n[  135.293613] RBP: 0000000000000003 R08: 0000000000000000 R09: ffff88806cff8d9b\n[  135.293613] R10: ffffed100d9ff1b3 R11: 0000000000000001 R12: ffffffff84593410\n[  135.293613] R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff11000c62fd2\n...\n[  135.389205] usb 1-1: == mwifiex dump information to /sys/class/devcoredump end\n\nThis patch uses delayed work to replace timer and moves the operations\nthat may sleep into a delayed work in order to mitigate bugs, it was\ntested on Marvell 88W8801 chip whose port is usb and the firmware is\nusb8801_uapsta.bin. The following is the result after using delayed\nwork to replace timer.\n\n[  134.936453] usb 1-1: == mwifiex dump information to /sys/class/devcoredump start\n[  135.043344] usb 1-1: == mwifiex dump information to /sys/class/devcoredump end\n\nAs we can see, there is no bug now.",
  "id": "GHSA-ccvx-m3xj-rqw7",
  "modified": "2025-06-18T12:30:50Z",
  "published": "2025-06-18T12:30:50Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50150"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/938139aef61bff52a154c68553fbaabd6924737f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/956b79c2066551845d7124b01c5845d02ccf47a1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a52ed4866d2b90dd5e4ae9dabd453f3ed8fa3cbc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a78b882c1a9feda10821a25201a0464674f8209e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c8e8b8b9f23a0c68855ecfc756b96be6c9946ec1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Loading…