Summary
This update for go1.25-openssl fixes the following issues:
Update to version 1.25.0 cut from the go1.25-fips-release
branch at the revision tagged go1.25.0-1-openssl-fips.
( jsc#SLE-18320 )
* Rebase to 1.25.0
* Fix HKDF-Extract The latest OpenSSL in c9s/c10s requires nil
salt to be passed as a hash length buffer of zeros.
go1.25 (released 2025-08-12) is a major release of Go.
go1.25.x minor releases will be provided through August 2026.
https://github.com/golang/go/wiki/Go-Release-Cycle
go1.25 arrives six months after Go 1.24. Most of its changes are
in the implementation of the toolchain, runtime, and
libraries. As always, the release maintains the Go 1 promise of
compatibility. We expect almost all Go programs to continue to
compile and run as before.
( bsc#1244485 go1.25 release tracking )
* Language changes: There are no languages changes that affect Go
programs in Go 1.25. However, in the language specification the
notion of core types has been removed in favor of dedicated
prose. See the respective blog post for more information.
* go command: The go build -asan option now defaults to doing
leak detection at program exit. This will report an error if
memory allocated by C is not freed and is not referenced by any
other memory allocated by either C or Go. These new error
reports may be disabled by setting ASAN_OPTIONS=detect_leaks=0
in the environment when running the program.
* go command: The Go distribution will include fewer prebuilt
tool binaries. Core toolchain binaries such as the compiler and
linker will still be included, but tools not invoked by build
or test operations will be built and run by go tool as needed.
* go command: The new go.mod ignore directive can be used to
specify directories the go command should ignore. Files in
these directories and their subdirectories will be ignored by
the go command when matching package patterns, such as all or
./..., but will still be included in module zip files.
* go command: The new go doc -http option will start a
documentation server showing documentation for the requested
object, and open the documentation in a browser window.
* go command: The new go version -m -json option will print the
JSON encodings of the runtime/debug.BuildInfo structures
embedded in the given Go binary files.
* go command: The go command now supports using a subdirectory of
a repository as the path for a module root, when resolving a
module path using the syntax <meta name='go-import'
content='root-path vcs repo-url subdir'> to indicate that the
root-path corresponds to the subdir of the repo-url with
version control system vcs.
* go command: The new work package pattern matches all packages
in the work (formerly called main) modules: either the single
work module in module mode or the set of workspace modules in
workspace mode.
* go command: When the go command updates the go line in a go.mod
or go.work file, it no longer adds a toolchain line specifying
the command’s current version.
* go vet: The go vet command includes new analyzers:
* go vet: waitgroup reports misplaced calls to
sync.WaitGroup.Add;
* go vet: hostport reports uses of fmt.Sprintf('%s:%d', host,
port) to construct addresses for net.Dial, as these will not
work with IPv6; instead it suggests using net.JoinHostPort.
* Runtime: Container-aware GOMAXPROCS. The default behavior of
the GOMAXPROCS has changed. In prior versions of Go, GOMAXPROCS
defaults to the number of logical CPUs available at startup
(runtime.NumCPU). Go 1.25 introduces two changes: On Linux, the
runtime considers the CPU bandwidth limit of the cgroup
containing the process, if any. If the CPU bandwidth limit is
lower than the number of logical CPUs available, GOMAXPROCS
will default to the lower limit. In container runtime systems
like Kubernetes, cgroup CPU bandwidth limits generally
correspond to the “CPU limit” option. The Go runtime does not
consider the “CPU requests” option. On all OSes, the runtime
periodically updates GOMAXPROCS if the number of logical CPUs
available or the cgroup CPU bandwidth limit change. Both of
these behaviors are automatically disabled if GOMAXPROCS is set
manually via the GOMAXPROCS environment variable or a call to
runtime.GOMAXPROCS. They can also be disabled explicitly with
the GODEBUG settings containermaxprocs=0 and updatemaxprocs=0,
respectively. In order to support reading updated cgroup
limits, the runtime will keep cached file descriptors for the
cgroup files for the duration of the process lifetime.
* Runtime: garbage collector: A new garbage collector is now
available as an experiment. This garbage collector’s design
improves the performance of marking and scanning small objects
through better locality and CPU scalability. Benchmark result
vary, but we expect somewhere between a 10—40% reduction in
garbage collection overhead in real-world programs that heavily
use the garbage collector. The new garbage collector may be
enabled by setting GOEXPERIMENT=greenteagc at build time. We
expect the design to continue to evolve and improve. To that
end, we encourage Go developers to try it out and report back
their experiences. See the GitHub issue for more details on the
design and instructions for sharing feedback.
* Runtime: trace flight recorder: Runtime execution traces have
long provided a powerful, but expensive way to understand and
debug the low-level behavior of an application. Unfortunately,
because of their size and the cost of continuously writing an
execution trace, they were generally impractical for debugging
rare events. The new runtime/trace.FlightRecorder API provides
a lightweight way to capture a runtime execution trace by
continuously record
Fixed packages 3
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.6 | go1.25-openssl | 1.25.0-150600.13.3.1 |
| SUSE · SLES 15 SP6 Linux Enterprise Module for Development Tools 15 SP6 | go1.25-openssl | 1.25.0-150600.13.3.1 |
| SUSE · SLES 15 SP7 Linux Enterprise Module for Development Tools 15 SP7 | go1.25-openssl | 1.25.0-150600.13.3.1 |
Vulnerabilities 3
-
High 8.6
Unexpected command execution in untrusted VCS repositories in cmd/go
The go command may execute unexpected commands when operating in untrusted VCS repositories. This occurs when possibly dangerous VCS configuration is present in repositories. This can happen when a repository was fetched via one VCS (e.g. Git), but contains m…
-
High 7.0
Incorrect results returned from Rows.Scan in database/sql
Cancelling a query (e.g. by cancelling the context passed to one of the query methods) during a call to the Scan method of the returned Rows can result in unexpected results if other queries are being made in parallel. This can result in a race condition that…
-
Medium 6.5
Unexpected paths returned from LookPath in os/exec
If the PATH environment variable contains paths which are executables (rather than just directories), passing certain strings to LookPath ("", ".", and ".."), can result in the binaries listed in the PATH being unexpectedly returned.
References
-
report
https://bugzilla.suse.com/1244485
-
report
https://bugzilla.suse.com/1246118
-
report
https://bugzilla.suse.com/1247719
-
report
https://bugzilla.suse.com/1247720
-
report
https://bugzilla.suse.com/1247816
-
report
https://bugzilla.suse.com/1248082
-
web
https://www.suse.com/security/cve/CVE-2025-4674
-
web
https://www.suse.com/security/cve/CVE-2025-47906
-
web
https://www.suse.com/security/cve/CVE-2025-47907