Answer in brief
CVE-2026-90409 records a Unknown severity vulnerability in drm/panthor: Add vm_bind region with kbo range overlap check. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=647810ec247641eb5aec8caef818919a4518a0b1 <761cf9c63274a5b711c3dc829601723215710d2d || >=647810ec247641eb5aec8caef818919a4518a0b1 <985f5e12f3cdf43030e13c2bbd154913133b5c3f | 761cf9c63274a5b711c3dc829601723215710d2d, 985f5e12f3cdf43030e13c2bbd154913133b5c3f |
| Linux/Linuxgeneric | 6.10 | Not reported |
| Linux/Linuxgeneric | >=647810ec247641eb5aec8caef818919a4518a0b1 <f2be47fa8e225968eb66863657143fe900ec4bca || >=647810ec247641eb5aec8caef818919a4518a0b1 <761cf9c63274a5b711c3dc829601723215710d2d || >=647810ec247641eb5aec8caef818919a4518a0b1 <985f5e12f3cdf43030e13c2bbd154913133b5c3f | f2be47fa8e225968eb66863657143fe900ec4bca, 761cf9c63274a5b711c3dc829601723215710d2d, 985f5e12f3cdf43030e13c2bbd154913133b5c3f |
| Linux/Linuxgeneric | >=647810ec247641eb5aec8caef818919a4518a0b1 <276753aaad65e6f7dac7989a600c1c2d3a382c1a || >=647810ec247641eb5aec8caef818919a4518a0b1 <f2be47fa8e225968eb66863657143fe900ec4bca || >=647810ec247641eb5aec8caef818919a4518a0b1 <761cf9c63274a5b711c3dc829601723215710d2d || >=647810ec247641eb5aec8caef818919a4518a0b1 <985f5e12f3cdf43030e13c2bbd154913133b5c3f | 276753aaad65e6f7dac7989a600c1c2d3a382c1a, f2be47fa8e225968eb66863657143fe900ec4bca, 761cf9c63274a5b711c3dc829601723215710d2d, 985f5e12f3cdf43030e13c2bbd154913133b5c3f |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.