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 r0763eca97daf (s390x; channels: 2.4-21.10_beta, 2.4-21.10_edge)
* libsepol1: 5391-1
Revision r163f41453761 (amd64; channels: 2.4-21.10_beta, 2.4-21.10_edge)
* libsepol1: 5391-1
Revision r78c7f8515178 (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libsepol1: 5391-1
Revision r7bd43bf799e4 (ppc64le; channels: 2.4-21.10_beta, 2.4-21.10_edge)
* libsepol1: 5391-1
Revision ra1fb8594b7d0 (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libsepol1: 5391-1
Revision rb8d0c9735b85 (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libsepol1: 5391-1
Revision reb63d1a6b907 (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libsepol1: 5391-1
Revision rf1edaa8d59ee (arm64; channels: 2.4-21.10_beta, 2.4-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/