CVE-2026-89585: auxdisplay: charlcd: cancel backlight work on registration failure
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.16% (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 22586432c1aba89d9bd33f3173408dac830f220b, 6eaed64a32e550daf0dc9549742b3ab9e41d984f, 84858671842ae5857b9ed1202b62f9045373dcd1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 22586432c1aba89d9bd33f3173408dac830f220b, 6eaed64a32e550daf0dc9549742b3ab9e41d984f, 84858671842ae5857b9ed1202b62f9045373dcd1 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: auxdisplay: charlcd: cancel backlight work on registration failure With CONFIG_CHARLCD_BL_FLASH, charlcd_init() schedules bl_work before charlcd_register() calls misc_register(). If registration fails, the caller frees the charlcd object while delayed work still contains its address. Add charlcd_deinit() to cancel the delayed work and turn the backlight off. Use it for both registration rollback and normal unregistration.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- 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.12affected
- 39f8ea46724efbed3ca021863a22337c31be264c and later · before cd97b3c68fe3c06c8067cc59d7dff976c5b7ea04affected · git
- 39f8ea46724efbed3ca021863a22337c31be264c and later · before 22586432c1aba89d9bd33f3173408dac830f220baffected · git
- 39f8ea46724efbed3ca021863a22337c31be264c and later · before 6eaed64a32e550daf0dc9549742b3ab9e41d984faffected · git
- 39f8ea46724efbed3ca021863a22337c31be264c and later · before fe7ba73dde94c5f413b1588cd444b49105015ddaaffected · git
- 39f8ea46724efbed3ca021863a22337c31be264c and later · before 84858671842ae5857b9ed1202b62f9045373dcd1affected · git
- 39f8ea46724efbed3ca021863a22337c31be264c and later · before ff2fb3c1e60cb247ea3e28c0ea0bea81c18f7755affected · git
- 39f8ea46724efbed3ca021863a22337c31be264c and later · before e3e3bf40916c1e810df03958cfa7ba6883cdce79affected · git
- before 4.12not affected · semver
- 5.15.221 and later · up to and including 5.15.*not 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-89583Sep 11, 2026 · Bluetooth: eir: Fix OOB read in eir_get_service_data()32Monitor
- ← EarlierCVE-2026-89584Sep 11, 2026 · block: validate user space vectors during extraction31Monitor
- Later →CVE-2026-89586Sep 11, 2026 · ata: libata-scsi: fix DSM TRIM for sector sizes larger than 2048 bytes32Monitor
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 | 22586432c1aba89d9bd33f3173408dac830f220b | Vendor (CNA) |
| Linux Linux | 6eaed64a32e550daf0dc9549742b3ab9e41d984f | Vendor (CNA) |
| Linux Linux | 84858671842ae5857b9ed1202b62f9045373dcd1 | Vendor (CNA) |
| Linux Linux | cd97b3c68fe3c06c8067cc59d7dff976c5b7ea04 | Vendor (CNA) |
| Linux Linux | e3e3bf40916c1e810df03958cfa7ba6883cdce79 | Vendor (CNA) |
| Linux Linux | fe7ba73dde94c5f413b1588cd444b49105015dda | Vendor (CNA) |
| Linux Linux | ff2fb3c1e60cb247ea3e28c0ea0bea81c18f7755 | 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.
- 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)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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 (6 more)Show less
- git.kernel.org/stable/c/6eaed64a32e550daf0dc9549742b3ab9e41d984f
- git.kernel.org/stable/c/84858671842ae5857b9ed1202b62f9045373dcd1
- git.kernel.org/stable/c/cd97b3c68fe3c06c8067cc59d7dff976c5b7ea04
- git.kernel.org/stable/c/e3e3bf40916c1e810df03958cfa7ba6883cdce79
- git.kernel.org/stable/c/fe7ba73dde94c5f413b1588cd444b49105015dda
- git.kernel.org/stable/c/ff2fb3c1e60cb247ea3e28c0ea0bea81c18f7755
Vendor advisories and official records. Exploit/PoC links are deliberately left out.