PatchSiren cyber security CVE debrief
CVE-2025-71197 Linux CVE debrief
A buffer overflow vulnerability was found in the Linux kernel's w1: therm: alarms_store function. The issue arises from an off-by-one error when allocating memory for the sysfs buffer, leading to a potential buffer overflow when copying data using strcpy(). This vulnerability affects Linux kernel users and distributors, particularly those using the w1: therm module. The vulnerability has a high defensive priority, and users should apply patches or updates to mitigate the issue. The CVE record was published on 2026-02-04T17:16:11.633Z, and the NVD entry is currently Deferred.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-14
- Original CVE updated
- 2026-07-28
- Advisory published
- 2026-07-14
- Advisory updated
- 2026-07-28
Who should care
Linux kernel users and distributors, particularly those using the w1: therm module, should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and updating Linux kernel configurations to disable or restrict access to the w1: therm module if not needed, monitoring system logs for potential exploitation attempts, and applying patches or updates to a fixed version of the Linux kernel.
Technical summary
The vulnerability is caused by an off-by-one error in the allocation of the sysfs buffer in the alarms_store function. The buffer is allocated with 'size + 1' bytes, but the 'size' argument does not account for the extra byte. When strcpy() is used to copy 'buf' into the allocated buffer, it writes one byte past the allocated buffer, resulting in a buffer overflow. The fix involves parsing the 'buf' parameter directly using simple_strtoll() without allocating intermediate memory or using string copying.
Defensive priority
High
Recommended defensive actions
- Apply the official patch or update to a fixed version of the Linux kernel
- Review and update Linux kernel configurations to disable or restrict access to the w1: therm module if not needed
- Monitor system logs for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record was published on 2026-02-04T17:16:11.633Z and last modified on 2026-07-14T13:18:05.637Z. The NVD entry is currently Deferred. Linux kernel users should verify their systems for the w1: therm module and assess potential exposure. Evidence is limited, and defenders should focus on applying patches or mitigations. Additional verification tasks include reviewing system logs for potential exploitation attempts and ensuring that Linux kernel configurations are updated to disable or restrict access to the w1: therm module if not needed.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-71197 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-71197
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-71197 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-71197
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/060b08d72a38b158a7f850d4b83c17c2969e0f6b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/49ff9b4b9deacbefa6654a0a2bcaf910c9de7e95
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6a5820ecfa5a76c3d3e154802c8c15f391ef442e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6fd6d2a8e41b7f544a4d26cbd60bedf9c67893a0
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/761fcf46a1bd797bd32d23f3ea0141ffd437668a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b3fc3e1f04dcc7c41787bbf08a6e0d2728e022cf
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e6b2609af21b5cccc9559339591b8a2cbf884169
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.