OpenTelemetry eBPF Profiler: unprivileged process can stall the agent by mapping a FIFO

Impact

Between 0.0.202527 and 0.0.202622, the profiler opens mapping files backed by non-regular types such as a FIFO and blocks indefinitely, halting further ELF analysis. Any unprivileged process on the node can arrange this, so a single workload silently takes down continuous profiling for the whole host. On a GPU fleet this is an observability loss, not a data loss: the agent typically runs privileged as a DaemonSet across every node, and a tenant that can start a process can blind the operator's profiling for that node without touching anyone else's GPUs. There is no claim of code execution or data exposure.

Who can reach it

Local, unauthenticated relative to the agent: any unprivileged process on a node where the profiler runs, including a process inside a tenant pod.

What to do

Upgrade the profiler to v0.0.202622. The advisory states no workarounds are available. For a DaemonSet deployment this is an image bump and a rolling restart of the agent pods - no node drain and no GPU workload interruption.

References

Related entries

• AMD TEE / ASP bootloader syscall input validation: Insufficient validation of syscall inputs in the AMD trustedCVE-2021-46759 · AMD TEE / ASP bootloader syscall input validationMedium
• HashiCorp Consul: Missing Content-Type header lets user input be reinterpretedCVE-2024-10086 · HashiCorp ConsulMedium
• SPI flash configuration (flash descriptor / protected range registers) across multiple Intel platformsCVE-2017-5703 · SPI flash configuration (flash descriptor / protected range registers) across multiple Intel platformsMedium
• Intel Data Center GPU Max Series 1100 / 1550: An improper conditions check lets a privileged local user takeCVE-2023-47165 · Intel Data Center GPU Max Series 1100 / 1550Medium
• AMD PCIe link handling (memory buffer bounds): A guest VM can drive the PCIe link into an out-of-bounds conditionCVE-2024-21961 · AMD PCIe link handling (memory buffer bounds)Medium
• OpenStack Swift: S3API does not strip X-Copy-From, allowing cross-tenant object readsCVE-2026-71192 · OpenStack Swift S3API middleware (X-Copy-From header handling with s3_acl=true)Medium