CVE and update status of the FreeBSD ports tree4,826 unaddressed CVEs in 618 portsAll times are CET

CVE details

CVE-2023-6693

A stack based buffer overflow was found in the virtio-net device of QEMU. This issue occurs when flushing TX in the virtio_net_flush_tx function if guest features VIRTIO_NET_F_HASH_REPORT, VIRTIO_F_VERSION_1 and VIRTIO_NET_F_MRG_RXBUF are enabled. This could allow a malicious user to overwrite local variables allocated on the stack. Specifically, the `out_sg` variable could be used to read a part of process memory and send it to the wire, causing an information leak.

Score
4.9 medium
Published
2024-01-02
Links
NVD · cve.org

Affected ports (2)

PortPackageVersionStatusMaintainer
emulators/qemu-cheriqemu-cheri0.d20260108unaddressedbrooks@FreeBSD.org
emulators/qemu-user-staticqemu-user-static3.1.0_16unaddressedemulation@FreeBSD.org

Template for a VuXML entry

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>qemu-cheri</name>
	<range><lt>8.2.1</lt></range>
      </package>
      <package>
	<name>qemu-user-static</name>
	<range><lt>8.2.1</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>A stack based buffer overflow was found in the virtio-net device of
	QEMU. This issue occurs when flushing TX in the virtio_net_flush_tx
	function if guest features VIRTIO_NET_F_HASH_REPORT,
	VIRTIO_F_VERSION_1 and VIRTIO_NET_F_MRG_RXBUF are enabled. This could
	allow a malicious user to overwrite local variables allocated on the
	stack. Specifically, the `out_sg` variable could be used to read a
	part of process memory and send it to the wire, causing an information
	leak.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2023-6693</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2023-6693</url>
    </references>
    <dates>
      <discovery>2024-01-02</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>