Answer in brief
CVE-2026-46209 records a Unknown severity vulnerability in drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs(). The current sources do not mark it as known exploited. The current feed maps 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.
Answer in brief
CVE-2026-46209 records a Unknown severity vulnerability in drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs(). The current sources do not mark it as known exploited. The current feed maps 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <11427ad6c9f0def5ce567982b785da3191946430 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <adfc5ba4ef4dd2bca5969f40e8fc7b41fb3902ad || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <22922f7dae74409fc4bf0f1142710cb6b8ce8cc2 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <6b992591e04f2cce813bcf239b354f375bbf84d3 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <1da4ab7189f1064b3b712b388772c008b4d82580 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <1a17ea9861e89585361caa8bc231bd22dc6dbe7d || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <c5fc49d8470c5ebf3b41607600f277158f159950 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <3d4c2268bd7243c3780fe32bf24ff876da272acf | 11427ad6c9f0def5ce567982b785da3191946430, adfc5ba4ef4dd2bca5969f40e8fc7b41fb3902ad, 22922f7dae74409fc4bf0f1142710cb6b8ce8cc2, 6b992591e04f2cce813bcf239b354f375bbf84d3, 1da4ab7189f1064b3b712b388772c008b4d82580, 1a17ea9861e89585361caa8bc231bd22dc6dbe7d, c5fc49d8470c5ebf3b41607600f277158f159950, 3d4c2268bd7243c3780fe32bf24ff876da272acf |
| Linux/Linuxgeneric | 4.14 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <11427ad6c9f0def5ce567982b785da3191946430 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <adfc5ba4ef4dd2bca5969f40e8fc7b41fb3902ad || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <22922f7dae74409fc4bf0f1142710cb6b8ce8cc2 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <6b992591e04f2cce813bcf239b354f375bbf84d3 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <1da4ab7189f1064b3b712b388772c008b4d82580 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <1a17ea9861e89585361caa8bc231bd22dc6dbe7d || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <c5fc49d8470c5ebf3b41607600f277158f159950 || >=4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 <3d4c2268bd7243c3780fe32bf24ff876da272acf | 11427ad6c9f0def5ce567982b785da3191946430, adfc5ba4ef4dd2bca5969f40e8fc7b41fb3902ad, 22922f7dae74409fc4bf0f1142710cb6b8ce8cc2, 6b992591e04f2cce813bcf239b354f375bbf84d3, 1da4ab7189f1064b3b712b388772c008b4d82580, 1a17ea9861e89585361caa8bc231bd22dc6dbe7d, c5fc49d8470c5ebf3b41607600f277158f159950, 3d4c2268bd7243c3780fe32bf24ff876da272acf |
| Linux/Linuxgeneric | 4.14 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.