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 r11dc303ab3a9 (arm64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libsepol1: 5391-1
Revision r36954a485e09 (amd64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libsepol1: 5391-1
Revision r5f61aae9a447 (s390x; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libsepol1: 5391-1
Revision r7f5b304d86ed (s390x; channels: 1.6-21.10_beta, 1.6-21.10_edge)
* libsepol1: 5391-1
Revision ra4748c47eadf (amd64; channels: 1.6-21.10_beta, 1.6-21.10_edge)
* libsepol1: 5391-1
Revision rae76df65a4d2 (ppc64le; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libsepol1: 5391-1
Revision rc8b21c29d948 (ppc64le; channels: 1.6-21.10_beta, 1.6-21.10_edge)
* libsepol1: 5391-1
Revision re3df88c0ff5c (arm64; channels: 1.6-21.10_beta, 1.6-21.10_edge)
* 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/