LiveActive security incident?Get immediate response
CVE Record

CVE-2024-50203: bpf, arm64: Fix address emission with tag-based KASAN enabled

In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Fix address emission with tag-based KASAN enabled When BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image struct on the stack is passed during the size calculation pass and an address on the heap is passed during code generation. This may cause a heap buffer overflow if the heap address is tagged because emit_a64_mov_i64() will emit longer code than it did during the size calculation pass. The same problem could occur without tag-based KASAN if one of the 16-bit words of the stack address happened to be all-ones during the size calculation pass. Fix the problem by assuming the worst case (4 instructions) when calculating the size of the bpf_tramp_image address emission.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can cause a heap buffer overflow while generating ARM64 BPF trampoline code. A locally authenticated, low-privileged attacker may be able to crash the system or compromise kernel confidentiality and integrity. Exposure depends on kernel version, ARM64 architecture, and use of the affected BPF trampoline path.

Executive priority

Treat as a high-priority kernel maintenance issue for exposed ARM64 multi-user, container-hosting, or untrusted-workload systems. Accelerate inventory and patch confirmation, but do not characterize it as an active-exploitation emergency based on the supplied evidence.

Technical view

The BPF trampoline size-calculation pass can underestimate ARM64 instructions needed to emit a bpf_tramp_image address. Heap pointer tagging, or rarely an all-ones 16-bit stack-address word, can make code generation longer than calculated, producing a heap buffer overflow. The correction budgets the worst case of four instructions.

Likely exposure

Potentially exposed systems run ARM64 Linux and permit reachable BPF trampoline functionality using BPF_TRAMP_F_CALL_ORIG. The bundle lists 6.11, 6.11.6, and 6.12 as affected, but also contains an ambiguous version entry of "0". Confirm exact distribution backports and configuration with the vendor.

Exploitation context

The supplied CVSS is 7.8 and describes local, low-complexity exploitation requiring low privileges, without user interaction. Successful exploitation could affect confidentiality, integrity, and availability. The CVE is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.

Researcher notes

The trigger is a mismatch between sizing and emission passes, not solely tag-based KASAN. Tagged heap addresses make the discrepancy possible, while a particular stack-address pattern can reportedly trigger it without tag-based KASAN. The bundle does not establish exploit reliability, affected configurations beyond the described path, or distribution-specific remediation status.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable linked stable fix.
  • Confirm distribution backports because package versions may not map directly to upstream versions.
  • If immediate updating is impossible, consult vendor guidance for supported exposure-reduction measures.
  • Prioritize ARM64 systems where untrusted local users or workloads can access BPF functionality.

Validation and detection

  • Inventory ARM64 systems and record exact kernel package, release, and distribution revision.
  • Check vendor advisories or package changelogs for a backport of the linked correction.
  • Determine whether affected BPF trampoline functionality is enabled and reachable by low-privileged users.
  • After updating, verify the running kernel matches the remediated package and reboot state.
Prepared
Confidence
high
Sources
6

Public sources used

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.

cve · low confidence lookup

CVE-2024-50203 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.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

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

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-50203Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux077149478497b2f00ff4fd9da2c892defa6418d8, d9664e6ff040798a46cdc5d401064f55b8676c83, 19d3c179a37730caf600a97fed3794feac2b197b, 19d3c179a37730caf600a97fed3794feac2b197b, 6d218fcc707d6b2c3616b6cd24b948fd4825cfec, 6.10.3unaffected
LinuxLinux6.11, 0, 6.11.6, 6.12affected
Weakness

CWE details

No CWE listed

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