Skip to main content

Linux Kernel CVE-2026-74687

| EUVDEUVD-2026-64374 HIGH
2026-08-22 Linux GHSA-x3hg-mqqh-m29v
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local access to AT91 SAM9 Linux system
  2. Delivery
    Trigger at91sam9_wdt driver removal or probe failure
  3. Exploit
    Race timer callback against devm memory release
  4. Execution
    Timer callback accesses freed at91wdt memory
  5. Persist
    Corrupt kernel heap via use-after-free
  6. Impact
    Escalate privileges to root

Vulnerability Assessment

Exploitation Conditions

Exploitation requires physical or logical access to a Linux system running on AT91 SAM9 SoC hardware with the at91sam9_wdt watchdog driver loaded - this driver is not present or active on any other hardware platform. The race window is triggered during driver teardown: either by unloading the at91sam9_wdt module (typically requiring CAP_SYS_MODULE / root-equivalent privileges) or by a probe failure during boot initialization (not user-triggerable in most configurations). The CVSS PR:L assignment implies the kernel team considers non-root triggering possible in some configurations, but the specific path is not confirmed in the description. Exploitation requires winning a timing race between the timer callback and memory deallocation, which adds non-determinism. Systems that do not use the AT91 SAM9 watchdog peripheral, or where the driver is blacklisted, are not affected regardless of kernel version.

Impact

CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this as High severity, reflecting the full CIA impact achievable from a kernel use-after-free. However, several signals significantly temper real-world risk: EPSS is 0.21% (11th percentile), indicating very low observed exploitation probability; the vulnerability is not in CISA KEV; and no public exploit or POC is known. The AV:L/AC:L assignment deserves scrutiny - this is a race condition, which typically implies AC:H; the assigned AC:L may reflect the kernel team's judgment that the race window is consistently reachable under normal probe-failure or unload conditions, but independent assessment suggests AC:H is more accurate. PR:L in the official vector implies exploitation is possible without root, yet triggering driver unload (rmmod) on a production system typically requires CAP_SYS_MODULE (root-equivalent). Probe failure races occur at boot time and are not ordinarily user-triggerable. Critically, this driver only executes on systems physically equipped with AT91 SAM9 SoC hardware - effectively restricting exposure to embedded and industrial Linux deployments on Microchip silicon. For mainstream x86/ARM server and desktop Linux environments, this vulnerability is irrelevant. The combination of hardware specificity, race timing requirements, low EPSS, and no active exploitation makes this a low real-world priority despite the High CVSS base score.

Exploit ScenarioDerived

An attacker with local access on an embedded Linux system based on an Atmel/Microchip AT91 SAM9 SoC - such as an industrial controller or IoT gateway - triggers watchdog driver removal (e.g., via rmmod at91sam9_wdt on a system where this is permitted, or by inducing probe failure at boot). If the at91_ping() timer callback fires in the narrow window between devm memory release and timer cancellation, the callback writes into freed memory, potentially corrupting kernel heap structures. A sophisticated attacker could shape the heap to place controlled data at the freed address, redirecting execution flow to achieve privilege escalation to root. No public POC exists at time of analysis, meaning this would require original exploit development.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 25, 2026

Use-after-free race condition in the Linux kernel at91sam9_wdt watchdog driver allows a local attacker with low privileges on affected AT91 SAM9 SoC hardware to corrupt freed memory, potentially achieving kernel-level code execution. The flaw arises because at91_ping() rearms a kernel timer from within its own callback, while timer_delete() neither waits for an in-flight callback to finish nor prevents rearming - leaving a window during probe failure or driver removal where the timer accesses devm-allocated memory that has already been freed. No public exploit has been identified at time of analysis, and EPSS probability is very low (0.21%, 11th percentile), consistent with the hardware-specific and timing-dependent nature of this race.

RemediationAI

The primary fix is to upgrade to a patched Linux kernel stable release: 6.18.45 or later on the 6.18.x branch, 7.1.9 or later on the 7.1.x branch, or 7.2 (mainline). The specific kernel.org stable commits that carry the fix are b7949b0a7d998013b7ec8617a0ef5b07cca80be4, 8444d66aa6b6e7fe0a26fa1a00a11cb4d0523783, and 29fe74c9aa69d78c1c6a3930f1d9fc5db71a6eed, accessible at https://git.kernel.org/stable/c/<commit>. Distributions shipping custom kernel builds for AT91 SAM9 platforms (BSP vendors, Yocto layers, Buildroot configs) should cherry-pick the appropriate backport commit for their kernel version. As a compensating control on systems that cannot be immediately patched, disabling the at91sam9_wdt kernel module (rmmod at91sam9_wdt or blacklisting it in /etc/modprobe.d/) prevents the vulnerable code path from running, with the trade-off of disabling hardware watchdog supervision - acceptable only in managed environments with alternative health monitoring. Restricting CAP_SYS_MODULE via seccomp or capability bounding sets also limits the ability of non-root processes to trigger driver unload, though this does not address probe-time races.

Affected VersionsENISA

Linux 5161b31dc39a6d6dadc95f298de48a725b73ada8 <b7949b0a7d998013b7ec8617a0ef5b07cca80be4
Linux patch: 7.1.9
Linux patch: 0
Linux 3.14
Linux patch: 6.18.45
Linux 5161b31dc39a6d6dadc95f298de48a725b73ada8 <8444d66aa6b6e7fe0a26fa1a00a11cb4d0523783
Linux 5161b31dc39a6d6dadc95f298de48a725b73ada8 <29fe74c9aa69d78c1c6a3930f1d9fc5db71a6eed
Linux patch: 7.2

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The at91sam9_wdt driver implements watchdog functionality for Atmel/Microchip AT91 SAM9 series SoCs (System-on-Chips), commonly found in embedded Linux platforms. The driver registers a kernel hrtimer-style timer that rearms itself from at91_ping() on expiry to keep the watchdog fed. The defect class is a classic timer teardown race: when the driver is removed (or probe fails), the teardown path called timer_delete(), which cancels a pending timer but does not synchronize with an already-executing callback, and crucially does not set a flag that prevents the callback from rescheduling the timer. This allows at91_ping() to re-queue the timer after the backing memory managed by devres (devm_*) has been released, resulting in a use-after-free. No CWE is formally assigned, but this maps to CWE-416 (Use After Free) combined with CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization). The fix replaces timer_delete() with timer_shutdown_sync() on both teardown paths; this function blocks until any running callback completes and then marks the timer as dead, causing subsequent rearm attempts to be silently dropped. Affected CPE is cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* across multiple stable branches introduced with the initial at91sam9_wdt commit (5161b31dc39a6d6dadc95f298de48a725b73ada8).

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 6.4 MEDIUM

Race condition timing requires AC:H; triggering driver unload requires CAP_SYS_MODULE, so PR:H; kernel UAF yields full CIA:H.

3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 4.1 MEDIUM
AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 25, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 22, 2026 - 16:01 EUVD
CVE Published
Aug 22, 2026 - 15:32 cve.org
HIGH 7.8
CVE Published
Aug 22, 2026 - 15:32 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

watchdog: at91sam9_wdt: prevent timer rearm during teardown

at91_ping() rearms the watchdog timer from its callback. timer_delete() neither waits for a running callback nor prevents it from rearming the timer, so probe failure or driver removal can leave the timer accessing the devm-allocated at91wdt after it has been freed.

Use timer_shutdown_sync() on both teardown paths. It waits for a running callback and rejects any attempt by the callback to rearm the timer.

Executive ViewAI

Why It Matters

A use-after-free race condition in the Linux kernel watchdog driver for AT91 SAM9 SoC hardware (CVE-2026-74687, CVSS 7.8) could allow local attackers to achieve kernel-level code execution. While technically severe, real-world exploitation is highly unlikely due to strict hardware requirements, timing constraints, and absence of public exploit code (EPSS 0.21%). Organizations should prioritize based on whether AT91 SAM9 hardware is deployed in production environments.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Low
hardware-specific watchdog driver for Atmel AT91 SAM9 embedded SoCs only
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy