CVE-2026-89599: fbdev: omapfb: panel-dsi-cm: initialize lock before registering display
Noroxi assessment
Priority: Monitor (action score 33/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.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 09db79078f25c048cfb5d7849795c70415ab8574, 2c3f8c9c995db185284b079f39177e85b2258176, 302d19fbc7dc7e9f498930c66d65ff711ba5ba9f.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 09db79078f25c048cfb5d7849795c70415ab8574, 2c3f8c9c995db185284b079f39177e85b2258176, 302d19fbc7dc7e9f498930c66d65ff711ba5ba9f 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: omapfb: panel-dsi-cm: initialize lock before registering display dsicm_probe() registers the display before initializing ddata->lock. Once omapdss_register_display() publishes the display, another consumer can reach a dsicm callback that takes this mutex while it is still uninitialized. Initialize the mutex before registering the display so the published callbacks always see a valid lock.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 4.5affected
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before ef20d4e17d7fb0d83144caa9667e6f3198288993affected · git
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before e7023d18c4eb292f886b31a3576402cb0e357df7affected · git
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before f33a96e49284589257e90ddc4394ec0c6bf11ec4affected · git
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before 302d19fbc7dc7e9f498930c66d65ff711ba5ba9faffected · git
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before 2c3f8c9c995db185284b079f39177e85b2258176affected · git
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before 76818e81cfcae33b09b739de09162c7d8d89bf0baffected · git
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before 09db79078f25c048cfb5d7849795c70415ab8574affected · git
- f76ee892a99e68b55402b8d4b8aeffcae2aff34d and later · before f8e43fe0f22b7137ce456e6fe3581d3098174f74affected · git
- before 4.5not affected · semver
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 | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-89597Sep 11, 2026 · fbdev: uvesafb: unregister connector callback on init failure31Monitor
- ← EarlierCVE-2026-89598Sep 11, 2026 · fbdev: ssd1307fb: defer I2C transfers from damage callbacks0Monitor
- Later →CVE-2026-89600Sep 11, 2026 · fanotify: fix use-after-free of file range info31Monitor
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 | 09db79078f25c048cfb5d7849795c70415ab8574 | Vendor (CNA) |
| Linux Linux | 2c3f8c9c995db185284b079f39177e85b2258176 | Vendor (CNA) |
| Linux Linux | 302d19fbc7dc7e9f498930c66d65ff711ba5ba9f | Vendor (CNA) |
| Linux Linux | 76818e81cfcae33b09b739de09162c7d8d89bf0b | Vendor (CNA) |
| Linux Linux | e7023d18c4eb292f886b31a3576402cb0e357df7 | Vendor (CNA) |
| Linux Linux | ef20d4e17d7fb0d83144caa9667e6f3198288993 | Vendor (CNA) |
| Linux Linux | f33a96e49284589257e90ddc4394ec0c6bf11ec4 | Vendor (CNA) |
| Linux Linux | f8e43fe0f22b7137ce456e6fe3581d3098174f74 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | 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).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2c3f8c9c995db185284b079f39177e85b2258176
- git.kernel.org/stable/c/302d19fbc7dc7e9f498930c66d65ff711ba5ba9f
- git.kernel.org/stable/c/76818e81cfcae33b09b739de09162c7d8d89bf0b
- git.kernel.org/stable/c/e7023d18c4eb292f886b31a3576402cb0e357df7
- git.kernel.org/stable/c/ef20d4e17d7fb0d83144caa9667e6f3198288993
- git.kernel.org/stable/c/f33a96e49284589257e90ddc4394ec0c6bf11ec4
- git.kernel.org/stable/c/f8e43fe0f22b7137ce456e6fe3581d3098174f74
Vendor advisories and official records. Exploit/PoC links are deliberately left out.