Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72077: Input: ims-pcu - fix firmware leak in async update

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 1f7bdfbe791aacad77db87f044e78ef60a93ae0d, 47a9889a9325b87698b6d6eaf3187a9af6e4773d, 99c428d7ef644d3e394f3072f905040c16dab18d.

Low priority for now. Upgrade to Linux Linux 1f7bdfbe791aacad77db87f044e78ef60a93ae0d, 47a9889a9325b87698b6d6eaf3187a9af6e4773d, 99c428d7ef644d3e394f3072f905040c16dab18d 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: Input: ims-pcu - fix firmware leak in async update The firmware object was not being released if validation failed. Use __free(firmware) to ensure the firmware is always released.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 23, 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-72077

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

    • 3.10affected
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before f4b8cd2a96b47473e912e8a134f3c59efb81f10faffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 9efba5177a51ed996b0bdc03aa677c08247d5b91affected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before af0641337f6584ccbc7a42ce3f4803d8ff9c5a4aaffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before a5dd47ea3904dedb1ae7a5fe0e6b44a458f0c5ecaffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 1f7bdfbe791aacad77db87f044e78ef60a93ae0daffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 99c428d7ef644d3e394f3072f905040c16dab18daffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 47a9889a9325b87698b6d6eaf3187a9af6e4773daffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before d48795b5cd6828d36b707e8d62fc9e5c90e004abaffected · git
    • before 3.10not 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.187-16.1.187-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-72075Aug 15, 2026 · Input: ims-pcu - fix race condition in reset_device sysfs callback
    0Monitor
  • ← EarlierCVE-2026-72076Aug 15, 2026 · Input: ims-pcu - fix out-of-bounds read in ims_pcu_irq() debug logging
    0Monitor
  • Later →CVE-2026-72078Aug 15, 2026 · Input: ims-pcu - validate control endpoint type
    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 Linux1f7bdfbe791aacad77db87f044e78ef60a93ae0dVendor (CNA)
Linux Linux47a9889a9325b87698b6d6eaf3187a9af6e4773dVendor (CNA)
Linux Linux99c428d7ef644d3e394f3072f905040c16dab18dVendor (CNA)
Linux Linux9efba5177a51ed996b0bdc03aa677c08247d5b91Vendor (CNA)
Linux Linuxa5dd47ea3904dedb1ae7a5fe0e6b44a458f0c5ecVendor (CNA)
Linux Linuxaf0641337f6584ccbc7a42ce3f4803d8ff9c5a4aVendor (CNA)
Linux Linuxd48795b5cd6828d36b707e8d62fc9e5c90e004abVendor (CNA)
Linux Linuxf4b8cd2a96b47473e912e8a134f3c59efb81f10fVendor (CNA)
debian:linux6.1.187-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