{"api_version":"1","generated_at":"2026-11-09T02:10:42+00:00","cve":"CVE-2026-98512","urls":{"html":"https://cve.report/CVE-2026-98512","api":"https://cve.report/api/cve/CVE-2026-98512.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98512","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98512"},"summary":{"title":"drm/nouveau: RCU-free the scheduler-containing nouveau_sched","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau: RCU-free the scheduler-containing nouveau_sched\n\nstruct nouveau_sched embeds a struct drm_gpu_scheduler (base).\nnouveau_sched_destroy() calls nouveau_sched_fini() (which does\ndrm_sched_fini(&sched->base)) and then frees the object with plain\nkfree(sched).\n\ndrm_sched_fence_get_timeline_name() returns fence->sched->name, and the\nscheduler fence keeps a .release callback so it is not ops-detached on\nsignalling.  A finished fence exported to userspace via drm_syncobj /\nsync_file therefore keeps pointing at &sched->base after nouveau_sched_destroy(),\nand a later get_timeline_name() -- reachable unprivileged through\nSYNC_IOC_FILE_INFO -- dereferences freed memory (KASAN slab-use-after-free\nread).\n\nPer the dma-fence lifetime contract the exporter must keep the data backing a\nsignalled fence alive for an RCU grace period.  Free the scheduler-containing\nobject with kfree_rcu() instead of kfree().","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:02","updated_at":"2026-10-24 14:16:45"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.1","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","baseScore":7.1,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.1","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","data":{"baseScore":7.1,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/f7eae6d8d768fabd6b59779ca7da79e02c74e113","name":"https://git.kernel.org/stable/c/f7eae6d8d768fabd6b59779ca7da79e02c74e113","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/35151e9a8274174ccbb92e3b3ba7dc7a008dcada","name":"https://git.kernel.org/stable/c/35151e9a8274174ccbb92e3b3ba7dc7a008dcada","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/40edf5eefc3fd94592a91d6eb074d4fc6f606c75","name":"https://git.kernel.org/stable/c/40edf5eefc3fd94592a91d6eb074d4fc6f606c75","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cd6e11b6ebe04a0a1f1435df561acada9eadc563","name":"https://git.kernel.org/stable/c/cd6e11b6ebe04a0a1f1435df561acada9eadc563","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98512","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98512","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5f03a507b29e44a848f315c7240c19894dd8be4f 40edf5eefc3fd94592a91d6eb074d4fc6f606c75 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5f03a507b29e44a848f315c7240c19894dd8be4f 35151e9a8274174ccbb92e3b3ba7dc7a008dcada git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5f03a507b29e44a848f315c7240c19894dd8be4f cd6e11b6ebe04a0a1f1435df561acada9eadc563 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5f03a507b29e44a848f315c7240c19894dd8be4f f7eae6d8d768fabd6b59779ca7da79e02c74e113 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.8","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.8 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.112 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.55 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.9 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/nouveau/nouveau_sched.c","drivers/gpu/drm/nouveau/nouveau_sched.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"40edf5eefc3fd94592a91d6eb074d4fc6f606c75","status":"affected","version":"5f03a507b29e44a848f315c7240c19894dd8be4f","versionType":"git"},{"lessThan":"35151e9a8274174ccbb92e3b3ba7dc7a008dcada","status":"affected","version":"5f03a507b29e44a848f315c7240c19894dd8be4f","versionType":"git"},{"lessThan":"cd6e11b6ebe04a0a1f1435df561acada9eadc563","status":"affected","version":"5f03a507b29e44a848f315c7240c19894dd8be4f","versionType":"git"},{"lessThan":"f7eae6d8d768fabd6b59779ca7da79e02c74e113","status":"affected","version":"5f03a507b29e44a848f315c7240c19894dd8be4f","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/nouveau/nouveau_sched.c","drivers/gpu/drm/nouveau/nouveau_sched.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.112","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.55","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.9","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.112","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.55","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.9","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.8","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau: RCU-free the scheduler-containing nouveau_sched\n\nstruct nouveau_sched embeds a struct drm_gpu_scheduler (base).\nnouveau_sched_destroy() calls nouveau_sched_fini() (which does\ndrm_sched_fini(&sched->base)) and then frees the object with plain\nkfree(sched).\n\ndrm_sched_fence_get_timeline_name() returns fence->sched->name, and the\nscheduler fence keeps a .release callback so it is not ops-detached on\nsignalling.  A finished fence exported to userspace via drm_syncobj /\nsync_file therefore keeps pointing at &sched->base after nouveau_sched_destroy(),\nand a later get_timeline_name() -- reachable unprivileged through\nSYNC_IOC_FILE_INFO -- dereferences freed memory (KASAN slab-use-after-free\nread).\n\nPer the dma-fence lifetime contract the exporter must keep the data backing a\nsignalled fence alive for an RCU grace period.  Free the scheduler-containing\nobject with kfree_rcu() instead of kfree()."}],"metrics":[{"cvssV3_1":{"baseScore":7.1,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - A local process reaches the patched nouveau_sched_destroy() through DRM-fd close or DRM_IOCTL_NOUVEAU_CHANNEL_FREE, then triggers the dangling scheduler access through SYNC_IOC_FILE_INFO → sync_fill_fence_info() → drm_sched_fence_get_timeline_name(); no network path exists.\nAC:L - The attacker controls fence creation, export, scheduler teardown, and querying; affected branches permit a post-teardown query, and where concurrent timing is needed the attacker can gate its job on a syncobj and repeatedly race its completion and close against SYNC_IOC_FILE_INFO.\nPR:L - NOUVEAU_VM_INIT, VM_BIND, EXEC, CHANNEL_FREE, and the core syncobj ioctls are DRM_RENDER_ALLOW, while drm_ioctl_permit() imposes no DRM_MASTER, DRM_ROOT_ONLY, or capability check; ordinary render-node access suffices.\nUI:N - The attacker independently creates and exports the scheduler fence, closes the channel or DRM file to invoke nouveau_sched_destroy(), and queries the retained sync-file without any victim action.\nS:U - The freed nouveau_sched and the resulting disclosure or crash are within the same host-kernel security authority; the path does not cross a VM, IOMMU, or hypervisor boundary.\nC:H - drm_sched_fence_get_timeline_name() treats reclaimed nouveau_sched bytes as the name pointer; after heap reuse, sync_fill_fence_info() copies up to 31 bytes from that attacker-influenced address into user-visible obj_name, and repeated objects support arbitrary kernel-memory disclosure.\nI:N - The stale value is used only as the source pointer for strscpy() into a correctly sized, newly allocated sync_fence_info buffer; this path never writes through fence->sched or the attacker-influenced pointer, so it provides no demonstrated modification primitive.\nA:H - If reclaimed sched->name contains an invalid address, strscpy() in sync_fill_fence_info() can cause a kernel page fault and oops or panic; KASAN directly detects the slab use-after-free, and the local sequence is repeatable."}]}],"providerMetadata":{"dateUpdated":"2026-10-24T14:09:12.662Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/40edf5eefc3fd94592a91d6eb074d4fc6f606c75"},{"url":"https://git.kernel.org/stable/c/35151e9a8274174ccbb92e3b3ba7dc7a008dcada"},{"url":"https://git.kernel.org/stable/c/cd6e11b6ebe04a0a1f1435df561acada9eadc563"},{"url":"https://git.kernel.org/stable/c/f7eae6d8d768fabd6b59779ca7da79e02c74e113"}],"title":"drm/nouveau: RCU-free the scheduler-containing nouveau_sched","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98512","datePublished":"2026-10-18T15:17:27.102Z","dateReserved":"2026-09-25T10:25:14.354Z","dateUpdated":"2026-10-24T14:09:12.662Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:02","lastModifiedDate":"2026-10-24 14:16:45","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","baseScore":7.1,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98512","Ordinal":"1","Title":"drm/nouveau: RCU-free the scheduler-containing nouveau_sched","CVE":"CVE-2026-98512","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98512","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau: RCU-free the scheduler-containing nouveau_sched\n\nstruct nouveau_sched embeds a struct drm_gpu_scheduler (base).\nnouveau_sched_destroy() calls nouveau_sched_fini() (which does\ndrm_sched_fini(&sched->base)) and then frees the object with plain\nkfree(sched).\n\ndrm_sched_fence_get_timeline_name() returns fence->sched->name, and the\nscheduler fence keeps a .release callback so it is not ops-detached on\nsignalling.  A finished fence exported to userspace via drm_syncobj /\nsync_file therefore keeps pointing at &sched->base after nouveau_sched_destroy(),\nand a later get_timeline_name() -- reachable unprivileged through\nSYNC_IOC_FILE_INFO -- dereferences freed memory (KASAN slab-use-after-free\nread).\n\nPer the dma-fence lifetime contract the exporter must keep the data backing a\nsignalled fence alive for an RCU grace period.  Free the scheduler-containing\nobject with kfree_rcu() instead of kfree().","Type":"Description","Title":"drm/nouveau: RCU-free the scheduler-containing nouveau_sched"}]}}}