Look up another CVE · open CVE-2026-80786 in the interactive tracker
CVE-2026-80786
fbdev: Wrap user-invoked calls to fb_set_var() in helper
Published 2026-09-04 (44 days ago) by the Linux kernel CNA. Subsystem drivers/video. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80786 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.1.12-1 | Update the kernel and reboot. Fixed in 7.1.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.12-1 | Update the kernel and reboot. Fixed in 7.1.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Handle fbcon during display updates in fb_set_var_from_user(). Check with fbcon if the mode change is possible, update hardware state and finally update fbcon. Update all callers. Only the FBIOPUT_VSCREENINFO ioctl currently does all steps. Other mode-changes callers in sysfs and driver code are missing fbcon-related steps. With the new helper, ps3fb and sh_mobile_lcdcfb no longer maintain fbcon state themselves.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/video/fbdev/core/fb_chrdev.c
drivers/video/fbdev/core/fbcon.c
drivers/video/fbdev/core/fbmem.c
drivers/video/fbdev/core/fbsysfs.c
drivers/video/fbdev/ps3fb.c
drivers/video/fbdev/sh_mobile_lcdcfb.c
include/linux/fb.h
- What this is
- FRAMEBUFFER COREMAINTAINERS section matched on drivers/video/fbdev/core/ · Odd Fixes
Check it on the machine
grep -wE 'CONFIG_FB|CONFIG_FB_CORE|CONFIG_FB_DEVICE|CONFIG_FRAMEBUFFER_CONSOLE' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormy
- trixie, forky, sidYnot built on s390x/s390x
- y
- built into the kernel image on every flavour - only a patch removes it
- Y
- built in where it is built at all; some flavours do not build it
- Build switches
- CONFIG_FB, CONFIG_FB_CORE, CONFIG_FB_DEVICE, CONFIG_FRAMEBUFFER_CONSOLE
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-04 (44 days ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.21%, higher than 10.0% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/video
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.12 | 6.18.57 | ed7e9715849a |
| 2.6.12 | 7.1.11 | 07f7e46833f7 |
| 2.6.12 | 7.2 | 6f611e5e5f33 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-80786, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.