In the Linux kernel, the following vulnerability has been resolved: fbdev: bitblit: bound-check glyph index in bit_cursor() bit_cursor() fetches the… (CVE-2026-74635)
A vulnerability in the Linux kernel's fbdev bitblit component was resolved that involved an out-of-bounds read in the bit_cursor() function. This occurred because the glyph index fetched from the screen buffer could exceed the current font's glyph count, leading to a global out-of-bounds memory access. The issue arises when the font changes from one with 512 glyphs to one with 256 glyphs, or when arbitrary values are written to the virtual console screen buffer without proper bounds checking. The fix adds proper clamping of the glyph index to prevent out-of-bounds reads without altering cursor behavior.
AI Analysis
Technical Summary
The Linux kernel fbdev subsystem's bitblit code had a vulnerability (CVE-2026-74635) where bit_cursor() did not properly bound-check the glyph index fetched from the screen buffer. The screen buffer value, obtained via scr_readw(), could be larger than the font's glyph count, especially after switching fonts from 512 to 256 glyphs or when arbitrary 16-bit values were written via vcs_write(). This led to a global out-of-bounds read detected by KASAN in soft_cursor(). The patch adds clamping of the glyph index in bit_cursor() to the font's charcount, completing the bounds checking already present in related functions. This prevents out-of-bounds memory access without changing cursor semantics.
Potential Impact
The vulnerability allows an out-of-bounds read in kernel memory, which can cause kernel crashes or memory corruption. While no direct exploit or active exploitation is known, such memory safety issues can potentially be leveraged for denial of service or as a component in privilege escalation attacks. The issue is limited to the fbdev bitblit code path and involves virtual console font handling and screen buffer manipulation.
Mitigation Recommendations
A fix has been applied to the Linux kernel to clamp the glyph index in bit_cursor(), preventing out-of-bounds reads. Users should update to a kernel version that includes this patch. Since this is a kernel code fix, no additional workarounds are indicated. Patch status is not explicitly stated in the input data; check the vendor advisory or Linux kernel stable release notes for the exact fixed version.
In the Linux kernel, the following vulnerability has been resolved: fbdev: bitblit: bound-check glyph index in bit_cursor() bit_cursor() fetches the… (CVE-2026-74635)
Description
A vulnerability in the Linux kernel's fbdev bitblit component was resolved that involved an out-of-bounds read in the bit_cursor() function. This occurred because the glyph index fetched from the screen buffer could exceed the current font's glyph count, leading to a global out-of-bounds memory access. The issue arises when the font changes from one with 512 glyphs to one with 256 glyphs, or when arbitrary values are written to the virtual console screen buffer without proper bounds checking. The fix adds proper clamping of the glyph index to prevent out-of-bounds reads without altering cursor behavior.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel fbdev subsystem's bitblit code had a vulnerability (CVE-2026-74635) where bit_cursor() did not properly bound-check the glyph index fetched from the screen buffer. The screen buffer value, obtained via scr_readw(), could be larger than the font's glyph count, especially after switching fonts from 512 to 256 glyphs or when arbitrary 16-bit values were written via vcs_write(). This led to a global out-of-bounds read detected by KASAN in soft_cursor(). The patch adds clamping of the glyph index in bit_cursor() to the font's charcount, completing the bounds checking already present in related functions. This prevents out-of-bounds memory access without changing cursor semantics.
Potential Impact
The vulnerability allows an out-of-bounds read in kernel memory, which can cause kernel crashes or memory corruption. While no direct exploit or active exploitation is known, such memory safety issues can potentially be leveraged for denial of service or as a component in privilege escalation attacks. The issue is limited to the fbdev bitblit code path and involves virtual console font handling and screen buffer manipulation.
Mitigation Recommendations
A fix has been applied to the Linux kernel to clamp the glyph index in bit_cursor(), preventing out-of-bounds reads. Users should update to a kernel version that includes this patch. Since this is a kernel code fix, no additional workarounds are indicated. Patch status is not explicitly stated in the input data; check the vendor advisory or Linux kernel stable release notes for the exact fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gcm2-cr9p-5jc7
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74635"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f2acd9273b499bc824
Added to database: 08/22/2026, 22:51:30 UTC
Last enriched: 08/22/2026, 23:40:40 UTC
Last updated: 08/23/2026, 00:32:05 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.