Answer in brief
CVE-2024-41049 records a Unknown severity vulnerability in filelock: fix potential use-after-free in posix_lock_inode. 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.
Answer in brief
CVE-2024-41049 records a Unknown severity vulnerability in filelock: fix potential use-after-free in posix_lock_inode. 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 | >=117fb80cd1e63c419c7a221ce070becb4bfc7b6d <1cbbb3d9475c403ebedc327490c7c2b991398197 || >=a6f4129378ca15f62cbdde09a7d3ccc35adcf49d <7d4c14f4b511fd4c0dc788084ae59b4656ace58b || >=766e56faddbec2eaf70c9299e1c9ef74d846d32b <02a8964260756c70b20393ad4006948510ac9967 || >=34bff6d850019e00001129d6de3aa4874c2cf471 <5cb36e35bc10ea334810937990c2b9023dacb1b0 || >=74f6f5912693ce454384eaeec48705646a21c74f <432b06b69d1d354a171f7499141116536579eb6a || >=74f6f5912693ce454384eaeec48705646a21c74f <116599f6a26906cf33f67975c59f0692ecf7e9b2 || >=74f6f5912693ce454384eaeec48705646a21c74f <1b3ec4f7c03d4b07bad70697d7e2f4088d2cfe92 || e75396988bb9b3b90e6e8690604d0f566cea403a || >=5.4.257 <5.4.280 || >=5.10.197 <5.10.222 || >=5.15.133 <5.15.163 || >=6.1.55 <6.1.100 || >=6.5.5 <6.6 | 1cbbb3d9475c403ebedc327490c7c2b991398197, 7d4c14f4b511fd4c0dc788084ae59b4656ace58b, 02a8964260756c70b20393ad4006948510ac9967, 5cb36e35bc10ea334810937990c2b9023dacb1b0, 432b06b69d1d354a171f7499141116536579eb6a, 116599f6a26906cf33f67975c59f0692ecf7e9b2, 1b3ec4f7c03d4b07bad70697d7e2f4088d2cfe92, 5.4.280, 5.10.222, 5.15.163, 6.1.100, 6.6 |
| Linux/Linuxgeneric | 6.6 | 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: filelock: fix potential use-after-free in posix_lock_inode Light Hsieh reported a KASAN UAF warning in trace_posix_lock_inode(). The request pointer had been changed earlier to point to a lock entry that was added to the inode's list. However, before the tracepoint could fire, another task raced in and freed that lock. Fix this by moving the tracepoint inside the spinlock, which should ensure that this doesn't happen.
Quoted source text, attributed separately from HOL analysis.
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 | >=117fb80cd1e63c419c7a221ce070becb4bfc7b6d <1cbbb3d9475c403ebedc327490c7c2b991398197 || >=a6f4129378ca15f62cbdde09a7d3ccc35adcf49d <7d4c14f4b511fd4c0dc788084ae59b4656ace58b || >=766e56faddbec2eaf70c9299e1c9ef74d846d32b <02a8964260756c70b20393ad4006948510ac9967 || >=34bff6d850019e00001129d6de3aa4874c2cf471 <5cb36e35bc10ea334810937990c2b9023dacb1b0 || >=74f6f5912693ce454384eaeec48705646a21c74f <432b06b69d1d354a171f7499141116536579eb6a || >=74f6f5912693ce454384eaeec48705646a21c74f <116599f6a26906cf33f67975c59f0692ecf7e9b2 || >=74f6f5912693ce454384eaeec48705646a21c74f <1b3ec4f7c03d4b07bad70697d7e2f4088d2cfe92 || e75396988bb9b3b90e6e8690604d0f566cea403a || >=5.4.257 <5.4.280 || >=5.10.197 <5.10.222 || >=5.15.133 <5.15.163 || >=6.1.55 <6.1.100 || >=6.5.5 <6.6 | 1cbbb3d9475c403ebedc327490c7c2b991398197, 7d4c14f4b511fd4c0dc788084ae59b4656ace58b, 02a8964260756c70b20393ad4006948510ac9967, 5cb36e35bc10ea334810937990c2b9023dacb1b0, 432b06b69d1d354a171f7499141116536579eb6a, 116599f6a26906cf33f67975c59f0692ecf7e9b2, 1b3ec4f7c03d4b07bad70697d7e2f4088d2cfe92, 5.4.280, 5.10.222, 5.15.163, 6.1.100, 6.6 |
| Linux/Linuxgeneric | 6.6 | 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: filelock: fix potential use-after-free in posix_lock_inode Light Hsieh reported a KASAN UAF warning in trace_posix_lock_inode(). The request pointer had been changed earlier to point to a lock entry that was added to the inode's list. However, before the tracepoint could fire, another task raced in and freed that lock. Fix this by moving the tracepoint inside the spinlock, which should ensure that this doesn't happen.
Quoted source text, attributed separately from HOL analysis.