https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292778
--- Comment #4 from Lexi Winter <[email protected]> --- (In reply to Colin Percival from comment #3) > Can you provide a patch to > https://www.freebsd.org/security/advisory-template.txt which adds appropriate > content? i think i provided this to to@ in <[email protected]> (subject: Re: pkgbase wording for SA/EN) on 2025-12-18. i've copied the patch below in case it got lost. [-- Attachment #2: advisory-template.diff --] [-- Type: text/x-diff, Encoding: quoted-printable, Size: 1.3K --] Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename=advisory-template.diff Content-Transfer-Encoding: quoted-printable --- advisory-template.txt 2025-12-17 14:50:00 +++ advisory-template-pkgbase.txt 2025-12-18 22:57:35 @@ -57,17 +57,26 @@ Perform one of the following: -1) To update your vulnerable system via a binary patch: +1) To update your vulnerable system installed from base system packages: +Systems running a 15.0-RELEASE version of FreeBSD on the amd64 or arm64 +platforms, which were installed using base system packages, can be updated +via the pkg(8) utility: + +# pkg upgrade -r FreeBSD-base +# shutdown -r +10min "Rebooting for a security update" <XX if required> + +2) To update your vulnerable system installed from binary distribution sets: + Systems running a RELEASE version of FreeBSD on the amd64 or arm64 platforms, -or the i386 platform on FreeBSD 13, can be updated via the freebsd-update(8) -utility: +or the i386 platform on FreeBSD 13, which were not installed using base +system packages, can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for a security update" <XX if required> -2) To update your vulnerable system via a source code patch: +3) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. [-- End of signed data --] -- You are receiving this mail because: You are on the CC list for the bug.
