CVE-2025-38374 (GCVE-0-2025-38374)
Vulnerability from cvelistv5
Published
2025-07-25 12:53
Modified
2025-07-28 04:20
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: optee: ffa: fix sleep in atomic context The OP-TEE driver registers the function notif_callback() for FF-A notifications. However, this function is called in an atomic context leading to errors like this when processing asynchronous notifications: | BUG: sleeping function called from invalid context at kernel/locking/mutex.c:258 | in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 9, name: kworker/0:0 | preempt_count: 1, expected: 0 | RCU nest depth: 0, expected: 0 | CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.14.0-00019-g657536ebe0aa #13 | Hardware name: linux,dummy-virt (DT) | Workqueue: ffa_pcpu_irq_notification notif_pcpu_irq_work_fn | Call trace: | show_stack+0x18/0x24 (C) | dump_stack_lvl+0x78/0x90 | dump_stack+0x18/0x24 | __might_resched+0x114/0x170 | __might_sleep+0x48/0x98 | mutex_lock+0x24/0x80 | optee_get_msg_arg+0x7c/0x21c | simple_call_with_arg+0x50/0xc0 | optee_do_bottom_half+0x14/0x20 | notif_callback+0x3c/0x48 | handle_notif_callbacks+0x9c/0xe0 | notif_get_and_handle+0x40/0x88 | generic_exec_single+0x80/0xc0 | smp_call_function_single+0xfc/0x1a0 | notif_pcpu_irq_work_fn+0x2c/0x38 | process_one_work+0x14c/0x2b4 | worker_thread+0x2e4/0x3e0 | kthread+0x13c/0x210 | ret_from_fork+0x10/0x20 Fix this by adding work queue to process the notification in a non-atomic context.
Impacted products
Vendor Product Version
Linux Linux Version: d0476a59de064205f4aaa8f7c6d6f32bc28a44d4
Version: d0476a59de064205f4aaa8f7c6d6f32bc28a44d4
Version: d0476a59de064205f4aaa8f7c6d6f32bc28a44d4
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/tee/optee/ffa_abi.c",
            "drivers/tee/optee/optee_private.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5f28563f0c6862c99eb115c918421d9b73f137ad",
              "status": "affected",
              "version": "d0476a59de064205f4aaa8f7c6d6f32bc28a44d4",
              "versionType": "git"
            },
            {
              "lessThan": "f27cf15783bd60063c6c97434cbd67ebd91d8db5",
              "status": "affected",
              "version": "d0476a59de064205f4aaa8f7c6d6f32bc28a44d4",
              "versionType": "git"
            },
            {
              "lessThan": "312d02adb959ea199372f375ada06e0186f651e4",
              "status": "affected",
              "version": "d0476a59de064205f4aaa8f7c6d6f32bc28a44d4",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/tee/optee/ffa_abi.c",
            "drivers/tee/optee/optee_private.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.8"
            },
            {
              "lessThan": "6.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.37",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.15.*",
              "status": "unaffected",
              "version": "6.15.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.16",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.37",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15.6",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.16",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\noptee: ffa: fix sleep in atomic context\n\nThe OP-TEE driver registers the function notif_callback() for FF-A\nnotifications. However, this function is called in an atomic context\nleading to errors like this when processing asynchronous notifications:\n\n | BUG: sleeping function called from invalid context at kernel/locking/mutex.c:258\n | in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 9, name: kworker/0:0\n | preempt_count: 1, expected: 0\n | RCU nest depth: 0, expected: 0\n | CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.14.0-00019-g657536ebe0aa #13\n | Hardware name: linux,dummy-virt (DT)\n | Workqueue: ffa_pcpu_irq_notification notif_pcpu_irq_work_fn\n | Call trace:\n |  show_stack+0x18/0x24 (C)\n |  dump_stack_lvl+0x78/0x90\n |  dump_stack+0x18/0x24\n |  __might_resched+0x114/0x170\n |  __might_sleep+0x48/0x98\n |  mutex_lock+0x24/0x80\n |  optee_get_msg_arg+0x7c/0x21c\n |  simple_call_with_arg+0x50/0xc0\n |  optee_do_bottom_half+0x14/0x20\n |  notif_callback+0x3c/0x48\n |  handle_notif_callbacks+0x9c/0xe0\n |  notif_get_and_handle+0x40/0x88\n |  generic_exec_single+0x80/0xc0\n |  smp_call_function_single+0xfc/0x1a0\n |  notif_pcpu_irq_work_fn+0x2c/0x38\n |  process_one_work+0x14c/0x2b4\n |  worker_thread+0x2e4/0x3e0\n |  kthread+0x13c/0x210\n |  ret_from_fork+0x10/0x20\n\nFix this by adding work queue to process the notification in a\nnon-atomic context."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-07-28T04:20:19.910Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/5f28563f0c6862c99eb115c918421d9b73f137ad"
        },
        {
          "url": "https://git.kernel.org/stable/c/f27cf15783bd60063c6c97434cbd67ebd91d8db5"
        },
        {
          "url": "https://git.kernel.org/stable/c/312d02adb959ea199372f375ada06e0186f651e4"
        }
      ],
      "title": "optee: ffa: fix sleep in atomic context",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-38374",
    "datePublished": "2025-07-25T12:53:16.785Z",
    "dateReserved": "2025-04-16T04:51:24.009Z",
    "dateUpdated": "2025-07-28T04:20:19.910Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-38374\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-07-25T13:15:26.400\",\"lastModified\":\"2025-07-25T15:29:19.837\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\noptee: ffa: fix sleep in atomic context\\n\\nThe OP-TEE driver registers the function notif_callback() for FF-A\\nnotifications. However, this function is called in an atomic context\\nleading to errors like this when processing asynchronous notifications:\\n\\n | BUG: sleeping function called from invalid context at kernel/locking/mutex.c:258\\n | in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 9, name: kworker/0:0\\n | preempt_count: 1, expected: 0\\n | RCU nest depth: 0, expected: 0\\n | CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.14.0-00019-g657536ebe0aa #13\\n | Hardware name: linux,dummy-virt (DT)\\n | Workqueue: ffa_pcpu_irq_notification notif_pcpu_irq_work_fn\\n | Call trace:\\n |  show_stack+0x18/0x24 (C)\\n |  dump_stack_lvl+0x78/0x90\\n |  dump_stack+0x18/0x24\\n |  __might_resched+0x114/0x170\\n |  __might_sleep+0x48/0x98\\n |  mutex_lock+0x24/0x80\\n |  optee_get_msg_arg+0x7c/0x21c\\n |  simple_call_with_arg+0x50/0xc0\\n |  optee_do_bottom_half+0x14/0x20\\n |  notif_callback+0x3c/0x48\\n |  handle_notif_callbacks+0x9c/0xe0\\n |  notif_get_and_handle+0x40/0x88\\n |  generic_exec_single+0x80/0xc0\\n |  smp_call_function_single+0xfc/0x1a0\\n |  notif_pcpu_irq_work_fn+0x2c/0x38\\n |  process_one_work+0x14c/0x2b4\\n |  worker_thread+0x2e4/0x3e0\\n |  kthread+0x13c/0x210\\n |  ret_from_fork+0x10/0x20\\n\\nFix this by adding work queue to process the notification in a\\nnon-atomic context.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/312d02adb959ea199372f375ada06e0186f651e4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/5f28563f0c6862c99eb115c918421d9b73f137ad\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f27cf15783bd60063c6c97434cbd67ebd91d8db5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


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…