Answer in brief
CVE-2024-47703 records a Unknown severity vulnerability in bpf, lsm: Add check for BPF LSM return value. 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 | >=520b7aa00d8cd8e411ecc09f63a2acd90feb6d29 <1050727d83e70449991c29dd1cf29fe936a63da3 || >=520b7aa00d8cd8e411ecc09f63a2acd90feb6d29 <27ca3e20fe80be85a92b10064dfeb56cb2564b1c || >=520b7aa00d8cd8e411ecc09f63a2acd90feb6d29 <5d99e198be279045e6ecefe220f5c52f8ce9bfd5 | 1050727d83e70449991c29dd1cf29fe936a63da3, 27ca3e20fe80be85a92b10064dfeb56cb2564b1c, 5d99e198be279045e6ecefe220f5c52f8ce9bfd5 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Oct 21, 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: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-47703 records a Unknown severity vulnerability in bpf, lsm: Add check for BPF LSM return value. 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 | >=520b7aa00d8cd8e411ecc09f63a2acd90feb6d29 <1050727d83e70449991c29dd1cf29fe936a63da3 || >=520b7aa00d8cd8e411ecc09f63a2acd90feb6d29 <27ca3e20fe80be85a92b10064dfeb56cb2564b1c || >=520b7aa00d8cd8e411ecc09f63a2acd90feb6d29 <5d99e198be279045e6ecefe220f5c52f8ce9bfd5 | 1050727d83e70449991c29dd1cf29fe936a63da3, 27ca3e20fe80be85a92b10064dfeb56cb2564b1c, 5d99e198be279045e6ecefe220f5c52f8ce9bfd5 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Oct 21, 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: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.
Quoted source text, attributed separately from HOL analysis.