LiveActive security incident?Get immediate response
CVE Record

CVE-2024-50161: bpf: Check the remaining info_cnt before repeating btf fields

In the Linux kernel, the following vulnerability has been resolved: bpf: Check the remaining info_cnt before repeating btf fields When trying to repeat the btf fields for array of nested struct, it doesn't check the remaining info_cnt. The following splat will be reported when the value of ret * nelems is greater than BTF_FIELDS_MAX: ------------[ cut here ]------------ UBSAN: array-index-out-of-bounds in ../kernel/bpf/btf.c:3951:49 index 11 is out of range for type 'btf_field_info [11]' CPU: 6 UID: 0 PID: 411 Comm: test_progs ...... 6.11.0-rc4+ #1 Tainted: [O]=OOT_MODULE Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ... Call Trace: <TASK> dump_stack_lvl+0x57/0x70 dump_stack+0x10/0x20 ubsan_epilogue+0x9/0x40 __ubsan_handle_out_of_bounds+0x6f/0x80 ? kallsyms_lookup_name+0x48/0xb0 btf_parse_fields+0x992/0xce0 map_create+0x591/0x770 __sys_bpf+0x229/0x2410 __x64_sys_bpf+0x1f/0x30 x64_sys_call+0x199/0x9f0 do_syscall_64+0x3b/0xc0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7fea56f2cc5d ...... </TASK> ---[ end trace ]--- Fix it by checking the remaining info_cnt in btf_repeat_fields() before repeating the btf fields.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local, low-privileged user may reach an out-of-bounds condition in Linux kernel BPF type processing. The supplied CVSS assessment indicates possible loss of confidentiality, integrity, and availability, although the sources do not demonstrate successful compromise or real-world exploitation.

Executive priority

Treat as a high-priority local privilege risk on systems exposed to untrusted local users or workloads. It is not directly remote according to the supplied CVSS vector. Prioritize vendor-supported kernel updates, while avoiding emergency claims because active exploitation is not evidenced.

Technical view

btf_repeat_fields() failed to check the remaining info_cnt before duplicating BTF fields for arrays of nested structures. When ret multiplied by nelems exceeds BTF_FIELDS_MAX, btf_parse_fields() can access beyond the btf_field_info array. The cited kernel changes add the missing bounds check.

Likely exposure

Exposure is limited to affected Linux kernels where a low-privileged local actor can reach the BPF map-creation path. The bundle points to the Linux 6.11-era and 6.12 lines, but its flattened version metadata is ambiguous. Confirm distribution-specific backports rather than relying only on version strings.

Exploitation context

The CVSS vector requires local access, low privileges, no user interaction, and low complexity. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. Its trace demonstrates an UBSAN-detected bounds violation during BPF testing, not successful security impact.

Researcher notes

The reported trigger involves repeated BTF fields for arrays of nested structures and an unchecked remaining info_cnt. The observable failure occurs in kernel/bpf/btf.c within btf_parse_fields(). CWE-129 and CVSS 7.8 are supplied. Whether the access is reliably exploitable beyond a diagnostic crash is not established by these sources.

Mitigation direction

  • Install a vendor kernel update containing the cited bounds-check fix.
  • Reboot systems into the updated kernel after installation.
  • Check distribution guidance for backported fixes and affected package versions.
  • If no update is available, follow vendor guidance; no alternative mitigation is identified in the sources.

Validation and detection

  • Record each system's running kernel build, not only its installed package version.
  • Confirm the distribution kernel includes either cited stable-kernel fix or an equivalent backport.
  • Verify systems booted into the corrected kernel after maintenance.
  • Review kernel diagnostics for btf_parse_fields array-index-out-of-bounds reports.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-129: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-50161 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-50161Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux64e8ee814819f21beeeda00d4119221443d77992, 64e8ee814819f21beeeda00d4119221443d77992unaffected
LinuxLinux6.11, 0, 6.11.6, 6.12affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-129 · source CWE mapping

Improper Validation of Array Index

Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.