CVE-2026-80785: fbdev: serialize mode sysfs access with lock_fb_info()
Noroxi assessment
Priority: Monitor (action score 0/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.15% (FIRST EPSS).
- Fixed version: Linux Linux 061db6b7a910b8378f3b2df64f8c0a3ddc6e85f2, 26135631ed8e487bc6aef70cc41934e258d09bbe; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 061db6b7a910b8378f3b2df64f8c0a3ddc6e85f2, 26135631ed8e487bc6aef70cc41934e258d09bbe; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: serialize mode sysfs access with lock_fb_info() show_mode(), show_modes(), and store_mode() access fb_info->modelist and fb_info->mode without holding lock_fb_info(). store_modes() takes lock_fb_info() while replacing the modelist and freeing the old one. A concurrent reader or writer can load a pointer to an old modelist entry before store_modes() frees it, then dereference freed memory or store a stale freed pointer in fb_info->mode. Take lock_fb_info() in show_mode(), show_modes(), and store_mode() to serialize with store_modes(). In show_mode(), copy the mode to the stack and format after dropping the lock. In store_mode(), split activate() into a _locked variant to avoid double-locking, and hold the locks for the modelist walk, mode conversion, activation, and fb_info->mode assignment together.
- Published
- Sep 4, 2026
- Updated
- Sep 7, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
—
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 26135631ed8e487bc6aef70cc41934e258d09bbeaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 061db6b7a910b8378f3b2df64f8c0a3ddc6e85f2affected · git
- before 2.6.12not affected · semver
- 7.1.11 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
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:14 | linux | before 7.1.12-1 | 7.1.12-1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-default | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-docs | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-ec2 | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-source | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-syms | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-trace | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-xen | before 3.0.101-108.223.1 | 3.0.101-108.223.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80776Sep 4, 2026 · futex: Fix race in futex_pivot_pending() during private hash resize0Monitor
- ← EarlierCVE-2026-80784Sep 4, 2026 · mptcp: pm: fix memory leak from alloc-during-teardown race0Monitor
- Later →CVE-2026-80820Sep 4, 2026 · xfs: don't livelock in scrub on a circular unlinked list0Monitor
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 | 061db6b7a910b8378f3b2df64f8c0a3ddc6e85f2 | Vendor (CNA) |
| Linux Linux | 26135631ed8e487bc6aef70cc41934e258d09bbe | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.161.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 7.1.12-1 · Debian:14 | Package registry (OSV) |
| suse:kernel-default | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-docs | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-ec2 | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-source | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-syms | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-trace | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-xen | 3.0.101-108.223.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.