summaryrefslogtreecommitdiffstats
path: root/ChangeLog.rss
diff options
context:
space:
mode:
Diffstat (limited to 'ChangeLog.rss')
-rw-r--r--ChangeLog.rss61
1 files changed, 59 insertions, 2 deletions
diff --git a/ChangeLog.rss b/ChangeLog.rss
index 4baf7bb5f..efb3d67b9 100644
--- a/ChangeLog.rss
+++ b/ChangeLog.rss
@@ -11,10 +11,67 @@
<description>Tracking Slackware development in git.</description>
<language>en-us</language>
<id xmlns="http://www.w3.org/2005/Atom">urn:uuid:c964f45e-6732-11e8-bbe5-107b4450212f</id>
- <pubDate>Thu, 16 Feb 2023 22:07:06 GMT</pubDate>
- <lastBuildDate>Fri, 17 Feb 2023 12:29:53 GMT</lastBuildDate>
+ <pubDate>Sat, 18 Feb 2023 02:04:34 GMT</pubDate>
+ <lastBuildDate>Sat, 18 Feb 2023 12:29:58 GMT</lastBuildDate>
<generator>maintain_current_git.sh v 1.17</generator>
<item>
+ <title>Sat, 18 Feb 2023 02:04:34 GMT</title>
+ <pubDate>Sat, 18 Feb 2023 02:04:34 GMT</pubDate>
+ <link>https://git.slackware.nl/current/tag/?h=20230218020434</link>
+ <guid isPermaLink="false">20230218020434</guid>
+ <description>
+ <![CDATA[<pre>
+patches/packages/kernel-firmware-20230214_a253a37-noarch-1.txz: Upgraded.
+patches/packages/linux-5.15.80/*: Upgraded.
+ These updates fix various bugs and security issues.
+ Be sure to upgrade your initrd after upgrading the kernel packages.
+ If you use lilo to boot your machine, be sure lilo.conf points to the correct
+ kernel and initrd and run lilo as root to update the bootloader.
+ If you use elilo to boot your machine, you should run eliloconfig to copy the
+ kernel and initrd to the EFI System Partition.
+ For more information, see:
+ Fixed in 5.15.81:
+ https://www.cve.org/CVERecord?id=CVE-2022-47519
+ https://www.cve.org/CVERecord?id=CVE-2022-47518
+ https://www.cve.org/CVERecord?id=CVE-2022-47520
+ https://www.cve.org/CVERecord?id=CVE-2022-47521
+ https://www.cve.org/CVERecord?id=CVE-2022-3344
+ Fixed in 5.15.82:
+ https://www.cve.org/CVERecord?id=CVE-2022-45869
+ https://www.cve.org/CVERecord?id=CVE-2022-4378
+ Fixed in 5.15.83:
+ https://www.cve.org/CVERecord?id=CVE-2022-3643
+ Fixed in 5.15.84:
+ https://www.cve.org/CVERecord?id=CVE-2022-3545
+ Fixed in 5.15.85:
+ https://www.cve.org/CVERecord?id=CVE-2022-45934
+ Fixed in 5.15.86:
+ https://www.cve.org/CVERecord?id=CVE-2022-3534
+ https://www.cve.org/CVERecord?id=CVE-2022-3424
+ Fixed in 5.15.87:
+ https://www.cve.org/CVERecord?id=CVE-2022-41218
+ https://www.cve.org/CVERecord?id=CVE-2023-23455
+ https://www.cve.org/CVERecord?id=CVE-2023-23454
+ https://www.cve.org/CVERecord?id=CVE-2023-0045
+ https://www.cve.org/CVERecord?id=CVE-2023-0210
+ https://www.cve.org/CVERecord?id=CVE-2022-36280
+ Fixed in 5.15.88:
+ https://www.cve.org/CVERecord?id=CVE-2023-0266
+ https://www.cve.org/CVERecord?id=CVE-2022-47929
+ Fixed in 5.15.89:
+ https://www.cve.org/CVERecord?id=CVE-2023-0179
+ https://www.cve.org/CVERecord?id=CVE-2023-0394
+ Fixed in 5.15.90:
+ https://www.cve.org/CVERecord?id=CVE-2022-4382
+ https://www.cve.org/CVERecord?id=CVE-2022-4842
+ Fixed in 5.15.91:
+ https://www.cve.org/CVERecord?id=CVE-2022-4129
+ https://www.cve.org/CVERecord?id=CVE-2023-23559
+ (* Security fix *)
+ </pre>]]>
+ </description>
+ </item>
+ <item>
<title>Thu, 16 Feb 2023 22:07:06 GMT</title>
<pubDate>Thu, 16 Feb 2023 22:07:06 GMT</pubDate>
<link>https://git.slackware.nl/current/tag/?h=20230216220706</link>