CVE-2025-38702: fbdev: fix potential buffer overflow in do_register_framebuffer()
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.19% (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 248b2aab9b2af5ecf89d9d7955a2ff20c4b4a399, 2828a433c7d7a05b6f27c8148502095101dd0b09, 523b84dc7ccea9c4d79126d6ed1cf9033cf83b05; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 248b2aab9b2af5ecf89d9d7955a2ff20c4b4a399, 2828a433c7d7a05b6f27c8148502095101dd0b09, 523b84dc7ccea9c4d79126d6ed1cf9033cf83b05; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 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: 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.
- Published
- Sep 4, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-787
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%
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel6.2 and later · before 6.6.103
- linux linux kernel6.7 and later · before 6.12.43
- linux linux kernel2.6.12.1 and later · before 6.1.149
- linux linux kernel6.16 and later · before 6.16.2
- linux linux kernel6.13 and later · before 6.15.11
- linux linux kernel2.6.12
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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5c3f5a25c62230b7965804ce7a2e9305c3ca3961affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before cbe740de32bb0fb7a5213731ff5f26ea6718fca3affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 806f85bdd3a60187c21437fc51baace11f659f35affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2828a433c7d7a05b6f27c8148502095101dd0b09affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 248b2aab9b2af5ecf89d9d7955a2ff20c4b4a399affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 523b84dc7ccea9c4d79126d6ed1cf9033cf83b05affected · git
- before 2.6.12not affected · semver
- 6.1.149 and later · up to and including 6.1.*not affected · semver
- 6.6.103 and later · up to and including 6.6.*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.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.43-1 | 6.12.43-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38700Sep 4, 2025 · scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated22Monitor
- ← EarlierCVE-2025-38701Sep 4, 2025 · ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr22Monitor
- Later →CVE-2025-38703Sep 4, 2025 · drm/xe: Make dma-fences compliant with the safe access rules31Monitor
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 | 248b2aab9b2af5ecf89d9d7955a2ff20c4b4a399 | Vendor (CNA) |
| Linux Linux | 2828a433c7d7a05b6f27c8148502095101dd0b09 | Vendor (CNA) |
| Linux Linux | 523b84dc7ccea9c4d79126d6ed1cf9033cf83b05 | Vendor (CNA) |
| Linux Linux | 5c3f5a25c62230b7965804ce7a2e9305c3ca3961 | Vendor (CNA) |
| Linux Linux | 806f85bdd3a60187c21437fc51baace11f659f35 | Vendor (CNA) |
| Linux Linux | cbe740de32bb0fb7a5213731ff5f26ea6718fca3 | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.153-1 · 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.
No history yet (it accumulates with the daily EPSS job).
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).
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)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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 (8 more)Show less
- git.kernel.org/stable/c/2828a433c7d7a05b6f27c8148502095101dd0b09
- git.kernel.org/stable/c/523b84dc7ccea9c4d79126d6ed1cf9033cf83b05
- git.kernel.org/stable/c/5c3f5a25c62230b7965804ce7a2e9305c3ca3961
- git.kernel.org/stable/c/806f85bdd3a60187c21437fc51baace11f659f35
- git.kernel.org/stable/c/cbe740de32bb0fb7a5213731ff5f26ea6718fca3
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- cert-portal.siemens.com/productcert/html/ssa-032379.html
- cert-portal.siemens.com/productcert/html/ssa-082556.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.