CVE-2026-46209 — drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs()
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().
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < 11427ad6c9f0def5ce567982b785da3191946430version 4.14≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < 3d4c2268bd7243c3780fe32bf24ff876da272acf≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < c5fc49d8470c5ebf3b41607600f277158f159950≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < 1a17ea9861e89585361caa8bc231bd22dc6dbe7d≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < 1da4ab7189f1064b3b712b388772c008b4d82580≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < 6b992591e04f2cce813bcf239b354f375bbf84d3≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < 22922f7dae74409fc4bf0f1142710cb6b8ce8cc2 and 1 more≥ 4c3dbb2c312c9fafbac30d98c523b8b1f3455d78 and < adfc5ba4ef4dd2bca5969f40e8fc7b41fb3902ad |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 4.14 and < 5.10.258version 7.1-rc1≥ 6.19 and < 7.0.9≥ 6.13 and < 6.18.32≥ 6.7 and < 6.12.90≥ 6.2 and < 6.6.140≥ 5.16 and < 6.1.175≥ 5.11 and < 5.15.209 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Analyzed → Modified
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
11 on the record
- git.kernel.org/stable/c/1da4ab7189f1064b3b712b388772c008b4d82580
- git.kernel.org/stable/c/c5fc49d8470c5ebf3b41607600f277158f159950
- git.kernel.org/stable/c/6b992591e04f2cce813bcf239b354f375bbf84d3
- git.kernel.org/stable/c/22922f7dae74409fc4bf0f1142710cb6b8ce8cc2
- git.kernel.org/stable/c/11427ad6c9f0def5ce567982b785da3191946430
- git.kernel.org/stable/c/1a17ea9861e89585361caa8bc231bd22dc6dbe7d
- git.kernel.org/stable/c/3d4c2268bd7243c3780fe32bf24ff876da272acf
- git.kernel.org/stable/c/adfc5ba4ef4dd2bca5969f40e8fc7b41fb3902ad
- nvd.nist.gov/vuln/detail/CVE-2026-46209
- github.com/advisories/GHSA-f8g6-g8cv-582v
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-46209 is "drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs()", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.