A scan of this rock shows that it was built with packages from the Ubuntu
archive that have since received security updates. The following lists new
USNs for affected binary packages in each rock revision:
Revision r1dcbe13d2e1a (ppc64le; channels: 6.0-21.10_edge, 6.0-21.10_beta)
* libsepol1: 5391-1
Revision r5a78aa9940d0 (amd64; channels: 6.0-21.10_edge, 6.0-21.10_beta)
* libsepol1: 5391-1
Revision r5fcd0996ce57 (s390x; channels: 6.0-21.10_edge, 6.0-21.10_beta)
* libsepol1: 5391-1
Revision r8b336bb6f03e (ppc64le; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* libsepol1: 5391-1
Revision r9948dfb20aa1 (amd64; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* libsepol1: 5391-1
Revision rb03007e03e41 (arm64; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* libsepol1: 5391-1
Revision rb39b2bdbaa1a (s390x; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* libsepol1: 5391-1
Revision rc86a40a49861 (arm64; channels: 6.0-21.10_edge, 6.0-21.10_beta)
* libsepol1: 5391-1
Simply rebuilding the rock will pull in the new security updates and
resolve this. If your rock also contains vendored code, now might be a
good time to review it for any needed updates.
Thank you for your rock and for attending to this matter.
References:
* https://ubuntu.com/security/notices/USN-5391-1/