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-42161bpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD [Changes from V1: - Use a default branch in the switch statement to initialize `val'.] GCC warns that `val' may be used uninitialized in the BPF_CRE_READ_BITFIELD macro, defined in bpf_core_read.h as: [...] unsigned long long val; \ [...] \ switch (__CORE_RELO(s, field, BYTE_SIZE)) { \ case 1: val = *(const unsigned char *)p; break; \ case 2: val = *(const unsigned short *)p; break; \ case 4: val = *(const unsigned int *)p; break; \ case 8: val = *(const unsigned long long *)p; break; \ } \ [...] val; \ } \ This patch adds a default entry in the switch statement that sets `val' to zero in order to avoid the warning, and random values to be used in case __builtin_preserve_field_info returns unexpected values for BPF_FIELD_BYTE_SIZE. Tested in bpf-next master. No regressions.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 22 months 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-42161, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium6.3CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ee26dade0e3bcd8a34ae7520e373fb69365fce7a – < b694989bb13ed5f166e633faa1eb0f21c6d261a6
    • affected ee26dade0e3bcd8a34ae7520e373fb69365fce7a – < 3364c2ed1c241989847f19cf83e3db903ce689e3
    • affected ee26dade0e3bcd8a34ae7520e373fb69365fce7a – < a21d76bd0b0d39518e9a4c19f6cf7c042a974aff
    • affected ee26dade0e3bcd8a34ae7520e373fb69365fce7a – < 7e5471b5efebc30dd0bc035cda86693a5c73d45f
    • affected ee26dade0e3bcd8a34ae7520e373fb69365fce7a – < ff941a8449e712eaf7efca1a13bfb9afd3d99fc2
    • affected ee26dade0e3bcd8a34ae7520e373fb69365fce7a – < 009367099eb61a4fc2af44d4eb06b6b4de7de6db
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.222 – ≤ 5.10.*
    • unaffected 5.15.163 – ≤ 5.15.*
    • unaffected 6.1.98 – ≤ 6.1.*
    • unaffected 6.6.39 – ≤ 6.6.*
    • unaffected 6.9.9 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .