Bug 2392017

Summary:	CVE-2025-58160 bootc: Tracing log pollution [fedora-42]
Product:	[Fedora] Fedora	Reporter:	Jon Moroney <jmoroney>
Component:	bootc	Assignee:	Colin Walters <walters>
Status:	POST ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	42	CC:	ckyrouac, jeckersb, jmarrero, jonathan, walters
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["3da49126-4f35-455c-8753-2221da43a3db"]}
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2391963

Description Jon Moroney 2025-08-29 22:40:05 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams

Comment 1 Colin Walters 2025-09-02 13:57:57 UTC

This motivated me to fix our renovate setup, and this got fixed in https://github.com/bootc-dev/bootc/pull/1566

Comment 2 Colin Walters 2025-09-02 14:28:45 UTC

Note our tracing setup changed in https://github.com/bootc-dev/bootc/pull/1522/commits/bf74ecbcc3fdefeaab598cb3fb6d06d926691021

- We only logged messages at ERROR level or above before
- There's very little usage of tracing::error! in our code base, only a few hits
- Almost all input that is provided comes from privileged code anyways

Hence I don't think we need to do any special releases for this and can just roll the fix into our next scheduled release.

OR TL;DR I think bootc is not vulnerable to this.