LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71197: w1: therm: Fix off-by-one buffer overflow in alarms_store

In the Linux kernel, the following vulnerability has been resolved: w1: therm: Fix off-by-one buffer overflow in alarms_store The sysfs buffer passed to alarms_store() is allocated with 'size + 1' bytes and a NUL terminator is appended. However, the 'size' argument does not account for this extra byte. The original code then allocated 'size' bytes and used strcpy() to copy 'buf', which always writes one byte past the allocated buffer since strcpy() copies until the NUL terminator at index 'size'. Fix this by parsing the 'buf' parameter directly using simple_strtoll() without allocating any intermediate memory or string copying. This removes the overflow while simplifying the code.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-71197 is a Linux kernel bug in the 1-Wire thermal sensor driver. A sysfs write path copied a NUL-terminated buffer into an allocation that was one byte too small, causing an off-by-one overflow. Business risk depends on whether exposed systems run affected kernels and use this driver path.

Executive priority

Prioritize asset identification and vendor patch tracking, especially for embedded, appliance, or Siemens-managed environments. Do not treat this as internet-scale urgent without evidence of exposure or exploitation.

Technical view

The flaw is in w1 therm alarms_store(). The source states sysfs provides size+1 bytes with a terminator, but the old code allocated size bytes and used strcpy(), writing one byte past the allocation. Stable kernel commits fix this by parsing the sysfs buffer directly with simple_strtoll() and avoiding the copy.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions where the w1 therm driver and relevant sysfs alarm attribute are present. The bundle also cites a Siemens advisory, so embedded or industrial products using Linux should be checked against vendor guidance.

Exploitation context

The bundle does not cite active exploitation, public exploit code, KEV listing, privilege requirements, or practical impact beyond the kernel buffer overflow. Treat exploitation status as unconfirmed and validate exposure before escalating broadly.

Researcher notes

The key research gap is impact. The source confirms memory corruption but does not establish attacker reachability, required permissions, exploitability, or resulting consequences. Focus triage on driver presence, sysfs write permissions, and vendor backport status.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Review the Siemens advisory for affected industrial products.
  • Limit write access to relevant sysfs interfaces where operationally feasible.
  • Track vendor guidance because no CVSS score is provided.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Compare deployed kernels against the CVE affected version data.
  • Confirm whether the w1 therm driver is present or loaded.
  • Check for relevant sysfs alarm attributes on exposed systems.
  • Verify vendor packages include one of the referenced stable fixes.
Prepared
Confidence
medium
Sources
10

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-71197 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
1ADP providers
9Source 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.

ADP provider summaries

siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe2c94d6f572079511945e64537eb1218643f2e68, e2c94d6f572079511945e64537eb1218643f2e68, e2c94d6f572079511945e64537eb1218643f2e68, e2c94d6f572079511945e64537eb1218643f2e68, e2c94d6f572079511945e64537eb1218643f2e68, e2c94d6f572079511945e64537eb1218643f2e68, e2c94d6f572079511945e64537eb1218643f2e68unaffected
LinuxLinux5.8, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

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