LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31391: crypto: atmel-sha204a - Fix OOM ->tfm_count leak

In the Linux kernel, the following vulnerability has been resolved: crypto: atmel-sha204a - Fix OOM ->tfm_count leak If memory allocation fails, decrement ->tfm_count to avoid blocking future reads.

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

Security readout for executives and security teams

Plain-English summary

A Linux kernel error-handling flaw can leave an internal usage counter elevated when memory allocation fails in the Atmel SHA204A crypto driver. That stale counter may prevent later reads, causing a localized availability problem. The supplied sources provide no severity score, demonstrated attack path, or evidence of broader system compromise.

Executive priority

Treat this as a targeted maintenance issue, not an emergency based on current evidence. Promptly assess embedded or industrial systems relying on the Atmel SHA204A device, where blocked reads could disrupt essential functions. Schedule vendor-approved kernel updates according to operational criticality and maintenance constraints.

Technical view

The atmel-sha204a driver fails to decrement tfm_count after an out-of-memory allocation failure. Subsequent operations may see the incorrect count and block future reads. Linux stable commits correct the counter handling. The bundle does not establish whether an unprivileged or remote actor can reliably trigger the required memory-allocation failure.

Likely exposure

Exposure is limited to Linux systems using the affected atmel-sha204a driver and vulnerable kernel code. The supplied version data lists multiple affected releases, but its exact range semantics are unclear. Systems without this driver or associated hardware are unlikely to reach the vulnerable path, although configuration and runtime use should be verified.

Exploitation context

CISA KEV status is false, and the supplied sources report no active exploitation, public proof of concept, or reliable remote trigger. Exploitation feasibility remains uncertain because the flaw depends on a memory-allocation failure in a specific driver path. The documented impact is blocked future reads, indicating availability risk rather than established code execution or data disclosure.

Researcher notes

The defect is a counter-state leak on an allocation-failure path, not evidence of a heap-memory leak despite the OOM wording. Important unknowns include trigger permissions, allocation size, recovery without reboot or reload, concurrency effects, and practical service impact. The source bundle provides fixes but no CVSS, CWE, reproduction details, or exploitation evidence.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable Linux stable fix.
  • Review Linux distribution and device-vendor advisories for the correct fixed package.
  • If updates are delayed, assess whether the atmel-sha204a driver can be safely disabled.
  • Prioritize devices where the affected crypto hardware supports essential operations.

Validation and detection

  • Inventory kernel versions, configurations, and devices using the atmel-sha204a driver.
  • Map installed kernels to the affected and fixed records from Linux or your distributor.
  • Confirm the updated kernel contains the applicable stable commit and is running.
  • After remediation, test repeated device reads, including controlled memory-pressure error handling where safe.
Prepared
Confidence
medium
Sources
9

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-2026-31391 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
10Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxda001fb651b00e1deeaf24767dd691ae8152a4f5, da001fb651b00e1deeaf24767dd691ae8152a4f5, da001fb651b00e1deeaf24767dd691ae8152a4f5, da001fb651b00e1deeaf24767dd691ae8152a4f5, da001fb651b00e1deeaf24767dd691ae8152a4f5, da001fb651b00e1deeaf24767dd691ae8152a4f5, da001fb651b00e1deeaf24767dd691ae8152a4f5unaffected
LinuxLinux5.3, 0, 5.10.253, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10, 7.0affected
Weakness

CWE details

No CWE listed

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