Answer in brief
CVE-2024-49861 records a Unknown severity vulnerability in bpf: Fix helper writes to read-only maps. 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 | >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <988e55abcf7fdb8fc9a76a7cf3f4e939a4d4fb3a || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <a2c8dc7e21803257e762b0bf067fd13e9c995da0 || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <2ed98ee02d1e08afee88f54baec39ea78dc8a23c || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <1e75d25133158b525e0456876e9bcfd6b2993fd5 || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <32556ce93bc45c730829083cb60f95a2728ea48b | 988e55abcf7fdb8fc9a76a7cf3f4e939a4d4fb3a, a2c8dc7e21803257e762b0bf067fd13e9c995da0, 2ed98ee02d1e08afee88f54baec39ea78dc8a23c, 1e75d25133158b525e0456876e9bcfd6b2993fd5, 32556ce93bc45c730829083cb60f95a2728ea48b |
| Linux/Linuxgeneric | 5.2 | 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: Fix helper writes to read-only maps Lonial found an issue that despite user- and BPF-side frozen BPF map (like in case of .rodata), it was still possible to write into it from a BPF program side through specific helpers having ARG_PTR_TO_{LONG,INT} as arguments. In check_func_arg() when the argument is as mentioned, the meta->raw_mode is never set. Later, check_helper_mem_access(), under the case of PTR_TO_MAP_VALUE as register base type, it assumes BPF_READ for the subsequent call to check_map_access_type() and given the BPF map is read-only it succeeds. The helpers really need to be annotated as ARG_PTR_TO_{LONG,INT} | MEM_UNINIT when results are written into them as opposed to read out of them. The latter indicates that it's okay to pass a pointer to uninitialized memory as the memory is written to anyway. However, ARG_PTR_TO_{LONG,INT} is a special case of ARG_PTR_TO_FIXED_SIZE_MEM just with additional alignment requirement. So it is better to just get rid of the ARG_PTR_TO_{LONG,INT} special cases altogether and reuse the fixed size memory types. For this, add MEM_ALIGNED to additionally ensure alignment given these helpers write directly into the args via *<ptr> = val. The .arg*_size has been initialized reflecting the actual sizeof(*<ptr>). MEM_ALIGNED can only be used in combination with MEM_FIXED_SIZE annotated argument types, since in !MEM_FIXED_SIZE cases the verifier does not know the buffer size a priori and therefore cannot blindly write *<ptr> = val.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-49861 records a Unknown severity vulnerability in bpf: Fix helper writes to read-only maps. 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 | >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <988e55abcf7fdb8fc9a76a7cf3f4e939a4d4fb3a || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <a2c8dc7e21803257e762b0bf067fd13e9c995da0 || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <2ed98ee02d1e08afee88f54baec39ea78dc8a23c || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <1e75d25133158b525e0456876e9bcfd6b2993fd5 || >=57c3bb725a3dd97d960d7e1cd0845d88de53217f <32556ce93bc45c730829083cb60f95a2728ea48b | 988e55abcf7fdb8fc9a76a7cf3f4e939a4d4fb3a, a2c8dc7e21803257e762b0bf067fd13e9c995da0, 2ed98ee02d1e08afee88f54baec39ea78dc8a23c, 1e75d25133158b525e0456876e9bcfd6b2993fd5, 32556ce93bc45c730829083cb60f95a2728ea48b |
| Linux/Linuxgeneric | 5.2 | 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: Fix helper writes to read-only maps Lonial found an issue that despite user- and BPF-side frozen BPF map (like in case of .rodata), it was still possible to write into it from a BPF program side through specific helpers having ARG_PTR_TO_{LONG,INT} as arguments. In check_func_arg() when the argument is as mentioned, the meta->raw_mode is never set. Later, check_helper_mem_access(), under the case of PTR_TO_MAP_VALUE as register base type, it assumes BPF_READ for the subsequent call to check_map_access_type() and given the BPF map is read-only it succeeds. The helpers really need to be annotated as ARG_PTR_TO_{LONG,INT} | MEM_UNINIT when results are written into them as opposed to read out of them. The latter indicates that it's okay to pass a pointer to uninitialized memory as the memory is written to anyway. However, ARG_PTR_TO_{LONG,INT} is a special case of ARG_PTR_TO_FIXED_SIZE_MEM just with additional alignment requirement. So it is better to just get rid of the ARG_PTR_TO_{LONG,INT} special cases altogether and reuse the fixed size memory types. For this, add MEM_ALIGNED to additionally ensure alignment given these helpers write directly into the args via *<ptr> = val. The .arg*_size has been initialized reflecting the actual sizeof(*<ptr>). MEM_ALIGNED can only be used in combination with MEM_FIXED_SIZE annotated argument types, since in !MEM_FIXED_SIZE cases the verifier does not know the buffer size a priori and therefore cannot blindly write *<ptr> = val.
Quoted source text, attributed separately from HOL analysis.