CVE-2024-49861

Published at:
2024-10-21T13:15:06.800
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Global infos:

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 * = val. The .arg*_size has been initialized reflecting the actual sizeof(*). 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 * = val.

CVE Status: Modified

References:

  • 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  • 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  • 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  • 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  • 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  • Metrics:

    AttributeValue
    Attack ComplexityLOW
    Attack VectorLOCAL
    Availability ImpactHIGH
    Base Score7.1
    Base SeverityHIGH
    Confidentiality ImpactNONE
    Integrity ImpactHIGH
    Privileges RequiredLOW
    ScopeUNCHANGED
    User InteractionNONE
    Vector StringCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
    Exploitability Score1.8
    Impact Score5.2
    Source[email protected]
    TypePrimary

    Links:

    Exploit-db
    Github