diff options
| author | Salvatore Bonaccorso <carnil@debian.org> | 2024-03-15 21:45:18 +0100 |
|---|---|---|
| committer | Salvatore Bonaccorso <carnil@debian.org> | 2024-03-15 21:45:18 +0100 |
| commit | 64a38df8b392033c012ab5b8b6bf22aa84f652f8 (patch) | |
| tree | 990e39fd16081733df367f7e06259e0dbafb8fb2 /active/CVE-2021-47113 | |
| parent | 8cdf38b8945b5e6fa0554d35eab20a73aa23425c (diff) | |
Add new batch of CVEs
One source of problem for the automatic processing was the following
manual fixup:
- detection of N/A in case the version never affected a unstable
released version and so the sid: field should be N/A "Vulnerable code
not present"
- The second manual fixup is where 5.14.6-1 was placed as fixed version
for sid, as it should have been 5.10.46-1 as this is before the
branching point. There is no such support of tracking branching points
yet so it seems to cause fallouts on the recent CVEs assigned by
importing the issues from the GSD.
Diffstat (limited to 'active/CVE-2021-47113')
| -rw-r--r-- | active/CVE-2021-47113 | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/active/CVE-2021-47113 b/active/CVE-2021-47113 new file mode 100644 index 000000000..d5bccfcbc --- /dev/null +++ b/active/CVE-2021-47113 @@ -0,0 +1,15 @@ +Description: btrfs: abort in rename_exchange if we fail to insert the second ref +References: +Notes: + carnil> First introducing commit could not be determined. +Bugs: +upstream: released (5.13-rc5) [dc09ef3562726cd520c8338c1640872a60187af5] +6.7-upstream-stable: N/A "Fixed before branching point" +6.6-upstream-stable: N/A "Fixed before branching point" +6.1-upstream-stable: N/A "Fixed before branching point" +5.10-upstream-stable: released (5.10.43) [0df50d47d17401f9f140dfbe752a65e5d72f9932] +4.19-upstream-stable: needed +sid: released (5.10.46-1) +6.1-bookworm-security: N/A "Fixed before branching point" +5.10-bullseye-security: N/A "Fixed before branching point" +4.19-buster-security: needed |