CVE-2026-63826Disclosure

LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

In the Linux kernel, the following vulnerability has been resolved: fbdev: fix use-after-free in store_modes() store_modes() replaces a framebuffer's modelist with modes from userspace. On success it frees the old modelist with fb_destroy_modelist(). Two fields still point into that freed list. One pointer is fb_display[i].mode, the mode a console is using. fbcon_new_modelist() moves these pointers to the new list. It only does so for consoles still mapped to the framebuffer. An unmapped console is skipped and keeps its stale pointer. Unbinding fbcon, for example, sets con2fb_map[i] to -1 but leaves fb_display[i].mode set. An FBIOPUT_VSCREENINFO ioctl with FB_ACTIVATE_INV_MODE later reaches fbcon_mode_deleted(). That function reads the stale fb_display[i].mode through fb_mode_is_equal(). The read is a use-after-free. The other pointer is fb_info->mode, the current mode. It is set through the mode sysfs attribute. store_modes() does not update fb_info->mode, so it is left pointing into the freed list. show_mode(), the attribute's read handler, dereferences the stale fb_info->mode through mode_string(). The read is a use-after-free. Clear both pointers before freeing the list. Commit a1f305893074 ("fbcon: Set fb_display[i]->mode to NULL when the mode is released") added the helper fbcon_delete_modelist(). It clears every fb_display[i].mode that points into a given list. So far it is called only from the unregister path. Call it from store_modes() too, and set fb_info->mode to NULL.

0.5/ 10 priority

Sources & remediation

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • Peaked 1d ago at 1 mentions (2026-07-19); latest day: 1
  • 2 total mentions across 2 days

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-07-19: 1Mentions · 2026-07-20: 1Patch / Workaround · 2026-07-20: 1Technical Details · 2026-07-19: 1Technical Details · 2026-07-20: 107-1907-20
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
Full discourse2 posts
  • Windows Forum@windowsforum
    Disclosure

    🐧 CVE-2026-63826 hits Linux’s legacy fbdev stack—not Windows directly, but WSL 2, VMs, dual-boot rigs, and appliances still count. “Legacy” is kernel-speak for “still waiting to bite you.” https://windowsforum.com/threads/cve-2026-63826-update-linux-kernels-to-fix-fbdev-use-after-free.439543/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #LinuxKernel #KernelVulnerabilities #Cve202663826 #Wsl2Security https://t.co/NFVgytzmzS

    Post summary

    CVE‑2026‑63826 is a use‑after‑free flaw in Linux’s legacy fbdev stack; the post urges kernel updates but provides no evidence of active exploitation or PoC.

    0000042
    1.3K followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-63826 Use-After-Free Vulnerability in Linux Kernel fbdev store_modes() Function https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-63826

    Post summary

    The text announces CVE‑2026‑63826 as a use‑after‑free flaw in the Linux kernel fbdev store_modes() function, providing a link to more details.

    0000088
    4.1K followersView on X

Explore more