CVE-2025-68346

Kernel memory corruption via unchecked FireWire stream count

Published Dec 24, 2025 · Updated Dec 24, 2025

Out-of-bounds write in affected Linux kernel releases allows physically proximate attackers to corrupt kernel memory through a malicious FireWire device. The ALSA DICE detect_stream_formats() function trusts the device-supplied stream_count for both transmit and receive paths and writes past fixed MAX_STREAMS arrays when the count is too large. Reachability requires a crafted FireWire device to be attached and probed by the DICE driver; the published record establishes memory corruption but not code execution.

CVSS severity7.0
High
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds write in affected Linux kernel releases allows physically proximate attackers to corrupt kernel memory through a malicious FireWire device. The ALSA DICE detect_stream_formats() function trusts the device-supplied stream_count for both transmit and receive paths and writes past fixed MAX_STREAMS arrays when the count is too large. Reachability requires a crafted FireWire device to be attached and probed by the DICE driver; the published record establishes memory corruption but not code execution.

The record

CVE
CVE-2025-68346
Published
Dec 24, 2025
Updated
Dec 24, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1200
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 24, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 24, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.18
  2. Affected versionversion=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <1e1b3207a53e50d5a66289fffc1f7d52cd9c50f9
  3. Affected versionversion=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <324f3e03e8a85931ce0880654e3c3eb38b0f0bba
  4. Affected versionversion=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <932aa1e80b022419cf9710e970739b7a8794f27c
  5. Affected versionversion=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <c0a1fe1902ad23e6d48e0f68be1258ccf7a163e6

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=4.18; version=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <1e1b3207a53e50d5a66289fffc1f7d52cd9c50f9; version=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <324f3e03e8a85931ce0880654e3c3eb38b0f0bba; version=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <932aa1e80b022419cf9710e970739b7a8794f27c; version=58579c056c1c9510ae6695ed8e01ee05bbdcfb23 <c0a1fe1902ad23e6d48e0f68be1258ccf7a163e6

Published CVSS scores

7.0Amazon LinuxCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1200Hardware Additions

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo