AZL-113579: CVE-2026-97038 affecting package python-tensorboard 2.16.2-6
Building a malicious package containing ".syso" files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including ".syso" files, direct object or library inputs in "#cgo LDFLAGS", and libraries in "-L" directories—were passed to the external linker without validating their format or checking for embedded linker options. Across platforms, this allowed executing GNU ld implicit linker scripts disguised as libraries or ".syso" files (or loaded via "-l:<filename>" or "-l" containing path separators), injecting unallowlisted linker flags via PE/COFF ".drectve" sections on Windows or Mach-O "LCLINKEROPTION" load commands on Darwin, or invoking LTO plugins via GCC or LLVM LTO intermediate representation sections in ELF, PE/COFF, or Mach-O objects. The go command now verifies that ".syso" files, direct linker inputs, and libraries in "-L" directories are valid binary objects or archives that do not contain unallowlisted ".drectve" directives, "LCLINKEROPTION" load commands, or LTO IR sections, and disallows "-l:<filename>" and ":", "=", or path separators in "-l" flags.
Affected Software
Event History
Frequently Asked Questions
What conditions are needed for exploitation?
An attacker needs to cause a build to consume a malicious linker input, such as a .syso file, a direct object or library referenced through #cgo LDFLAGS, or a library found in a -L directory. The vulnerable behavior occurs when those inputs are passed to an external linker without format and embedded-option validation.
Which build inputs should be treated as untrusted or high risk?
Review .syso files, direct object and library inputs in #cgo LDFLAGS, and libraries resolved from -L directories. Also treat uses of -l:<filename> and -l values containing colons, equals signs, or path separators as unsafe under the corrected behavior.
What is the available mitigation if an update cannot be applied immediately?
Do not build with untrusted .syso files, object files, archives, or libraries supplied through cgo linker flags or -L directories. Restrict build inputs to validated binary objects or archives and reject inputs containing linker-script content, embedded linker options, or LTO intermediate-representation sections.