Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-46209

drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs()

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.90, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

In the Linux kernel, the following vulnerability has been resolved: drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() drm_gem_fb_init_with_funcs() computes sub-sampled plane dimensions using plain integer division: unsigned int width = mode_cmd->width / (i ? info->hsub : 1); unsigned int height = mode_cmd->height / (i ? info->vsub : 1); However, the ioctl-level framebuffer_check() in drm_framebuffer.c uses drm_format_info_plane_width/height() which round up dimensions via DIV_ROUND_UP(). This inconsistency corrupts the subsequent GEM object size check for certain pixel format and dimension combinations. For example, with NV12 (vsub=2) and a 1-pixel-tall framebuffer the GEM size validation path sees height=0 instead of height=1. The expression (height - 1) then wraps to UINT_MAX as an unsigned int, causing min_size to overflow and wrap back to a small value. A tiny GEM object therefore passes the size guard, yet when the GPU accesses the chroma plane it will read or write memory beyond the object's bounds. Fix by replacing the open-coded divisions with drm_format_info_plane_width() and drm_format_info_plane_height(), which use DIV_ROUND_UP() and match the calculation already used in framebuffer_check().

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in 11427ad6c9f0def5ce567982b785da3191946430; From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in adfc5ba4ef4dd2bca5969f40e8fc7b41fb3902ad; From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in 22922f7dae74409fc4bf0f1142710cb6b8ce8cc2; From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in 6b992591e04f2cce813bcf239b354f375bbf84d3; From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in 1da4ab7189f1064b3b712b388772c008b4d82580; From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in 1a17ea9861e89585361caa8bc231bd22dc6dbe7d; From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in c5fc49d8470c5ebf3b41607600f277158f159950; From 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 · fixed in 3d4c2268bd7243c3780fe32bf24ff876da272acf

  • Linux Linux

    4.14

  • KernelLinux

    From 4.14.0 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.90; From 6.13.0 · fixed in 6.18.32; From 6.19.0 · fixed in 7.0.9

References 8

git.kernel.org