Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Fixed version: Linux Linux 060b08d72a38b158a7f850d4b83c17c2969e0f6b, 49ff9b4b9deacbefa6654a0a2bcaf910c9de7e95, 6a5820ecfa5a76c3d3e154802c8c15f391ef442e.

Low priority for now. Upgrade to Linux Linux 060b08d72a38b158a7f850d4b83c17c2969e0f6b, 49ff9b4b9deacbefa6654a0a2bcaf910c9de7e95, 6a5820ecfa5a76c3d3e154802c8c15f391ef442e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Feb 4, 2026
Updated
Oct 15, 2026
EPSS
0.2% · 16th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-71197

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.8affected
    • e2c94d6f572079511945e64537eb1218643f2e68 and later · before 49ff9b4b9deacbefa6654a0a2bcaf910c9de7e95affected · git
    • e2c94d6f572079511945e64537eb1218643f2e68 and later · before 060b08d72a38b158a7f850d4b83c17c2969e0f6baffected · git
    • e2c94d6f572079511945e64537eb1218643f2e68 and later · before b3fc3e1f04dcc7c41787bbf08a6e0d2728e022cfaffected · git
    • e2c94d6f572079511945e64537eb1218643f2e68 and later · before 6a5820ecfa5a76c3d3e154802c8c15f391ef442eaffected · git
    • e2c94d6f572079511945e64537eb1218643f2e68 and later · before 6fd6d2a8e41b7f544a4d26cbd60bedf9c67893a0affected · git
    • e2c94d6f572079511945e64537eb1218643f2e68 and later · before e6b2609af21b5cccc9559339591b8a2cbf884169affected · git
    • e2c94d6f572079511945e64537eb1218643f2e68 and later · before 761fcf46a1bd797bd32d23f3ea0141ffd437668aaffected · git
    • before 5.8not affected · semver
    • 5.10.249 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-71193Feb 4, 2026 · phy: qcom-qusb2: Fix NULL pointer dereference on early suspend
    0Monitor
  • ← EarlierCVE-2025-71194Feb 4, 2026 · btrfs: fix deadlock in wait_current_trans() due to ignored transaction type
    0Monitor
  • Later →CVE-2025-71198Feb 4, 2026 · iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux060b08d72a38b158a7f850d4b83c17c2969e0f6bVendor (CNA)
Linux Linux49ff9b4b9deacbefa6654a0a2bcaf910c9de7e95Vendor (CNA)
Linux Linux6a5820ecfa5a76c3d3e154802c8c15f391ef442eVendor (CNA)
Linux Linux6fd6d2a8e41b7f544a4d26cbd60bedf9c67893a0Vendor (CNA)
Linux Linux761fcf46a1bd797bd32d23f3ea0141ffd437668aVendor (CNA)
Linux Linuxb3fc3e1f04dcc7c41787bbf08a6e0d2728e022cfVendor (CNA)
Linux Linuxe6b2609af21b5cccc9559339591b8a2cbf884169Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records