diff options
| author | Moritz Muehlenhoff <jmm@debian.org> | 2022-12-14 15:33:27 +0100 |
|---|---|---|
| committer | Moritz Muehlenhoff <jmm@debian.org> | 2022-12-14 15:33:27 +0100 |
| commit | fa9e50dfa2ecfe80ee04035b55d36bf33555cb2f (patch) | |
| tree | ab78ba97383bc1e4c5bc0d2e3a9174ab97156406 /active/CVE-2018-13095 | |
| parent | cfc5cef637a25d5c1d5c9b28932ff091f28754e5 (diff) | |
retire issues
Diffstat (limited to 'active/CVE-2018-13095')
| -rw-r--r-- | active/CVE-2018-13095 | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/active/CVE-2018-13095 b/active/CVE-2018-13095 deleted file mode 100644 index 46e10760..00000000 --- a/active/CVE-2018-13095 +++ /dev/null @@ -1,19 +0,0 @@ -Description: NULL pointer dereference in xfs_bmap_extents_to_btree() when mounting and operating a crafted image -References: - https://bugzilla.kernel.org/show_bug.cgi?id=199915 - https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/commit/?h=for-next&id=23fcb3340d033d9f081e21e6c12c2db7eaa541d3 -Notes: - bwh> Upstream fix depends on (at least) commit 71493b839e29 - bwh> "xfs: move inode fork verifiers to xfs_dinode_verify". I think - bwh> this is more trouble than it's worth to backport. -Bugs: -upstream: released (4.18-rc3) [23fcb3340d033d9f081e21e6c12c2db7eaa541d3] -5.10-upstream-stable: N/A "Fixed before branch point" -4.19-upstream-stable: N/A "Fixed before branch point" -4.9-upstream-stable: needed -3.16-upstream-stable: ignored "Too risky to backport" -sid: released (4.18.6-1) -5.10-bullseye-security: N/A "Fixed before branching point" -4.19-buster-security: N/A "Fixed before branching point" -4.9-stretch-security: ignored "EOL" -3.16-jessie-security: ignored "Too risky to backport" |