drm/komeda: fix integer overflow in AFBC framebuffer size check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 65ad2392dd6d1691db93e82b08d3311298b9d64a · < fe1f80f8f6e8611ac6349b9d464e8750443390cf| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/komeda: fix integer overflow in AFBC framebuffer size check
The AFBC framebuffer size validation calculates the minimum required buffer size by adding the AFBC payload size to the framebuffer offset. This addition is performed without checking for integer overflow.
If the addition oveflows, the size check may incorrectly succed and allow userspace to provide an undersized drm_gem_object, potentially leading to out-of-bounds memory access.
Add usage of check_add_overflow() to safely compute the minimum required size and reject the framebuffer if an overflow is detected. This makes the AFBC size validation more robust against malformed.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
From the CVE record · Linux
The Linux kernel’s drm/komeda AFBC framebuffer size check can overflow when adding the payload size to the framebuffer offset. Local userspace can provide an undersized DRM GEM object that passes validation, potentially causing out-of-bounds memory access.
Engineers running Linux kernels with drm/komeda should check their kernel versions against the vendor advisory; affected versions were not specified.