LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22082: iio: backend: make sure to NULL terminate stack buffer

In the Linux kernel, the following vulnerability has been resolved: iio: backend: make sure to NULL terminate stack buffer Make sure to NULL terminate the buffer in iio_backend_debugfs_write_reg() before passing it to sscanf(). It is a stack variable so we should not assume it will 0 initialized.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-22082 is a Linux kernel bug in the Industrial I/O backend debugfs register-write path. A stack buffer was passed to sscanf() without guaranteed null termination. The public record does not provide CVSS, impact details, or confirmed exploitation, so urgency depends on whether affected kernels expose this debugfs path.

Executive priority

Treat as a targeted Linux kernel maintenance issue until vendor advisories clarify impact. Patch through normal kernel update channels, with faster action for systems using IIO hardware, diagnostics, or exposed debugfs access.

Technical view

The fix null-terminates the stack buffer in iio_backend_debugfs_write_reg() before parsing it with sscanf(). The issue is in the Linux kernel IIO backend debugfs code. The source bundle lists Linux 6.12-era affected versions and stable kernel commits addressing the flaw.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the relevant IIO backend debugfs interface present and reachable by a permitted local user. The bundle does not identify specific distributions, devices, default configurations, or remote exposure.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not claim active exploitation or provide exploitation evidence. The available facts support a local kernel debugfs parsing flaw, but not weaponization, privilege impact, or reliability claims.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed impact is provided. The central behavior is missing null termination of a stack buffer before sscanf() in iio_backend_debugfs_write_reg(). Avoid assuming privilege escalation or information disclosure without vendor confirmation.

Mitigation direction

  • Update to vendor kernel packages containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes and affected package versions.
  • Restrict access to debugfs on systems where it is not operationally required.
  • Prioritize systems using Industrial I/O hardware or diagnostics on affected kernels.

Validation and detection

  • Inventory kernel versions and compare against vendor advisories for CVE-2025-22082.
  • Confirm whether debugfs is enabled and accessible on candidate systems.
  • Check for the referenced stable fix commits in deployed kernel source or changelog.
  • Verify IIO backend debugfs functionality is not exposed beyond intended administrators.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22082 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcdf01e0809a4c6c7877ea52401c2a6679df7aed6, cdf01e0809a4c6c7877ea52401c2a6679df7aed6, cdf01e0809a4c6c7877ea52401c2a6679df7aed6, cdf01e0809a4c6c7877ea52401c2a6679df7aed6unaffected
LinuxLinux6.12, 0, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.