p PatchFirst

CVE-2021-28692

CVE-2021-28692

This page contains facts from public vulnerability sources. Check the original advisory before updating.

inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.

CVSS 7.1 · High · EPSS 0.3% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • xen

    Versions
    • 4.13.x: Affected

    No fix published

  • xen

    Versions
    • 4.14.x: Affected

    No fix published

  • xen

    Versions
    • 4.15.x: Affected

    No fix published

  • xen

    Versions
    • xen-unstable: Affected

    No fix published

  • xen

    Versions
    • 4.12.x: Affected

    No fix published

  • xen

    Versions
    • 4.11.x: Affected

    No fix published

  • xen Debian:12

    Affected ranges
    • ECOSYSTEM: < 4.14.2+25-gb6a8c4f72d-1

    Update to 4.14.2+25-gb6a8c4f72d-1

  • xen Debian:13

    Affected ranges
    • ECOSYSTEM: < 4.14.2+25-gb6a8c4f72d-1

    Update to 4.14.2+25-gb6a8c4f72d-1

  • xen Debian:14

    Affected ranges
    • ECOSYSTEM: < 4.14.2+25-gb6a8c4f72d-1

    Update to 4.14.2+25-gb6a8c4f72d-1

  • xen Ubuntu:16.04:LTS

    Versions
    • 4.5.1-0ubuntu1
    • 4.5.1-0ubuntu2
    • 4.6.0-1ubuntu1
    • 4.6.0-1ubuntu2
    • 4.6.0-1ubuntu4
    • 4.6.0-1ubuntu4.1
    • 4.6.0-1ubuntu4.2
    • 4.6.0-1ubuntu4.3
    • 4.6.5-0ubuntu1
    • 4.6.5-0ubuntu1.1
    • 4.6.5-0ubuntu1.2
    • 4.6.5-0ubuntu1.4
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:18.04:LTS

    Versions
    • 4.9.0-0ubuntu3
    • 4.9.0-0ubuntu4
    • 4.9.2-0ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:20.04:LTS

    Versions
    • 4.9.2-0ubuntu2
    • 4.9.2-0ubuntu6
    • 4.9.2-0ubuntu7
    • 4.11.3+24-g14b62ab3e5-1ubuntu1
    • 4.11.3+24-g14b62ab3e5-1ubuntu2
    • 4.11.3+24-g14b62ab3e5-1ubuntu2.2
    • 4.11.3+24-g14b62ab3e5-1ubuntu2.3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:22.04:LTS

    Versions
    • 4.11.4+24-gddaaccbbab-1ubuntu2
    • 4.16.0-1~ubuntu2
    • 4.16.0-1~ubuntu2.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:24.04:LTS

    Versions
    • 4.17.2-1
    • 4.17.2+55-g0b56bed864-1
    • 4.17.2+76-ge1f9cb16e2-1
    • 4.17.2+76-ge1f9cb16e2-1ubuntu1
    • 4.17.3+10-g091466ba55-1
    • 4.17.3+10-g091466ba55-1.1ubuntu2
    • 4.17.3+10-g091466ba55-1.1ubuntu3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:25.10

    Versions
    • 4.20.0-1ubuntu1
    • 4.20.0+68-g35cb38b222-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:26.10

    Versions
    • 4.20.2+7-g1badcf5035-2build2
    • 4.20.2+37-g61ff35323e-1ubuntu1
    • 4.20.3+127-gc42374a105-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:26.04:LTS

    Versions
    • 4.20.0+68-g35cb38b222-1
    • 4.20.2+7-g1badcf5035-2
    • 4.20.2+7-g1badcf5035-2build2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →