ALSA-2026:96083 (CVE-2026-100236)

Vulnerability from osv_almalinux – Published: 2026-11-09 00:00 – Updated: 2026-11-09 09:15 – Source website
VLAI
Summary
Important: dpdk security update
Details

The dpdk packages provide the Data Plane Development Kit, which is a set of libraries and drivers for fast packet processing in the user space.

Security Fix(es):

  • dpdk: dpdk: Missing memory size validation before mmap in vhost memory region setup (CVE-2026-86561)
  • dpdk: dpdk: Control-queue descriptor double-fetch overflows host heap in DPDK vhost (VDUSE) (CVE-2026-86562)
  • dpdk: dpdk: Double offset bug in vhost log mapping calculation (CVE-2026-86563)
  • dpdk: dpdk: Guest can desynchronize virtqueue size from inflight descriptor table size, causing out-of-bounds write (CVE-2026-86565)
  • dpdk: dpdk: Guest with runt RX descriptors underflows copy length in vhost enqueue (split and packed rings) (CVE-2026-86566)
  • dpdk: dpdk: VDUSE handler fails to invalidate vring pointers when IOTLB is invalidated, leading to use-after-unmap (CVE-2026-86567)
  • dpdk: dpdk: Guest-triggered use-after-free and type confusion in vhost-crypto session cleanup (CVE-2026-86845)
  • dpdk: dpdk: Guest can trigger out-of-bounds write by controlling avail ring index in vhost-crypto (CVE-2026-86846)
  • dpdk: dpdk: Guest can trigger infinite loop in vhost-crypto writeback chain cleanup (CVE-2026-86847)
  • dpdk: dpdk: Time-of-check/time-of-use vulnerability allowing guest-triggered out-of-bounds write in vhost-crypto (CVE-2026-86848)
  • dpdk: dpdk: Integer overflow combined with missing validation leads to host buffer overflow in vhost-crypto (CVE-2026-86849)
  • dpdk: dpdk: Stack and heap buffer overflow in nfp vDPA driver (CVE-2026-86856)
  • dpdk: dpdk: Guest-triggered out-of-bounds walk via vhost indirect descriptor length TOCTOU (CVE-2026-93683)
  • dpdk: dpdk: heap out-of-bounds read/write in GSO header copy (CVE-2026-100236)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

References
https://access.redhat.com/errata/RHSA-2026:96083 ADVISORY
https://access.redhat.com/security/cve/CVE-2026-100236 REPORT
https://access.redhat.com/security/cve/CVE-2026-86561 REPORT
https://access.redhat.com/security/cve/CVE-2026-86562 REPORT
https://access.redhat.com/security/cve/CVE-2026-86563 REPORT
https://access.redhat.com/security/cve/CVE-2026-86565 REPORT
https://access.redhat.com/security/cve/CVE-2026-86566 REPORT
https://access.redhat.com/security/cve/CVE-2026-86567 REPORT
https://access.redhat.com/security/cve/CVE-2026-86845 REPORT
https://access.redhat.com/security/cve/CVE-2026-86846 REPORT
https://access.redhat.com/security/cve/CVE-2026-86847 REPORT
https://access.redhat.com/security/cve/CVE-2026-86848 REPORT
https://access.redhat.com/security/cve/CVE-2026-86849 REPORT
https://access.redhat.com/security/cve/CVE-2026-86856 REPORT
https://access.redhat.com/security/cve/CVE-2026-93683 REPORT
https://bugzilla.redhat.com/2529666 REPORT
https://bugzilla.redhat.com/2529667 REPORT
https://bugzilla.redhat.com/2529668 REPORT
https://bugzilla.redhat.com/2529683 REPORT
https://bugzilla.redhat.com/2529684 REPORT
https://bugzilla.redhat.com/2529685 REPORT
https://bugzilla.redhat.com/2529844 REPORT
https://bugzilla.redhat.com/2529846 REPORT
https://bugzilla.redhat.com/2529847 REPORT
https://bugzilla.redhat.com/2529853 REPORT
https://bugzilla.redhat.com/2529858 REPORT
https://bugzilla.redhat.com/2529897 REPORT
https://bugzilla.redhat.com/2537015 REPORT
https://bugzilla.redhat.com/2541488 REPORT
https://errata.almalinux.org/8/ALSA-2026-96083.html ADVISORY
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "AlmaLinux:8",
        "name": "dpdk"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "23.11-3.el8_10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "AlmaLinux:8",
        "name": "dpdk-devel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "23.11-3.el8_10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "AlmaLinux:8",
        "name": "dpdk-doc"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "23.11-3.el8_10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "AlmaLinux:8",
        "name": "dpdk-tools"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "23.11-3.el8_10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "The dpdk packages provide the Data Plane Development Kit, which is a set of libraries and drivers for fast packet processing in the user space.  \n\nSecurity Fix(es):  \n\n  * dpdk: dpdk: Missing memory size validation before mmap in vhost memory region setup (CVE-2026-86561)\n  * dpdk: dpdk: Control-queue descriptor double-fetch overflows host heap in DPDK vhost (VDUSE) (CVE-2026-86562)\n  * dpdk: dpdk: Double offset bug in vhost log mapping calculation (CVE-2026-86563)\n  * dpdk: dpdk: Guest can desynchronize virtqueue size from inflight descriptor table size, causing out-of-bounds write (CVE-2026-86565)\n  * dpdk: dpdk: Guest with runt RX descriptors underflows copy length in vhost enqueue (split and packed rings) (CVE-2026-86566)\n  * dpdk: dpdk: VDUSE handler fails to invalidate vring pointers when IOTLB is invalidated, leading to use-after-unmap (CVE-2026-86567)\n  * dpdk: dpdk: Guest-triggered use-after-free and type confusion in vhost-crypto session cleanup (CVE-2026-86845)\n  * dpdk: dpdk: Guest can trigger out-of-bounds write by controlling avail ring index in vhost-crypto (CVE-2026-86846)\n  * dpdk: dpdk: Guest can trigger infinite loop in vhost-crypto writeback chain cleanup (CVE-2026-86847)\n  * dpdk: dpdk: Time-of-check/time-of-use vulnerability allowing guest-triggered out-of-bounds write in vhost-crypto (CVE-2026-86848)\n  * dpdk: dpdk: Integer overflow combined with missing validation leads to host buffer overflow in vhost-crypto (CVE-2026-86849)\n  * dpdk: dpdk: Stack and heap buffer overflow in nfp vDPA driver (CVE-2026-86856)\n  * dpdk: dpdk: Guest-triggered out-of-bounds walk via vhost indirect descriptor length TOCTOU (CVE-2026-93683)\n  * dpdk: dpdk: heap out-of-bounds read/write in GSO header copy (CVE-2026-100236)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n",
  "id": "ALSA-2026:96083",
  "modified": "2026-11-09T09:15:20Z",
  "published": "2026-11-09T00:00:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://access.redhat.com/errata/RHSA-2026:96083"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-100236"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86561"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86562"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86563"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86565"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86566"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86567"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86845"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86846"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86847"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86848"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86849"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86856"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-93683"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529666"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529667"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529668"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529683"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529684"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529685"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529844"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529846"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529847"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529853"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529858"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2529897"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2537015"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2541488"
    },
    {
      "type": "ADVISORY",
      "url": "https://errata.almalinux.org/8/ALSA-2026-96083.html"
    }
  ],
  "related": [
    "CVE-2026-100236",
    "CVE-2026-86561",
    "CVE-2026-86562",
    "CVE-2026-86563",
    "CVE-2026-86565",
    "CVE-2026-86566",
    "CVE-2026-86567",
    "CVE-2026-86845",
    "CVE-2026-86846",
    "CVE-2026-86847",
    "CVE-2026-86848",
    "CVE-2026-86849",
    "CVE-2026-86856",
    "CVE-2026-93683"
  ],
  "schema_version": "1.7.0",
  "summary": "Important: dpdk security update",
  "upstream": [
    "CVE-2026-100236",
    "CVE-2026-86561",
    "CVE-2026-86562",
    "CVE-2026-86563",
    "CVE-2026-86565",
    "CVE-2026-86566",
    "CVE-2026-86567",
    "CVE-2026-86845",
    "CVE-2026-86846",
    "CVE-2026-86847",
    "CVE-2026-86848",
    "CVE-2026-86849",
    "CVE-2026-86856",
    "CVE-2026-93683"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.