{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-40069","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-04-16T07:20:57.159Z","datePublished":"2025-10-28T11:48:38.232Z","dateUpdated":"2026-08-05T12:07:32.509Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:07:32.509Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm: Fix obj leak in VM_BIND error path\n\nIf we fail a handle-lookup part way thru, we need to drop the already\nobtained obj references.\n\nPatchwork: https://patchwork.freedesktop.org/patch/669784/"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - Reached only through the `DRM_IOCTL_MSM_VM_BIND` ioctl on the local msm DRM device/render node, which requires an open file descriptor on `/dev/dri/renderD*`. There is no remote or adjacent-network path to this code.\nAC:L - Triggering is fully deterministic and race-free — a single VM_BIND ioctl with one MSM_VM_BIND_OP_MAP op carrying a handle not present in `file->object_idr` (any large value, since IDR ids are allocated from 1 upward) drives the error path every time. All other validation (page-aligned iova/range, VA range) is trivially satisfied using values queryable via MSM_PARAM_VA_START/VA_SIZE.\nPR:L - Every ioctl on the path (MSM_SET_PARAM, MSM_SUBMITQUEUE_NEW, MSM_VM_BIND) is marked `DRM_RENDER_ALLOW`, so no DRM master, authentication, or capability is needed, and `MSM_PARAM_EN_VM_BIND` has no `capable()` gate. Any unprivileged process that can open the render node — including an Android app, a Chrome GPU sandbox process, or a desktop user on a Snapdragon laptop — qualifies.\nUI:N - The attacker issues the ioctls entirely from their own process; no victim action, no file to open, no device to plug in is involved.\nS:U - The corruption and any resulting escalation stay within the kernel's own security authority on the same host, with no crossing of a hypervisor, IOMMU, or other separate security scope.\nC:H - The union-aliased handle is dereferenced as a `struct drm_gem_object *` at an address the attacker fully controls; if that access succeeds, `drm_gem_object_free()` proceeds to read `obj->funcs->free` from attacker-shaped memory, giving a memory-corruption primitive that can be leveraged into arbitrary kernel memory disclosure.\nI:H - `kref_put()` performs an atomic read-modify-write (decrement) at the attacker-supplied address, and reaching zero funnels into an indirect call through a function pointer read from that same attacker-influenced memory — a write plus control-flow-hijack primitive, not a mere refcount imbalance.\nA:H - In the common case the wild pointer lands in an unmapped or PAN/SMAP-protected page and the `refcount_dec_and_test()` faults, producing an immediate kernel oops that kills the task and leaks the job/submitqueue state; an unprivileged user can trigger this at will, and with `panic_on_oops` (common on Android and hardened builds) it is a full system panic."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/msm/msm_gem_vma.c"],"versions":[{"version":"2e6a8a1fe2b262a6dfd0a65041fcd830ee1e7143","lessThan":"2b512909a291a964cfcf6b58de13256ab3e848c4","status":"affected","versionType":"git"},{"version":"2e6a8a1fe2b262a6dfd0a65041fcd830ee1e7143","lessThan":"278f8904434aa96055e793936b5977c010549e28","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/msm/msm_gem_vma.c"],"versions":[{"version":"6.17","status":"affected"},{"version":"0","lessThan":"6.17","status":"unaffected","versionType":"semver"},{"version":"6.17.3","lessThanOrEqual":"6.17.*","status":"unaffected","versionType":"semver"},{"version":"6.18","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.17","versionEndExcluding":"6.17.3"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.17","versionEndExcluding":"6.18"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/2b512909a291a964cfcf6b58de13256ab3e848c4"},{"url":"https://git.kernel.org/stable/c/278f8904434aa96055e793936b5977c010549e28"}],"title":"drm/msm: Fix obj leak in VM_BIND error path","x_generator":{"engine":"bippy-1.2.0"}}}}