Skip to main content

Linux Kernel EUVDEUVD-2026-80542

| CVE-2026-89942 HIGH
2026-09-16 Linux GHSA-3g64-jv43-3qjf
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.3 MEDIUM

Local device access (AV:L, PR:L); teardown timing race raises AC to H; impact is a UAF crash (A:H), with no disclosure (C:N) and only incidental memory corruption (I:L).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

7
Metadata Corrected
Sep 16, 2026 - 16:40 vuln.today
tag: Denial Of Service added
Metadata Corrected
Sep 16, 2026 - 16:40 vuln.today
tag: Information Disclosure removed
Analysis Generated
Sep 16, 2026 - 16:05 vuln.today
CVSS changed
Sep 16, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Sep 16, 2026 - 11:03 EUVD
CVE Published
Sep 16, 2026 - 10:32 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 16, 2026 - 10:32 cve.org
HIGH 7.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

iio: buffer: Fix potential use-after-free in anonymous buffer release

An anonymous buffer handle holds a reference to the underlying IIO device. The reference is dropped in the buffer handle's release function. If the device has been removed, either through unbind or hot-unplug, the buffer handle might hold the last reference.

The release function takes the mutex for the buffer using a guard, which means the unlock happens after all the code in the function, including iio_device_put(). If the anonymous buffer holds the last reference this might free both the IIO device and the buffer, which contains the mutex, leading to use-after-free when the mutex is unlocked.

Fix this by using a scoped guard just around the buffer dmabuf list access, making sure the mutex is unlocked before releasing the IIO device.

Version 10 of the patch that introduced this issue used this exact scheme of first unlocking and then dropping the reference [1]. During review it was suggested to use a guard instead, and version 11 made that change [2].

AnalysisAI

A local use-after-free in the Linux kernel's Industrial I/O (IIO) subsystem can crash or corrupt the kernel when an anonymous IIO buffer handle is released while its underlying IIO device is being torn down at the same time. Only kernels built with the anonymous/DMABUF buffer interface introduced in 6.11 are affected, and the vendor-scored 7.8 severity is not supported by the evidence: exploitation requires local low-privileged access (CVSS PR:L), a narrow race with driver unbind or hot-unplug (AC:H), and results in denial of service (kernel memory corruption/crash) rather than the high confidentiality and integrity impact the vendor vector claims. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitation requires local access to a system with an IIO (Industrial I/O) device that exposes the anonymous buffer interface, and the ability to open a buffer handle on it. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The vendor CVSS is 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), but the signals do not support that severity. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Apply the vendor-released patches: update to Linux 6.12.110, 6.18.51, 7.2.5 or 7.3-rc1 (or newer) as appropriate for your branch, or cherry-pick the upstream stable fixes at https://git.kernel.org/stable/c/6288b593e76eb10329326f2cd51e32557203b9e5, https://git.kernel.org/stable/c/ab53077511cde811bf3ee219426c522329c41226, https://git.kernel.org/stable/c/6d4bdbf7bad63e759bf20259c527f69a1209e3dd and https://git.kernel.org/stable/c/f1f8f0e8e0af9cae8150658dc7bb51332f984893; the upstream commit restores the correct ordering by scoping the buffer mutex guard to only the dmabuf list access, so the mutex is unlocked before iio_device_put(). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, inventory Linux hosts and identify systems running kernels 6.11 or later built with the IIO anonymous/DMABUF buffer interface, prioritizing embedded, industrial, sensor-gateway, and multi-tenant hosts; restrict local interactive and container access on unpatched systems to trusted operators. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-80542 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy