CVE-2026-97604 — fbdev: vfb: defer cleanup until the last reference
In the Linux kernel, the following vulnerability has been resolved: fbdev: vfb: defer cleanup until the last reference FBIOGETCMAP takes a shallow snapshot of info->cmap and performs the usercopy after dropping info->lock. vfb_remove() frees the colormap immediately after unregistering the framebuffer, even when an open file still holds a reference to fb_info. A concurrent driver unbind can therefore free the colormap while the ioctl copies it to userspace. KASAN reports: BUG: KASAN: slab-use-after-free in _copy_to_user Read of size 512 by task poc/125 _copy_to_user (./include/linux/instrumented.h:129 ./include/linux/uaccess.h:201 lib/usercopy.c:24) fb_cmap_to_user (./include/linux/uaccess.h:230 drivers/video/fbdev/core/fbcmap.c:211) do_fb_ioctl (drivers/video/fbdev/core/fb_chrdev.c:114) Allocated by task 1: fb_alloc_cmap_gfp (./include/linux/slab.h:973 ./include/linux/slab.h:1290 drivers/video/fbdev/core/fbcmap.c:108) vfb_probe (drivers/video/fbdev/vfb.c:459) Freed by task 124: fb_dealloc_cmap (drivers/video/fbdev/core/fbcmap.c:151) vfb_remove (drivers/video/fbdev/vfb.c:489) unregister_framebuffer() drops the registration reference, and fbdev calls fb_destroy after the last put_fb_info(). Move the registered framebuffer's cleanup into an fb_destroy callback so its colormap and screen buffer stay alive until all file references have been released.
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)+2
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.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
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).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < bf49eac7ed11aabd0b9b790c062742a8e4be97c6≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < 040ce3950f64a11e9ee5646c8aaa91fd2e29e245≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < ab664e279eb2a68e55895dd115a9488807280f07≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < de5a0eda59fe4b3eacd1a67c992e54766bb6683f≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < 86356f13598f59f5acb1754895747dcdaf65a254≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < 5ff1effb047e465cde193d7df95988aa1520035e≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < 3c91e51a53cf805e551e5dc8149cd0539a6dbb9d≥ 5e266e2e0e19532c1b8e2e2bff1eb6ccf42e478a and < a0a34a40ed299c9c7cff6af163a5b883ee9d6d73 and 1 moreversion 2.6.30 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/a0a34a40ed299c9c7cff6af163a5b883ee9d6d73
- git.kernel.org/stable/c/bf49eac7ed11aabd0b9b790c062742a8e4be97c6
- git.kernel.org/stable/c/ab664e279eb2a68e55895dd115a9488807280f07
- git.kernel.org/stable/c/86356f13598f59f5acb1754895747dcdaf65a254
- git.kernel.org/stable/c/3c91e51a53cf805e551e5dc8149cd0539a6dbb9d
- git.kernel.org/stable/c/de5a0eda59fe4b3eacd1a67c992e54766bb6683f
- git.kernel.org/stable/c/5ff1effb047e465cde193d7df95988aa1520035e
- git.kernel.org/stable/c/040ce3950f64a11e9ee5646c8aaa91fd2e29e245
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 2d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 2d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 2d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 2d
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 CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- 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-97604 is "fbdev: vfb: defer cleanup until the last reference", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% 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.