CVE-2026-72275: fbdev: broadsheetfb: fix potential memory leak in broadsheetfb_probe()
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 07d2f9cb667c2f6331a483227c62d0a4a91ef42f, 4ce94f9e3bfb37866638e4b81e2c3d8f7470a12c, 5.15.212.
Low priority for now. Upgrade to Linux Linux 07d2f9cb667c2f6331a483227c62d0a4a91ef42f, 4ce94f9e3bfb37866638e4b81e2c3d8f7470a12c, 5.15.212 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: broadsheetfb: fix potential memory leak in broadsheetfb_probe() The memory allocated for pagerefs in fb_deferred_io_init() is not freed on the error path. Fix it by calling fb_deferred_io_cleanup().
- Published
- Aug 15, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
- 5.19affected
- 186b89659c4c67cccead52961eab0ca3b23951dc and later · before edc5a845108337d0c167ab850fe9adfaea442975affected · git
- 56c134f7f1b58be08bdb0ca8372474a4a5165f31 and later · before 54a4cd11702d5e8bcefc3b514e338955813993a1affected · git
- 56c134f7f1b58be08bdb0ca8372474a4a5165f31 and later · before 4ce94f9e3bfb37866638e4b81e2c3d8f7470a12caffected · git
- 56c134f7f1b58be08bdb0ca8372474a4a5165f31 and later · before 07d2f9cb667c2f6331a483227c62d0a4a91ef42faffected · git
- 56c134f7f1b58be08bdb0ca8372474a4a5165f31 and later · before e8c9aae8c950869f65af8b9dd2f71f861ea6e433affected · git
- 56c134f7f1b58be08bdb0ca8372474a4a5165f31 and later · before e818c397548cde68d64c6abf8be0a5f3e3eef7d1affected · git
- 56c134f7f1b58be08bdb0ca8372474a4a5165f31 and later · before 9d18a4e4234fd3ee0d0eed8ccbbb50cb76b2232caffected · git
- 5.15.149 and later · before 5.15.212affected · semver
- before 5.19not 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-72272Aug 15, 2026 · fbdev: radeon: fix potential memory leak in radeonfb_pci_register()0Monitor
- ← EarlierCVE-2026-72274Aug 15, 2026 · fbdev: hecubafb: fix potential memory leak in hecubafb_probe()0Monitor
- Later →CVE-2026-72276Aug 15, 2026 · fbdev: metronomefb: fix potential memory leak in metronomefb_probe()0Monitor
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 | 07d2f9cb667c2f6331a483227c62d0a4a91ef42f | Vendor (CNA) |
| Linux Linux | 4ce94f9e3bfb37866638e4b81e2c3d8f7470a12c | Vendor (CNA) |
| Linux Linux | 5.15.212 | Vendor (CNA) |
| Linux Linux | 54a4cd11702d5e8bcefc3b514e338955813993a1 | Vendor (CNA) |
| Linux Linux | 9d18a4e4234fd3ee0d0eed8ccbbb50cb76b2232c | Vendor (CNA) |
| Linux Linux | e818c397548cde68d64c6abf8be0a5f3e3eef7d1 | Vendor (CNA) |
| Linux Linux | e8c9aae8c950869f65af8b9dd2f71f861ea6e433 | Vendor (CNA) |
| Linux Linux | edc5a845108337d0c167ab850fe9adfaea442975 | Vendor (CNA) |
| debian:linux | 6.1.180-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.
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).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/4ce94f9e3bfb37866638e4b81e2c3d8f7470a12c
- git.kernel.org/stable/c/54a4cd11702d5e8bcefc3b514e338955813993a1
- git.kernel.org/stable/c/9d18a4e4234fd3ee0d0eed8ccbbb50cb76b2232c
- git.kernel.org/stable/c/e818c397548cde68d64c6abf8be0a5f3e3eef7d1
- git.kernel.org/stable/c/e8c9aae8c950869f65af8b9dd2f71f861ea6e433
- git.kernel.org/stable/c/edc5a845108337d0c167ab850fe9adfaea442975
Vendor advisories and official records. Exploit/PoC links are deliberately left out.