{"api_version":"1","generated_at":"2026-10-15T14:27:10+00:00","cve":"CVE-2026-90409","urls":{"html":"https://cve.report/CVE-2026-90409","api":"https://cve.report/api/cve/CVE-2026-90409.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90409","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90409"},"summary":{"title":"drm/panthor: Add vm_bind region with kbo range overlap check","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panthor: Add vm_bind region with kbo range overlap check\n\nWhen a VM is created, caller has to specify the range of the address space\ncarve-out set aside for mapping kernel BO's. That means vm_bind mappings of\nUM-exposed BO's should not intersect with that region, but at the moment\nwe're not checking this.\n\nAt first, I thought of giving these values to drm_gpuvm_init() through its\nreserve_{offset, range} arguments, but it turns out that is meant for VM\naddress spans that are not managed through the usual drm_gpuvm split/merge\ncircuit, so storing the end of the user VA range at VM creation time and\ndoing a quick check in the vm_bind ioctl path was the simplest workaround.\n\nThe new check also makes sure vm_bind range doesn't overflow the size of a\n64-bit unsigned integer. That was already being done further down the call\nstack inside drm_gpuvm_sm_map -> drm_gpuvm_range_valid, but it's best to\nfail early in the driver before GPUVM functions are invoked so that we\nwon't waste time allocating vm_bind context resources.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:40","updated_at":"2026-10-15 11:18:02"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/761cf9c63274a5b711c3dc829601723215710d2d","name":"https://git.kernel.org/stable/c/761cf9c63274a5b711c3dc829601723215710d2d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f2be47fa8e225968eb66863657143fe900ec4bca","name":"https://git.kernel.org/stable/c/f2be47fa8e225968eb66863657143fe900ec4bca","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/985f5e12f3cdf43030e13c2bbd154913133b5c3f","name":"https://git.kernel.org/stable/c/985f5e12f3cdf43030e13c2bbd154913133b5c3f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90409","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90409","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 647810ec247641eb5aec8caef818919a4518a0b1 f2be47fa8e225968eb66863657143fe900ec4bca git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 647810ec247641eb5aec8caef818919a4518a0b1 761cf9c63274a5b711c3dc829601723215710d2d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 647810ec247641eb5aec8caef818919a4518a0b1 985f5e12f3cdf43030e13c2bbd154913133b5c3f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.57 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * 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/panthor/panthor_mmu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"f2be47fa8e225968eb66863657143fe900ec4bca","status":"affected","version":"647810ec247641eb5aec8caef818919a4518a0b1","versionType":"git"},{"lessThan":"761cf9c63274a5b711c3dc829601723215710d2d","status":"affected","version":"647810ec247641eb5aec8caef818919a4518a0b1","versionType":"git"},{"lessThan":"985f5e12f3cdf43030e13c2bbd154913133b5c3f","status":"affected","version":"647810ec247641eb5aec8caef818919a4518a0b1","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/panthor/panthor_mmu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.10"},{"lessThan":"6.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.57","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.57","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panthor: Add vm_bind region with kbo range overlap check\n\nWhen a VM is created, caller has to specify the range of the address space\ncarve-out set aside for mapping kernel BO's. That means vm_bind mappings of\nUM-exposed BO's should not intersect with that region, but at the moment\nwe're not checking this.\n\nAt first, I thought of giving these values to drm_gpuvm_init() through its\nreserve_{offset, range} arguments, but it turns out that is meant for VM\naddress spans that are not managed through the usual drm_gpuvm split/merge\ncircuit, so storing the end of the user VA range at VM creation time and\ndoing a quick check in the vm_bind ioctl path was the simplest workaround.\n\nThe new check also makes sure vm_bind range doesn't overflow the size of a\n64-bit unsigned integer. That was already being done further down the call\nstack inside drm_gpuvm_sm_map -> drm_gpuvm_range_valid, but it's best to\nfail early in the driver before GPUVM functions are invoked so that we\nwon't waste time allocating vm_bind context resources."}],"providerMetadata":{"dateUpdated":"2026-10-15T10:11:12.063Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/f2be47fa8e225968eb66863657143fe900ec4bca"},{"url":"https://git.kernel.org/stable/c/761cf9c63274a5b711c3dc829601723215710d2d"},{"url":"https://git.kernel.org/stable/c/985f5e12f3cdf43030e13c2bbd154913133b5c3f"}],"title":"drm/panthor: Add vm_bind region with kbo range overlap check","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90409","datePublished":"2026-09-17T16:09:36.740Z","dateReserved":"2026-09-11T19:38:34.812Z","dateUpdated":"2026-10-15T10:11:12.063Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:40","lastModifiedDate":"2026-10-15 11:18:02","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90409","Ordinal":"1","Title":"drm/panthor: Add vm_bind region with kbo range overlap check","CVE":"CVE-2026-90409","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90409","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panthor: Add vm_bind region with kbo range overlap check\n\nWhen a VM is created, caller has to specify the range of the address space\ncarve-out set aside for mapping kernel BO's. That means vm_bind mappings of\nUM-exposed BO's should not intersect with that region, but at the moment\nwe're not checking this.\n\nAt first, I thought of giving these values to drm_gpuvm_init() through its\nreserve_{offset, range} arguments, but it turns out that is meant for VM\naddress spans that are not managed through the usual drm_gpuvm split/merge\ncircuit, so storing the end of the user VA range at VM creation time and\ndoing a quick check in the vm_bind ioctl path was the simplest workaround.\n\nThe new check also makes sure vm_bind range doesn't overflow the size of a\n64-bit unsigned integer. That was already being done further down the call\nstack inside drm_gpuvm_sm_map -> drm_gpuvm_range_valid, but it's best to\nfail early in the driver before GPUVM functions are invoked so that we\nwon't waste time allocating vm_bind context resources.","Type":"Description","Title":"drm/panthor: Add vm_bind region with kbo range overlap check"}]}}}