From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 2/2] migration-guides: use new cve_mitre macro
Date: Wed, 24 May 2023 19:27:24 +0200 [thread overview]
Message-ID: <20230524172724.393781-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230524172724.393781-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/migration-guides/release-notes-4.0.7.rst | 4 ++--
documentation/migration-guides/release-notes-4.1.3.rst | 4 ++--
documentation/migration-guides/release-notes-4.2.rst | 6 +++---
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/documentation/migration-guides/release-notes-4.0.7.rst b/documentation/migration-guides/release-notes-4.0.7.rst
index 9e8ad51a0c..c3885d9e0e 100644
--- a/documentation/migration-guides/release-notes-4.0.7.rst
+++ b/documentation/migration-guides/release-notes-4.0.7.rst
@@ -7,7 +7,7 @@ Security Fixes in Yocto-4.0.7
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- binutils: Fix :cve:`2022-4285`
-- curl: Fix :cve:`2022-43551` and `CVE-2022-43552 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-43552>`__
+- curl: Fix :cve:`2022-43551` and :cve_mitre:`2022-43552`
- ffmpeg: Fix :cve:`2022-3109` and :cve:`2022-3341`
- go: Fix :cve:`2022-41715` and :cve:`2022-41717`
- libX11: Fix :cve:`2022-3554` and :cve:`2022-3555`
@@ -24,7 +24,7 @@ Security Fixes in Yocto-4.0.7
- sqlite: Fix :cve:`2022-46908`
- systemd: Fix :cve:`2022-45873`
- vim: Fix :cve:`2023-0049`, :cve:`2023-0051`, :cve:`2023-0054` and :cve:`2023-0088`
-- webkitgtk: Fix :cve:`2022-32886`, `CVE-2022-32891 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32891>`__ and :cve:`2022-32912`
+- webkitgtk: Fix :cve:`2022-32886`, :cve_mitre:`2022-32891` and :cve:`2022-32912`
Fixes in Yocto-4.0.7
diff --git a/documentation/migration-guides/release-notes-4.1.3.rst b/documentation/migration-guides/release-notes-4.1.3.rst
index 16e0a40426..d8474cda68 100644
--- a/documentation/migration-guides/release-notes-4.1.3.rst
+++ b/documentation/migration-guides/release-notes-4.1.3.rst
@@ -24,8 +24,8 @@ Security Fixes in Yocto-4.1.3
- sudo: Fix :cve:`2023-22809`
- tar: Fix :cve:`2022-48303`
- vim: Fix :cve:`2023-0049`, :cve:`2023-0051`, :cve:`2023-0054`, :cve:`2023-0288`, :cve:`2023-0433` and :cve:`2023-0512`
-- xserver-xorg: Fix `CVE-2023-0494 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0494>`__
-- xwayland: Fix `CVE-2023-0494 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0494>`__
+- xserver-xorg: Fix :cve_mitre:`2023-0494`
+- xwayland: Fix :cve_mitre:`2023-0494`
Fixes in Yocto-4.1.3
diff --git a/documentation/migration-guides/release-notes-4.2.rst b/documentation/migration-guides/release-notes-4.2.rst
index 27d51a574a..653602f152 100644
--- a/documentation/migration-guides/release-notes-4.2.rst
+++ b/documentation/migration-guides/release-notes-4.2.rst
@@ -348,7 +348,7 @@ The following corrections have been made to the :term:`LICENSE` values set by re
Security Fixes in 4.2
~~~~~~~~~~~~~~~~~~~~~
-- binutils: :cve:`2022-4285`, `CVE-2023-25586 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-25586>`__
+- binutils: :cve:`2022-4285`, :cve_mitre:`2023-25586`
- curl: :cve:`2022-32221`, :cve:`2022-35260`, :cve:`2022-42915`, :cve:`2022-42916`
- epiphany: :cve:`2023-26081`
- expat: :cve:`2022-43680`
@@ -356,7 +356,7 @@ Security Fixes in 4.2
- git: :cve:`2022-39260`, :cve:`2022-41903`, :cve:`2022-23521`, :cve:`2022-41953` (ignored)
- glibc: :cve:`2023-25139` (ignored)
- go: :cve:`2023-24532`, :cve:`2023-24537`
-- grub2: :cve:`2022-2601`, :cve:`2022-3775`, `CVE-2022-28736 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28736>`__
+- grub2: :cve:`2022-2601`, :cve:`2022-3775`, :cve_mitre:`2022-28736`
- inetutils: :cve:`2019-0053`
- less: :cve:`2022-46663`
- libarchive: :cve:`2022-36227`
@@ -368,7 +368,7 @@ Security Fixes in 4.2
- openssl: :cve:`2022-3358`, :cve:`2022-3786`, :cve:`2022-3602`, :cve:`2022-3996`, :cve:`2023-0286`, :cve:`2022-4304`, :cve:`2022-4203`, :cve:`2023-0215`, :cve:`2022-4450`, :cve:`2023-0216`, :cve:`2023-0217`, :cve:`2023-0401`, :cve:`2023-0464`
- ppp: :cve:`2022-4603`
- python3-cryptography{-vectors}: :cve:`2022-3602`, :cve:`2022-3786`, :cve:`2023-23931`
-- python3: `CVE-2022-37460 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37460>`__
+- python3: :cve_mitre:`2022-37460`
- qemu: :cve:`2022-3165`
- rust: :cve:`2022-46176`
- rxvt-unicode: :cve:`2022-4170`
--
2.34.1
prev parent reply other threads:[~2023-05-24 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 17:27 [PATCH 1/2] conf.py: add macro for Mitre CVE links michael.opdenacker
2023-05-24 17:27 ` michael.opdenacker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230524172724.393781-2-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox