CVE-2026-63826: fbdev: fix use-after-free in store_modes()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0d35f9f194a858567a21017d69318a51e3a822b9, 2c1c805c65fb7dc7524e20376d6987721e73a0b1, 3047319e44f1368370f6fa2c04dea2961fb10215.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0d35f9f194a858567a21017d69318a51e3a822b9, 2c1c805c65fb7dc7524e20376d6987721e73a0b1, 3047319e44f1368370f6fa2c04dea2961fb10215 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 19, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3047319e44f1368370f6fa2c04dea2961fb10215affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5267eab88fa4c684459504b8be577ad64953b9a6affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c6765f39ed27014ff877b00a2efa494233404e17affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0d35f9f194a858567a21017d69318a51e3a822b9affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 70f1e000b88cfa8ca3fd7f4d082647fc089a7769affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2c1c805c65fb7dc7524e20376d6987721e73a0b1affected · git
- before 2.6.12not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.144 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.12.1 and later · before 6.1.191
- linux linux kernel6.2 and later · before 6.6.144
- linux linux kernel6.7 and later · before 6.12.95
- linux linux kernel6.13 and later · before 6.18.38
- linux linux kernel6.19 and later · before 7.1.3
- linux linux kernel2.6.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.95-1 | 6.12.95-1 |
| Debian:14 | linux | before 7.1.3-1 | 7.1.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63824Jul 19, 2026 · KEYS: fix overflow in keyctl_pkey_params_get_2()31Monitor
- ← EarlierCVE-2026-63825Jul 19, 2026 · gcov: use atomic counter updates to fix concurrent access crashes39Monitor
- Later →CVE-2026-63827Jul 19, 2026 · apparmor: fix use-after-free in rawdata dedup loop31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0d35f9f194a858567a21017d69318a51e3a822b9 | Vendor (CNA) |
| Linux Linux | 2c1c805c65fb7dc7524e20376d6987721e73a0b1 | Vendor (CNA) |
| Linux Linux | 3047319e44f1368370f6fa2c04dea2961fb10215 | Vendor (CNA) |
| Linux Linux | 5267eab88fa4c684459504b8be577ad64953b9a6 | Vendor (CNA) |
| Linux Linux | 70f1e000b88cfa8ca3fd7f4d082647fc089a7769 | Vendor (CNA) |
| Linux Linux | c6765f39ed27014ff877b00a2efa494233404e17 | Vendor (CNA) |
| debian:linux | 6.12.95-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0576 · Jul 20, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 7.8
- Severity— → high
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2c1c805c65fb7dc7524e20376d6987721e73a0b1
- git.kernel.org/stable/c/3047319e44f1368370f6fa2c04dea2961fb10215
- git.kernel.org/stable/c/5267eab88fa4c684459504b8be577ad64953b9a6
- git.kernel.org/stable/c/70f1e000b88cfa8ca3fd7f4d082647fc089a7769
- git.kernel.org/stable/c/c6765f39ed27014ff877b00a2efa494233404e17
Vendor advisories and official records. Exploit/PoC links are deliberately left out.