Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-50164bpf: Fix overloading of MEM_UNINIT's meaning

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix overloading of MEM_UNINIT's meaning Lonial reported an issue in the BPF verifier where check_mem_size_reg() has the following code: if (!tnum_is_const(reg->var_off)) /* For unprivileged variable accesses, disable raw * mode so that the program is required to * initialize all the memory that the helper could * just partially fill up. */ meta = NULL; This means that writes are not checked when the register containing the size of the passed buffer has not a fixed size. Through this bug, a BPF program can write to a map which is marked as read-only, for example, .rodata global maps. The problem is that MEM_UNINIT's initial meaning that "the passed buffer to the BPF helper does not need to be initialized" which was added back in commit 435faee1aae9 ("bpf, verifier: add ARG_PTR_TO_RAW_STACK type") got overloaded over time with "the passed buffer is being written to". The problem however is that checks such as the above which were added later via 06c1c049721a ("bpf: allow helpers access to variable memory") set meta to NULL in order force the user to always initialize the passed buffer to the helper. Due to the current double meaning of MEM_UNINIT, this bypasses verifier write checks to the memory (not boundary checks though) and only assumes the latter memory is read instead. Fix this by reverting MEM_UNINIT back to its original meaning, and having MEM_WRITE as an annotation to BPF helpers in order to then trigger the BPF verifier checks for writing to memory. Some notes: check_arg_pair_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO} we can access fn->arg_type[arg - 1] since it must contain a preceding ARG_PTR_TO_MEM. For check_mem_reg() the meta argument can be removed altogether since we do check both BPF_READ and BPF_WRITE. Same for the equivalent check_kfunc_mem_size_reg().

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50164, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 97e6d7dab1ca4648821c790a2b7913d6d5d549db – < 43f4df339a4d375bedcad29a61ae6f0ee7a048f8
    • affected 97e6d7dab1ca4648821c790a2b7913d6d5d549db – < 48068ccaea957469f1adf78dfd2c1c9a7e18f0fe
    • affected 97e6d7dab1ca4648821c790a2b7913d6d5d549db – < 54bc31682660810af1bed7ca7a19f182df8d3df8
    • affected 97e6d7dab1ca4648821c790a2b7913d6d5d549db – < 8ea607330a39184f51737c6ae706db7fdca7628e
    • affected 6099a6c8a749a5c8d5f8b4c4342022a92072a02b
    • affected bfe25df63048edd4ceaf78a2fc755d5e2befc978
    • affected 717c39718dbc4f7ebcbb7b625fb11851cd9007fe
    • affected 5d0bba8232bf22ce13747cbfc8f696318ff01a50
    • affected 70674d11d14eeecad90be4b409a22b902112ba32
    • affected a08d942ecbf46e23a192093f6983cb1d779f4fa8
    • affected 5.15.45 – < 5.16
    • affected 5.17.13 – < 5.18
    • affected 5.18.2 – < 5.19
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.125 – ≤ 6.1.*
    • unaffected 6.6.59 – ≤ 6.6.*
    • unaffected 6.11.6 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50164 badge
[![CVE-2024-50164](https://cveledger.app/badge/CVE-2024-50164.svg)](https://cveledger.app/cve/CVE-2024-50164)

Record last updated .