Skip to content
Noroxi
CVE-2026-72079· NVD / CVE Program· CNA Linux

Input: ims-pcu - fix use-after-free and double-free in disconnect

In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix use-after-free and double-free in disconnect ims_pcu_disconnect() only intended to perform cleanup when the primary (control) interface is unbound. However, it currently relies on the interface class to distinguish between control and data interfaces. A malicious device could present a data interface with the same class as the control interface, leading to premature cleanup and potential use-after-free or double-free. Switch to verifying that the interface being disconnected is indeed the control interface.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

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%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

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 315f269ea04bc1477ab9bf351e939623d12a1621affected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 293388e42e5c0865204de6f36bfb8662156fce3baffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 921abbb33887052e46b1b77299f87a3c741dc580affected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 6a6c373e6a82eddc522342c8a8db7072c65f2b56affected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before a4b3f4d42fbf58f06f0d49e37a9d0d9392eca338affected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 6aacc18004b1a915ccb8a829d30279a37988066eaffected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before bf0b58ba489d0bdaa18c7dd8beeaeb954dd7dbb7affected · git
    • 628329d52474323938a03826941e166bc7c8eff4 and later · before 462a999917755a3bf77448dfd64307963cf0a9f0affected · 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.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
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

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 Linux293388e42e5c0865204de6f36bfb8662156fce3bVendor (CNA)
Linux Linux315f269ea04bc1477ab9bf351e939623d12a1621Vendor (CNA)
Linux Linux462a999917755a3bf77448dfd64307963cf0a9f0Vendor (CNA)
Linux Linux6a6c373e6a82eddc522342c8a8db7072c65f2b56Vendor (CNA)
Linux Linux6aacc18004b1a915ccb8a829d30279a37988066eVendor (CNA)
Linux Linux921abbb33887052e46b1b77299f87a3c741dc580Vendor (CNA)
Linux Linuxa4b3f4d42fbf58f06f0d49e37a9d0d9392eca338Vendor (CNA)
Linux Linuxbf0b58ba489d0bdaa18c7dd8beeaeb954dd7dbb7Vendor (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

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

All records