linux-signed-i386_5.10.179+3_source.changes ACCEPTED into oldstable-proposed-updates
Thank you for your contribution to Debian.
Accepted:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 28 Jul 2023 00:17:15 +0200
Source: linux-signed-i386
Architecture: source
Version: 5.10.179+3
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Salvatore Bonaccorso <carnil@debian.org>
Changes:
linux-signed-i386 (5.10.179+3) bullseye-security; urgency=high
.
* Sign kernel from linux 5.10.179-3
.
[ Salvatore Bonaccorso ]
* [x86] microcode/AMD: Load late on both threads too
* [x86] cpu/amd: Move the errata checking functionality up
* [x86] cpu/amd: Add a Zenbleed fix (CVE-2023-20593)
* netfilter: nftables: statify nft_parse_register()
* netfilter: nf_tables: validate registers coming from userspace.
* netfilter: nf_tables: hold mutex on netns pre_exit path
* netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE
(CVE-2023-3390)
* Ignore ABI changes for nft_parse_register (dropped with 08a01c11a5bb
("netfilter: nftables: statify nft_parse_register()"))
.
[ Ben Hutchings ]
* netfilter: nf_tables: fix chain binding transaction logic (CVE-2023-3610)
Checksums-Sha1:
9aa4bd0d6ccf6ac64970e53f4968b5b34d49c16b 14265 linux-signed-i386_5.10.179+3.dsc
1ec6d31dbbc7fddf43b12bc9c78999d48fc7d783 3792896 linux-signed-i386_5.10.179+3.tar.xz
Checksums-Sha256:
8dc615ee9ca1afc9e256722ce4d0b799d6ae47953805c15b50a5e3a481a8cd0a 14265 linux-signed-i386_5.10.179+3.dsc
98fd137246bfc0e2150a5a45f96a1331ebeb6c11077b6ad16948ae024e3e4407 3792896 linux-signed-i386_5.10.179+3.tar.xz
Files:
4cd895ffcf0acf07b3b1735e40f0078f 14265 kernel optional linux-signed-i386_5.10.179+3.dsc
1b20bda1eb77eba0e3cfc0b25f654dbd 3792896 kernel optional linux-signed-i386_5.10.179+3.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmTFfl8ACgkQi0FRiLdO
NzZajRAAirEznp+2e8uZbb+n8BZN51LbtgLerZGZcvXEkAj2UZ3eF5RvaXm3BSCh
z8/NTHq8Ic1pFF4C73r6cL3uFHAOtNkZV0FgpUmNsC2Ap5fIW/7+zPi/cxJ1YaGm
tT8JErUinTjBkCcBVrEVh7QTr+kxKgEv7Kj9fOw3JHIBOgzLN9x8/YJ8Bs4arzng
ztbN/gxZpwRvKEpCQUgr2BaV3gyKMIpsGUkrBaEUmUtEZg7PXsKWn5om8tKehkRq
lGimOu1CQ2Lp6ENQxr3gyCJz9zK9EzEqGrfvmEkpXzGsi19suso+OMNdRK1AGFJG
dpPAk+ek/3Zuiic5rSNQnPou7a0BtyCV/sKH9pIfn5LRVwHj4J1ON49YZ12BRugr
6ygzAg9pbqAZIlZvprR8LiLdtW2Y7sF9IsHM0jOBKtxvliy/4Hf3p6i7snR6dQq+
VxVRK/ToHT4RxDpO9f+GBnEwDqGvQpPyeNyqedbZehFoo3zlAyfo7BOVDOhY8Rwk
nZgQSI+Ph1sE6n0T/t9yxIBCZBRZPypT5X/mE8uC7mfjTRqKY3UBN4H1NauEz18A
EuyQv7TxskBzxaQh1yNyHA8bZ4R8DghxMUhihTls99RmYD0p7I72HmOpp4B5dbwm
HXztCTj8aM3hI/f4uYHlqNEY4+uMLSzbqsAG3N7q3TcEfq3DI/0=
=S4An
-----END PGP SIGNATURE-----
Reply to: