Unknown

CVE-2026-80595 — Input: ims-pcu - add response length checks

In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - add response length checks The driver processes response data from device buffers without verifying that the device actually sent enough data. This can lead to out-of-bounds reads or processing stale data. Add checks for the expected response length before accessing the buffers.

Published Aug 28, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.22%

ahead of 12% of scored CVEs · Oct 27, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 628329d52474323938a03826941e166bc7c8eff4 and < bbafb75cd9da50d86335cbd98b8b3492bb5e42a6≥ 628329d52474323938a03826941e166bc7c8eff4 and < 3e0e8d7f8139a9496e389e7372e3f8b57b3e4e3e≥ 628329d52474323938a03826941e166bc7c8eff4 and < 89cf4d18ff87efa5c47ba38de36aea5c03f98b05≥ 628329d52474323938a03826941e166bc7c8eff4 and < f7f5afeed31baaca0b027c2d46a25ee86fb4c9da≥ 628329d52474323938a03826941e166bc7c8eff4 and < dc9fdb538ce5b7f32540991f4a25ab63fab7ba07≥ 628329d52474323938a03826941e166bc7c8eff4 and < f28c5cabb2df09ad1fcfb7cdb2b3ed2f690d81f0≥ 628329d52474323938a03826941e166bc7c8eff4 and < f3c63aecca90be42b66cdc66de7c4a6104104d17≥ 628329d52474323938a03826941e166bc7c8eff4 and < 48c9d92fd4ee3a8f5d2cb46c802a0eff8e67c79c and 1 more version 3.10	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.22%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 28, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/3e0e8d7f8139a9496e389e7372e3f8b57b3e4e3e
NIST National Vulnerability Database
git.kernel.org/stable/c/dc9fdb538ce5b7f32540991f4a25ab63fab7ba07
NIST National Vulnerability Database
git.kernel.org/stable/c/48c9d92fd4ee3a8f5d2cb46c802a0eff8e67c79c
NIST National Vulnerability Database
git.kernel.org/stable/c/89cf4d18ff87efa5c47ba38de36aea5c03f98b05
NIST National Vulnerability Database
git.kernel.org/stable/c/bbafb75cd9da50d86335cbd98b8b3492bb5e42a6
NIST National Vulnerability Database
git.kernel.org/stable/c/f28c5cabb2df09ad1fcfb7cdb2b3ed2f690d81f0
NIST National Vulnerability Database
git.kernel.org/stable/c/f3c63aecca90be42b66cdc66de7c4a6104104d17
NIST National Vulnerability Database
git.kernel.org/stable/c/f7f5afeed31baaca0b027c2d46a25ee86fb4c9da
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 16h
Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 16h
Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 16h
Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 16h
Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 16h
Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 16h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80595 is "Input: ims-pcu - add response length checks", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.