GHSA-QVFP-2HW2-QFFH

Vulnerability from github – Published: 2024-12-27 15:31 – Updated: 2025-01-15 21:31
VLAI
Details

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

binder: fix memleak of proc->delivered_freeze

If a freeze notification is cleared with BC_CLEAR_FREEZE_NOTIFICATION before calling binder_freeze_notification_done(), then it is detached from its reference (e.g. ref->freeze) but the work remains queued in proc->delivered_freeze. This leads to a memory leak when the process exits as any pending entries in proc->delivered_freeze are not freed:

unreferenced object 0xffff38e8cfa36180 (size 64): comm "binder-util", pid 655, jiffies 4294936641 hex dump (first 32 bytes): b8 e9 9e c8 e8 38 ff ff b8 e9 9e c8 e8 38 ff ff .....8.......8.. 0b 00 00 00 00 00 00 00 3c 1f 4b 00 00 00 00 00 ........<.K..... backtrace (crc 95983b32): [<000000000d0582cf>] kmemleak_alloc+0x34/0x40 [<000000009c99a513>] __kmalloc_cache_noprof+0x208/0x280 [<00000000313b1704>] binder_thread_write+0xdec/0x439c [<000000000cbd33bb>] binder_ioctl+0x1b68/0x22cc [<000000002bbedeeb>] __arm64_sys_ioctl+0x124/0x190 [<00000000b439adee>] invoke_syscall+0x6c/0x254 [<00000000173558fc>] el0_svc_common.constprop.0+0xac/0x230 [<0000000084f72311>] do_el0_svc+0x40/0x58 [<000000008b872457>] el0_svc+0x38/0x78 [<00000000ee778653>] el0t_64_sync_handler+0x120/0x12c [<00000000a8ec61bf>] el0t_64_sync+0x190/0x194

This patch fixes the leak by ensuring that any pending entries in proc->delivered_freeze are freed during binder_deferred_release().

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-56553"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-401"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-12-27T15:15:14Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbinder: fix memleak of proc-\u003edelivered_freeze\n\nIf a freeze notification is cleared with BC_CLEAR_FREEZE_NOTIFICATION\nbefore calling binder_freeze_notification_done(), then it is detached\nfrom its reference (e.g. ref-\u003efreeze) but the work remains queued in\nproc-\u003edelivered_freeze. This leads to a memory leak when the process\nexits as any pending entries in proc-\u003edelivered_freeze are not freed:\n\n  unreferenced object 0xffff38e8cfa36180 (size 64):\n    comm \"binder-util\", pid 655, jiffies 4294936641\n    hex dump (first 32 bytes):\n      b8 e9 9e c8 e8 38 ff ff b8 e9 9e c8 e8 38 ff ff  .....8.......8..\n      0b 00 00 00 00 00 00 00 3c 1f 4b 00 00 00 00 00  ........\u003c.K.....\n    backtrace (crc 95983b32):\n      [\u003c000000000d0582cf\u003e] kmemleak_alloc+0x34/0x40\n      [\u003c000000009c99a513\u003e] __kmalloc_cache_noprof+0x208/0x280\n      [\u003c00000000313b1704\u003e] binder_thread_write+0xdec/0x439c\n      [\u003c000000000cbd33bb\u003e] binder_ioctl+0x1b68/0x22cc\n      [\u003c000000002bbedeeb\u003e] __arm64_sys_ioctl+0x124/0x190\n      [\u003c00000000b439adee\u003e] invoke_syscall+0x6c/0x254\n      [\u003c00000000173558fc\u003e] el0_svc_common.constprop.0+0xac/0x230\n      [\u003c0000000084f72311\u003e] do_el0_svc+0x40/0x58\n      [\u003c000000008b872457\u003e] el0_svc+0x38/0x78\n      [\u003c00000000ee778653\u003e] el0t_64_sync_handler+0x120/0x12c\n      [\u003c00000000a8ec61bf\u003e] el0t_64_sync+0x190/0x194\n\nThis patch fixes the leak by ensuring that any pending entries in\nproc-\u003edelivered_freeze are freed during binder_deferred_release().",
  "id": "GHSA-qvfp-2hw2-qffh",
  "modified": "2025-01-15T21:31:40Z",
  "published": "2024-12-27T15:31:53Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56553"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1db76ec2b4b206ff943e292a0b55e68ff3443598"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b8b77712142fb146fe18d2253bc8a798d522e427"
    }
  ],
  "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…

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.

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.


Loading…