Answer in brief
CVE-2024-50203 records a Unknown severity vulnerability in bpf, arm64: Fix address emission with tag-based KASAN enabled. 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 | >=077149478497b2f00ff4fd9da2c892defa6418d8 <9e80f366ebfdfafc685fe83a84c34f7ef01cbe88 || >=d9664e6ff040798a46cdc5d401064f55b8676c83 <f521c2a0c0c4585f36d912bf62c852b88682c4f2 || >=19d3c179a37730caf600a97fed3794feac2b197b <7db1a2121f3c7903b8e397392beec563c3d00950 || >=19d3c179a37730caf600a97fed3794feac2b197b <a552e2ef5fd1a6c78267cd4ec5a9b49aa11bbb1c || 6d218fcc707d6b2c3616b6cd24b948fd4825cfec || >=6.10.3 <6.11 | 9e80f366ebfdfafc685fe83a84c34f7ef01cbe88, f521c2a0c0c4585f36d912bf62c852b88682c4f2, 7db1a2121f3c7903b8e397392beec563c3d00950, a552e2ef5fd1a6c78267cd4ec5a9b49aa11bbb1c, 6.11 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Nov 8, 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, arm64: Fix address emission with tag-based KASAN enabled When BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image struct on the stack is passed during the size calculation pass and an address on the heap is passed during code generation. This may cause a heap buffer overflow if the heap address is tagged because emit_a64_mov_i64() will emit longer code than it did during the size calculation pass. The same problem could occur without tag-based KASAN if one of the 16-bit words of the stack address happened to be all-ones during the size calculation pass. Fix the problem by assuming the worst case (4 instructions) when calculating the size of the bpf_tramp_image address emission.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-50203 records a Unknown severity vulnerability in bpf, arm64: Fix address emission with tag-based KASAN enabled. 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 | >=077149478497b2f00ff4fd9da2c892defa6418d8 <9e80f366ebfdfafc685fe83a84c34f7ef01cbe88 || >=d9664e6ff040798a46cdc5d401064f55b8676c83 <f521c2a0c0c4585f36d912bf62c852b88682c4f2 || >=19d3c179a37730caf600a97fed3794feac2b197b <7db1a2121f3c7903b8e397392beec563c3d00950 || >=19d3c179a37730caf600a97fed3794feac2b197b <a552e2ef5fd1a6c78267cd4ec5a9b49aa11bbb1c || 6d218fcc707d6b2c3616b6cd24b948fd4825cfec || >=6.10.3 <6.11 | 9e80f366ebfdfafc685fe83a84c34f7ef01cbe88, f521c2a0c0c4585f36d912bf62c852b88682c4f2, 7db1a2121f3c7903b8e397392beec563c3d00950, a552e2ef5fd1a6c78267cd4ec5a9b49aa11bbb1c, 6.11 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Nov 8, 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, arm64: Fix address emission with tag-based KASAN enabled When BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image struct on the stack is passed during the size calculation pass and an address on the heap is passed during code generation. This may cause a heap buffer overflow if the heap address is tagged because emit_a64_mov_i64() will emit longer code than it did during the size calculation pass. The same problem could occur without tag-based KASAN if one of the 16-bit words of the stack address happened to be all-ones during the size calculation pass. Fix the problem by assuming the worst case (4 instructions) when calculating the size of the bpf_tramp_image address emission.
Quoted source text, attributed separately from HOL analysis.