CVE-2026-31391: crypto: atmel-sha204a - Fix OOM ->tfm_count leak
Published Apr 3, 2026
·Updated
In the Linux kernel, the following vulnerability has been resolved:
crypto: atmel-sha204a - Fix OOM ->tfmcount leak
If memory allocation fails, decrement ->tfmcount to avoid blocking future reads.
Affected Software
9 affected components
Linux Linux kernel (atmel-sha204a crypto driver)
Linux Linux kernel>=5.3<5.10.253
Linux Linux kernel>=5.11<6.1.167
Linux Linux kernel>=6.2<6.6.130
Linux Linux kernel>=6.7<6.12.78
Linux Linux kernel>=6.13<6.18.20
Linux Linux kernel>=6.19<6.19.10
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Event History
Apr 3, 2026
CVE Published
via MITRE·03:15 PM
Data Sourced
via MITRE·03:15 PM
Description
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-31391?
CVE-2026-31391 is classified as a low severity vulnerability affecting the Linux kernel's atmel-sha204a crypto driver.
2
How do I fix CVE-2026-31391?
To fix CVE-2026-31391, update your Linux kernel to a version where the vulnerability has been patched.
3
What does CVE-2026-31391 affect?
CVE-2026-31391 affects the atmel-sha204a crypto driver in the Linux kernel.
4
What is the nature of the issue in CVE-2026-31391?
CVE-2026-31391 involves a leak of the tfm_count variable when memory allocation fails, which could affect future reads.
5
Is CVE-2026-31391 remotely exploitable?
CVE-2026-31391 is not considered remotely exploitable, as it requires local access to the affected system.