CVE-2026-46209 drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs()

High 7.8 Published Updated

An integer overflow in Linux kernel DRM allows out-of-bounds memory access, potentially leading to code execution or data disclosure.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-46209?

CVE-2026-46209 is a high-severity vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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().

Weakness: CWE-787, CWE-190

Which versions are affected by CVE-2026-46209?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-46209?

Apply the vendor's patch.

Is CVE-2026-46209 being exploited?

There is no known exploitation of CVE-2026-46209 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-88985, BELL-CVE-2026-46209, DEBIAN-CVE-2026-46209, GHSA-f8g6-g8cv-582v, ROOT-OS-DEBIAN-11-CVE-2026-46209, ROOT-OS-DEBIAN-12-CVE-2026-46209 and 3 more.

Is CVE-2026-46209 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free