Linux Kernel up to 6.16.1 fbdev do_register_framebuffer registered_fb[] buffer overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.1.148/6.6.102/6.12.42/6.15.10/6.16.1. It has been classified as critical. Affected by this issue is the function do_register_framebuffer of the component fbdev. The manipulation of the argument registered_fb[] leads to buffer overflow.
This vulnerability is referenced as CVE-2025-38702. No exploit is available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Linux Kernel up to 6.1.148/6.6.102/6.12.42/6.15.10/6.16.1 and classified as critical. This issue affects the function do_register_framebuffer of the component fbdev. The manipulation of the argument registered_fb[] with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: fbdev: fix potential buffer overflow in do_register_framebuffer() The current implementation may lead to buffer overflow when: 1. Unregistration creates NULL gaps in registered_fb[] 2. All array slots become occupied despite num_registered_fb < FB_MAX 3. The registration loop exceeds array bounds Add boundary check to prevent registered_fb[FB_MAX] access.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-38702 since 04/16/2025. The exploitation is known to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/10/2026).
The vulnerability scanner Nessus provides a plugin with the ID 261571 (Linux Distros Unpatched Vulnerability : CVE-2025-38702), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2 or 6.17-rc1 eliminates this vulnerability. Applying the patch 5c3f5a25c62230b7965804ce7a2e9305c3ca3961/cbe740de32bb0fb7a5213731ff5f26ea6718fca3/806f85bdd3a60187c21437fc51baace11f659f35/2828a433c7d7a05b6f27c8148502095101dd0b09/248b2aab9b2af5ecf89d9d7955a2ff20c4b4a399/523b84dc7ccea9c4d79126d6ed1cf9033cf83b05 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (261571) and CERT Bund (WID-SEC-2025-1976). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Open Source Linux Kernel
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- RESF Rocky Linux
- Microsoft Azure
- Dell Secure Connect Gateway
- IBM QRadar SIEM
- IBM Security Verify Access
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 6.1.148
- 6.6.102
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.15.0
- 6.15.1
- 6.15.2
- 6.15.3
- 6.15.4
- 6.15.5
- 6.15.6
- 6.15.7
- 6.15.8
- 6.15.9
- 6.15.10
- 6.16.0
- 6.16.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.7
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 261571
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-38702
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.1.149/6.6.103/6.12.43/6.15.11/6.16.2/6.17-rc1
Patch: 5c3f5a25c62230b7965804ce7a2e9305c3ca3961/cbe740de32bb0fb7a5213731ff5f26ea6718fca3/806f85bdd3a60187c21437fc51baace11f659f35/2828a433c7d7a05b6f27c8148502095101dd0b09/248b2aab9b2af5ecf89d9d7955a2ff20c4b4a399/523b84dc7ccea9c4d79126d6ed1cf9033cf83b05
Timeline
04/16/2025 CVE reserved09/04/2025 Advisory disclosed
09/04/2025 VulDB entry created
02/10/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-38702 (🔒)
GCVE (CVE): GCVE-0-2025-38702
GCVE (VulDB): GCVE-100-322565
CERT Bund: WID-SEC-2025-1976 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 09/04/2025 18:31Updated: 02/10/2026 06:48
Changes: 09/04/2025 18:31 (60), 09/05/2025 18:23 (7), 09/07/2025 21:37 (2), 10/08/2025 17:55 (1), 12/09/2025 17:52 (1), 01/15/2026 00:47 (1), 01/24/2026 10:32 (11), 02/10/2026 06:48 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.