In the Linux kernel, the following vulnerability has been resolved: fbdev: uvesafb: unregister connector callback on init failure uvesafb_init()… (CVE-2026-89597)
A vulnerability in the Linux kernel's uvesafb framebuffer driver was resolved. The issue involved the uvesafb_init() function registering a connector callback before platform driver registration. If platform_driver_register() failed, the callback remained registered, causing a resource cleanup inconsistency. This was fixed by adding proper cleanup on failure. The flaw was found during static analysis and no exploits are known in the wild.
AI Analysis
Technical Summary
The Linux kernel's uvesafb framebuffer driver had a flaw where the v86d connector callback was registered before the platform driver. If platform_driver_register() failed, the function returned an error without unregistering the callback, leaving it registered improperly. This could lead to resource management issues. The fix adds unregistering the connector callback before returning on platform driver registration failure. The vulnerability was discovered via static code analysis.
Potential Impact
The vulnerability causes improper cleanup of the connector callback on platform driver registration failure, potentially leading to resource leaks or inconsistent kernel state. No known exploits or active attacks have been reported. The impact is limited to kernel resource management correctness.
Mitigation Recommendations
A fix has been applied to the Linux kernel source code to unregister the connector callback on platform driver registration failure in uvesafb_init(). Users should update to the fixed kernel version once available. No additional mitigation is required.
In the Linux kernel, the following vulnerability has been resolved: fbdev: uvesafb: unregister connector callback on init failure uvesafb_init()… (CVE-2026-89597)
Description
A vulnerability in the Linux kernel's uvesafb framebuffer driver was resolved. The issue involved the uvesafb_init() function registering a connector callback before platform driver registration. If platform_driver_register() failed, the callback remained registered, causing a resource cleanup inconsistency. This was fixed by adding proper cleanup on failure. The flaw was found during static analysis and no exploits are known in the wild.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's uvesafb framebuffer driver had a flaw where the v86d connector callback was registered before the platform driver. If platform_driver_register() failed, the function returned an error without unregistering the callback, leaving it registered improperly. This could lead to resource management issues. The fix adds unregistering the connector callback before returning on platform driver registration failure. The vulnerability was discovered via static code analysis.
Potential Impact
The vulnerability causes improper cleanup of the connector callback on platform driver registration failure, potentially leading to resource leaks or inconsistent kernel state. No known exploits or active attacks have been reported. The impact is limited to kernel resource management correctness.
Mitigation Recommendations
A fix has been applied to the Linux kernel source code to unregister the connector callback on platform driver registration failure in uvesafb_init(). Users should update to the fixed kernel version once available. No additional mitigation is required.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-4qm2-vqpp-wwm8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89597"]
Threat ID: 6aa4a00d55bf5e2cf5a8668a
Added to database: 09/12/2026, 00:42:53 UTC
Last enriched: 09/12/2026, 01:04:15 UTC
Last updated: 09/12/2026, 01:40:38 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.