Answer in brief
CVE-2024-41019 records a High severity (CVSS 7.8) vulnerability in fs/ntfs3: Validate ff offset. 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 | >=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <35652dfa8cc9a8a900ec0f1e0395781f94ffc5f0 || >=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <818a257428644b8873e79c44404d8fb6598d4440 || >=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <6ae7265a7b816879fd0203e83b5030d3720bbb7a || >=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <82c94e6a7bd116724738aa67eba6f5fedf3a3319 || >=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <617cf144c206f98978ec730b17159344fd147cb4 || >=4534a70b7056fd4b9a1c6db5a4ce3c98546b291e <50c47879650b4c97836a0086632b3a2e300b0f06 | 35652dfa8cc9a8a900ec0f1e0395781f94ffc5f0, 818a257428644b8873e79c44404d8fb6598d4440, 6ae7265a7b816879fd0203e83b5030d3720bbb7a, 82c94e6a7bd116724738aa67eba6f5fedf3a3319, 617cf144c206f98978ec730b17159344fd147cb4, 50c47879650b4c97836a0086632b3a2e300b0f06 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Jul 29, 2024
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: fs/ntfs3: Validate ff offset This adds sanity checks for ff offset. There is a check on rt->first_free at first, but walking through by ff without any check. If the second ff is a large offset. We may encounter an out-of-bound read.
Quoted source text, attributed separately from HOL analysis.