drm/panthor: Add vm_bind region with kbo range overlap check
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Add vm_bind region with kbo range overlap check When a VM is created, caller has to specify the range of the address space carve-out set aside for mapping kernel BO's. That means vm_bind mappings of UM-exposed BO's should not intersect with that region, but at the moment we're not checking this. At first, I thought of giving these values to drm_gpuvm_init() through its reserve_{offset, range} arguments, but it turns out that is meant for VM address spans that are not managed through the usual drm_gpuvm split/merge circuit, so storing the end of the user VA range at VM creation time and doing a quick check in the vm_bind ioctl path was the simplest workaround. The new check also makes sure vm_bind range doesn't overflow the size of a 64-bit unsigned integer. That was already being done further down the call stack inside drm_gpuvm_sm_map -> drm_gpuvm_range_valid, but it's best to fail early in the driver before GPUVM functions are invoked so that we won't waste time allocating vm_bind context resources.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.114, 6.18.57, 7.2.6
- CVEs
- CVE-2026-90409
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 01:29 UTC · Revision 1
Source evidence
drm/panthor: Add vm_bind region with kbo range overlap check
core-osv · Original sourcePublished 17 Sept 2026, 16:09 UTC
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Add vm_bind region with kbo range overlap check When a VM is created, caller has to specify the range of the address space carve-out set aside for mapping kernel BO's. That means vm_bind mappings of UM-exposed BO's should not intersect with that region, but at the moment we're not checking this. At first, I thought of giving these values to drm_gpuvm_init() through its reserve_{offset, range} arguments, but it turns out that is meant for VM address spans that are not managed through the usual drm_gpuvm split/merge circuit, so storing the end of the user VA range at VM creation time and doing a quick check in the vm_bind ioctl path was the simplest workaround. The new check also makes sure vm_bind range doesn't overflow the size of a 64-bit unsigned integer. That was already being done further down the call stack inside drm_gpuvm_sm_map -> drm_gpuvm_range_valid, but it's best to fail early in the driver before GPUVM functions are invoked so that we won't waste time allocating vm_bind context resources.
osv:CVE-2026-90409
Kernel
Fixed versions: 6.12.114, 6.18.57, 7.2.6
Complete source record
{
"id": "623180e25d274333bb2dc8001fa763aa58478b34da3c4925455faede90b87cd0",
"url": "https://osv.dev/vulnerability/CVE-2026-90409",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "drm/panthor: Add vm_bind region with kbo range overlap check",
"summary": "In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Add vm_bind region with kbo range overlap check When a VM is created, caller has to specify the range of the address space carve-out set aside for mapping kernel BO's. That means vm_bind mappings of UM-exposed BO's should not intersect with that region, but at the moment we're not checking this. At first, I thought of giving these values to drm_gpuvm_init() through its reserve_{offset, range} arguments, but it turns out that is meant for VM address spans that are not managed through the usual drm_gpuvm split/merge circuit, so storing the end of the user VA range at VM creation time and doing a quick check in the vm_bind ioctl path was the simplest workaround. The new check also makes sure vm_bind range doesn't overflow the size of a 64-bit unsigned integer. That was already being done further down the call stack inside drm_gpuvm_sm_map -> drm_gpuvm_range_valid, but it's best to fail early in the driver before GPUVM functions are invoked so that we won't waste time allocating vm_bind context resources.",
"evidence": "osv:CVE-2026-90409",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.114",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.57",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-90409",
"aliases": [
"CVE-2026-90409"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "647810ec247641eb5aec8caef818919a4518a0b1"
},
{
"fixed": "276753aaad65e6f7dac7989a600c1c2d3a382c1a"
},
{
"fixed": "f2be47fa8e225968eb66863657143fe900ec4bca"
},
{
"fixed": "761cf9c63274a5b711c3dc829601723215710d2d"
},
{
"fixed": "985f5e12f3cdf43030e13c2bbd154913133b5c3f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90409.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.10.0"
},
{
"fixed": "6.12.114"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.57"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90409.json"
}
}
],
"modified": "2026-10-28T02:30:52.357172425Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/276753aaad65e6f7dac7989a600c1c2d3a382c1a",
"https://git.kernel.org/stable/c/761cf9c63274a5b711c3dc829601723215710d2d",
"https://git.kernel.org/stable/c/985f5e12f3cdf43030e13c2bbd154913133b5c3f",
"https://git.kernel.org/stable/c/f2be47fa8e225968eb66863657143fe900ec4bca",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90409.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-90409",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90409.json"
}
},
"related_cves": [
{
"value": "CVE-2026-90409",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 521357,
"published_at": "2026-09-17T16:09:36.74+00:00"
}