CVE Status: Difference between revisions
RossBurton (talk | contribs) mNo edit summary |
RossBurton (talk | contribs) mNo edit summary |
||
| Line 16: | Line 16: | ||
Hypothetical DoS. A patch [https://dev.gnupg.org/D556 was proposed] but hasn't been reviewed or merged. | Hypothetical DoS. A patch [https://dev.gnupg.org/D556 was proposed] but hasn't been reviewed or merged. | ||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 CVE-2022-0400] (linux-yocto) === | |||
Out-of-bounds read in the SMC stack. Details are still embargoed so can't tell what this actually impacts. | |||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 CVE-2022-1247] (linux-yocto) === | |||
Race in the X.25 AF_ROSE implementation, so only an issue if <tt>CONFIG_ROSE</tt> is enabled. | |||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 CVE-2022-4543] (linux-yocto) === | |||
aka EntryBleed. Vulnerable on x86-64 systems. | |||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 CVE-2022-33065] (libsndfile1) === | === [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 CVE-2022-33065] (libsndfile1) === | ||
Integer overflow, [https://github.com/libsndfile/libsndfile/issues/789 still open upstream]. | Integer overflow, [https://github.com/libsndfile/libsndfile/issues/789 still open upstream]. | ||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 CVE-2022-36402] (linux-yocto) === | |||
Bug in vmwgfx driver, still open. Mitigated if CONFIG_DRM_VMWGFX is not enabled. | |||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 CVE-2022-38096] (linux-yocto) === | |||
Bug in vmwgfx driver, still open. Mitigated if CONFIG_DRM_VMWGFX is not enabled. | |||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 CVE-2022-46456] (nasm) === | === [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 CVE-2022-46456] (nasm) === | ||
| Line 29: | Line 49: | ||
Bad CPE, should be marked as fixed in 2.38. Emailed NIST, data not updated yet. | Bad CPE, should be marked as fixed in 2.38. Emailed NIST, data not updated yet. | ||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 CVE-2023-1386] (qemu) === | === [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 CVE-2023-1386] (qemu) === | ||
| Line 48: | Line 65: | ||
[https://gitlab.com/qemu-project/qemu/-/commit/10be627d2b5ec2d6b3dce045144aa739eef678b4 Fixed] in 8.1.0. | [https://gitlab.com/qemu-project/qemu/-/commit/10be627d2b5ec2d6b3dce045144aa739eef678b4 Fixed] in 8.1.0. | ||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 CVE-2023-3640] (linux-yocto) === | === [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 CVE-2023-3640] (linux-yocto) === | ||
| Line 99: | Line 86: | ||
Merged in 3044b16e7c6fe5d24b1cdbcf1bd0a9d92d1ebd81, needs backporting. | Merged in 3044b16e7c6fe5d24b1cdbcf1bd0a9d92d1ebd81, needs backporting. | ||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 CVE-2023-4135] (qemu) === | |||
[https://gitlab.com/qemu-project/qemu/-/commit/ecb1b7b082d3b7dceff0e486a114502fc52c0fdf Fixed] in 8.1.0. | |||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 CVE-2023-37769] (pixman) === | |||
Appears to be a floating point exception in a test, should verify that the crash is in the test code and not the library. [https://gitlab.freedesktop.org/pixman/pixman/-/issues/76 This ticket] has the details. | |||
=== [https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 CVE-2023-40360] (qemu) === | |||
[https://gitlab.com/qemu-project/qemu/-/commit/6c8f8456cb0b239812dee5211881426496da7b98 Fixed] in 8.1.0. | |||
<!-- | <!-- | ||
Revision as of 15:02, 4 September 2023
This is a list of CVEs which are currently being reported as open, and the current state.
CVE-2019-14899 (linux-yocto)
Claims to be about breaking into VPN tunnels. OpenVPN dispute, Red Hat think it might actually have a larger scope but also the paper is misleading.
CVE-2021-3714 (linux-yocto)
Flaw in kernel memory de-duplication. Still an issue, albeit minor.
CVE-2021-3864 (linux-yocto)
Issue with suid binaries and coredumps. Last known progress on mitigating was this thread.
CVE-2022-3219 (gnupg)
Hypothetical DoS. A patch was proposed but hasn't been reviewed or merged.
CVE-2022-0400 (linux-yocto)
Out-of-bounds read in the SMC stack. Details are still embargoed so can't tell what this actually impacts.
CVE-2022-1247 (linux-yocto)
Race in the X.25 AF_ROSE implementation, so only an issue if CONFIG_ROSE is enabled.
CVE-2022-4543 (linux-yocto)
aka EntryBleed. Vulnerable on x86-64 systems.
CVE-2022-33065 (libsndfile1)
Integer overflow, still open upstream.
CVE-2022-36402 (linux-yocto)
Bug in vmwgfx driver, still open. Mitigated if CONFIG_DRM_VMWGFX is not enabled.
CVE-2022-38096 (linux-yocto)
Bug in vmwgfx driver, still open. Mitigated if CONFIG_DRM_VMWGFX is not enabled.
CVE-2022-46456 (nasm)
Buffer overflow, still open upstream.
CVE-2023-0687 (glibc)
Bad CPE, should be marked as fixed in 2.38. Emailed NIST, data not updated yet.
CVE-2023-1386 (qemu)
Still open upstream.
CVE-2023-3019 (qemu)
Linked patches need rebasing and review.
CVE-2023-3180 (qemu)
Fixed in 8.1.0.
CVE-2023-3354 (qemu)
Fixed in 8.1.0.
CVE-2023-3640 (linux-yocto)
CPU-level address leak specific to x86, still an issue.
CVE-2023-3772 (linux-yocto)
Merged in 00374d9b6d9f932802b55181be9831aa948e5b7c, needs backport.
CVE-2023-3773 (linux-yocto)
Merged in 5e2424708da7207087934c5c75211e8584d553a0, needs backport.
CVE-2023-4010 (linux-yocto)
Hang in USB subsystem. No fix yet.
CVE-2023-4128 (linux-yocto)
Merged in 3044b16e7c6fe5d24b1cdbcf1bd0a9d92d1ebd81, needs backporting.
CVE-2023-4135 (qemu)
Fixed in 8.1.0.
CVE-2023-37769 (pixman)
Appears to be a floating point exception in a test, should verify that the crash is in the test code and not the library. This ticket has the details.
CVE-2023-40360 (qemu)
Fixed in 8.1.0.
