CVE-2025-21976 Details
Description
In the Linux kernel, the following vulnerability has been resolved: fbdev: hyperv_fb: Allow graceful removal of framebuffer When a Hyper-V framebuffer device is unbind, hyperv_fb driver tries to release the framebuffer forcefully. If this framebuffer is in use it produce the following WARN and hence this framebuffer is never released. [ 44.111220] WARNING: CPU: 35 PID: 1882 at drivers/video/fbdev/core/fb_info.c:70 framebuffer_release+0x2c/0x40 < snip > [ 44.111289] Call Trace: [ 44.111290] <TASK> [ 44.111291] ? show_regs+0x6c/0x80 [ 44.111295] ? __warn+0x8d/0x150 [ 44.111298] ? framebuffer_release+0x2c/0x40 [ 44.111300] ? report_bug+0x182/0x1b0 [ 44.111303] ? handle_bug+0x6e/0xb0 [ 44.111306] ? exc_invalid_op+0x18/0x80 [ 44.111308] ? asm_exc_invalid_op+0x1b/0x20 [ 44.111311] ? framebuffer_release+0x2c/0x40 [ 44.111313] ? hvfb_remove+0x86/0xa0 [hyperv_fb] [ 44.111315] vmbus_remove+0x24/0x40 [hv_vmbus] [ 44.111323] device_remove+0x40/0x80 [ 44.111325] device_release_driver_internal+0x20b/0x270 [ 44.111327] ? bus_find_device+0xb3/0xf0 Fix this by moving the release of framebuffer and assosiated memory to fb_ops.fb_destroy function, so that framebuffer framework handles it gracefully. While we fix this, also replace manual registrations/unregistration of framebuffer with devm_register_framebuffer.
A vulnerability in the Linux kernel's Hyper-V framebuffer driver can lead to improper handling during the removal of a framebuffer device. When the device is unbound, the driver attempts to forcefully release the framebuffer. If the framebuffer is currently in use, this action triggers a warning and prevents the framebuffer from being released properly. The issue arises because the release process does not account for the framebuffer's usage, leading to a potential resource management problem.
The vulnerability has been addressed by modifying the framebuffer release process to allow for a more graceful removal. Users should ensure they are using a version of the Linux kernel that includes this fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 15, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/4545e2aa121aea304d33903099c03e29ed4fe50a | kernel.org | Patch |
| https://git.kernel.org/stable/c/a7b583dc99c6cf4a96877017be1d08247e1ef2c7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b1a86a5ab0d44160534f495a3630646092d98e27 | kernel.org | |
| https://git.kernel.org/stable/c/ea2f45ab0e53b255f72c85ccd99e2b394fc5fceb | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 3.10, < 6.12.20 >= 6.13, < 6.13.8 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc4 6.14 rc5 6.14 rc6 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 21, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | CISA-ADP |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 30, 2025 | Initial Analysis | [email protected] |
| Apr 1, 2025 | New CVE Received | kernel.org |