Answer in brief
CVE-2022-49078 records a Unknown severity vulnerability in lz4: fix LZ4_decompress_safe_partial read out of bound. 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.
A CVSS score is not reported in the current record. 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 | >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <73953dfa9d50e5c9fe98ee13fd1d3427aa12a0a3 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <6adc01a7aa37445dafe8846faa0610a86029b253 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <9fb8bc6cfc58773ce95414e11c9ccc8fc6ac4927 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <e64dbe97c05c769525cbca099ddbd22485630235 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <467d5e200ab4486b744fe1776154a43d1aa22d4b || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <eafc0a02391b7b36617b36c97c4b5d6832cf5e24 | 73953dfa9d50e5c9fe98ee13fd1d3427aa12a0a3, 6adc01a7aa37445dafe8846faa0610a86029b253, 9fb8bc6cfc58773ce95414e11c9ccc8fc6ac4927, e64dbe97c05c769525cbca099ddbd22485630235, 467d5e200ab4486b744fe1776154a43d1aa22d4b, eafc0a02391b7b36617b36c97c4b5d6832cf5e24 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: lz4: fix LZ4_decompress_safe_partial read out of bound When partialDecoding, it is EOF if we've either filled the output buffer or can't proceed with reading an offset for following match. In some extreme corner cases when compressed data is suitably corrupted, UAF will occur. As reported by KASAN [1], LZ4_decompress_safe_partial may lead to read out of bound problem during decoding. lz4 upstream has fixed it [2] and this issue has been disscussed here [3] before. current decompression routine was ported from lz4 v1.8.3, bumping lib/lz4 to v1.9.+ is certainly a huge work to be done later, so, we'd better fix it first. [1] https://lore.kernel.org/all/[email protected]/ [2] https://github.com/lz4/lz4/commit/c5d6f8a8be3927c0bec91bcc58667a6cfad244ad# [3] https://lore.kernel.org/all/[email protected]/
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49078 records a Unknown severity vulnerability in lz4: fix LZ4_decompress_safe_partial read out of bound. 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.
A CVSS score is not reported in the current record. 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 | >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <73953dfa9d50e5c9fe98ee13fd1d3427aa12a0a3 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <6adc01a7aa37445dafe8846faa0610a86029b253 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <9fb8bc6cfc58773ce95414e11c9ccc8fc6ac4927 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <e64dbe97c05c769525cbca099ddbd22485630235 || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <467d5e200ab4486b744fe1776154a43d1aa22d4b || >=2209fda323e2fd2a2d0885595fd5097717f8d2aa <eafc0a02391b7b36617b36c97c4b5d6832cf5e24 | 73953dfa9d50e5c9fe98ee13fd1d3427aa12a0a3, 6adc01a7aa37445dafe8846faa0610a86029b253, 9fb8bc6cfc58773ce95414e11c9ccc8fc6ac4927, e64dbe97c05c769525cbca099ddbd22485630235, 467d5e200ab4486b744fe1776154a43d1aa22d4b, eafc0a02391b7b36617b36c97c4b5d6832cf5e24 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: lz4: fix LZ4_decompress_safe_partial read out of bound When partialDecoding, it is EOF if we've either filled the output buffer or can't proceed with reading an offset for following match. In some extreme corner cases when compressed data is suitably corrupted, UAF will occur. As reported by KASAN [1], LZ4_decompress_safe_partial may lead to read out of bound problem during decoding. lz4 upstream has fixed it [2] and this issue has been disscussed here [3] before. current decompression routine was ported from lz4 v1.8.3, bumping lib/lz4 to v1.9.+ is certainly a huge work to be done later, so, we'd better fix it first. [1] https://lore.kernel.org/all/[email protected]/ [2] https://github.com/lz4/lz4/commit/c5d6f8a8be3927c0bec91bcc58667a6cfad244ad# [3] https://lore.kernel.org/all/[email protected]/
Quoted source text, attributed separately from HOL analysis.