Answer in brief
CVE-2026-53156 records a High severity (CVSS 7.8) vulnerability in nvmem: core: fix use-after-free bugs in error paths. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e888d445ac33a5b0288d670ecd970908b13f07cd <6cdcf0d16c80900f42d60252480cd131c1a83d23 || >=e888d445ac33a5b0288d670ecd970908b13f07cd <e0d38bf47a72da2f02c9fa6f752cd66d977cd7f7 || >=e888d445ac33a5b0288d670ecd970908b13f07cd <cb85ef5a227b3662b88f4d849a1aad43bfe7f5ae || >=e888d445ac33a5b0288d670ecd970908b13f07cd <40e2a459c0dd1333b2343831480a0ad80dc07614 || >=e888d445ac33a5b0288d670ecd970908b13f07cd <5b6b6fc491899d583eaa75344e094796ae9b530b | 6cdcf0d16c80900f42d60252480cd131c1a83d23, e0d38bf47a72da2f02c9fa6f752cd66d977cd7f7, cb85ef5a227b3662b88f4d849a1aad43bfe7f5ae, 40e2a459c0dd1333b2343831480a0ad80dc07614, 5b6b6fc491899d583eaa75344e094796ae9b530b |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: nvmem: core: fix use-after-free bugs in error paths Fix several instances of error paths in which we call __nvmem_device_put() - which may end up freeing the underlying memory and other resources - and then keep on using the nvmem structure. Always put the reference to the nvmem device as the last step before returning the error code.
Quoted source text, attributed separately from HOL analysis.