Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72265: fbdev: nvidia: fix potential memory leak in nvidiafb_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.22% (FIRST EPSS).
  • Fixed version: Linux Linux 009a8514745b16c468acc25aa00539abbf38e1b5, 2515cd60f6b5ad680ed164aa6bd19b05270af34c, 508704de34fb8c0dcbbf13397212363bbf0974de.

Low priority for now. Upgrade to Linux Linux 009a8514745b16c468acc25aa00539abbf38e1b5, 2515cd60f6b5ad680ed164aa6bd19b05270af34c, 508704de34fb8c0dcbbf13397212363bbf0974de 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: nvidia: fix potential memory leak in nvidiafb_probe() In nvidiafb_probe(), the memory allocated for modelist in nvidia_set_fbinfo() is not freed in the subsequent error paths. Fix that by calling fb_destroy_modelist().

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2026-72265

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7e747f7b17ccce750502fd4d0b4e866fe4f066a6affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2515cd60f6b5ad680ed164aa6bd19b05270af34caffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 508704de34fb8c0dcbbf13397212363bbf0974deaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6ca48f23ce61a26349d7d084fb63b70499137c8eaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e8172773e5251f4df2eed74caab6ca3195fed1eaaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 009a8514745b16c468acc25aa00539abbf38e1b5affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ed3b3eb212441fb5f287dfd24ebafe11d634f009affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 85f5e38c162bdf9dbbe197275d416402712f3707affected · git
    • before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72263Aug 15, 2026 · ASoC: SOF: topology: fix memory leak in snd_sof_load_topology
    0Monitor
  • ← EarlierCVE-2026-72264Aug 15, 2026 · fbdev: tridentfb: fix potential memory leak in trident_pci_probe()
    0Monitor
  • Later →CVE-2026-72266Aug 15, 2026 · fbdev: vesafb: fix memory leak in vesafb_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 / packageFixed versionSource
Linux Linux009a8514745b16c468acc25aa00539abbf38e1b5Vendor (CNA)
Linux Linux2515cd60f6b5ad680ed164aa6bd19b05270af34cVendor (CNA)
Linux Linux508704de34fb8c0dcbbf13397212363bbf0974deVendor (CNA)
Linux Linux6ca48f23ce61a26349d7d084fb63b70499137c8eVendor (CNA)
Linux Linux7e747f7b17ccce750502fd4d0b4e866fe4f066a6Vendor (CNA)
Linux Linux85f5e38c162bdf9dbbe197275d416402712f3707Vendor (CNA)
Linux Linuxe8172773e5251f4df2eed74caab6ca3195fed1eaVendor (CNA)
Linux Linuxed3b3eb212441fb5f287dfd24ebafe11d634f009Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package 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.

EPSS, last 120 days

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 researchers

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records