PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-90128 Linux CVE debrief

A vulnerability in the Linux kernel's vdpa/mlx5 has been addressed, where the add_direct_chain error path incorrectly iterated over the wrong list, potentially leading to resource leaks or incorrect cleanup. This issue has been resolved by correcting the list iteration in the error path. The fix ensures proper cleanup and prevents potential resource leaks. Linux kernel developers and maintainers should verify patch application and assess exposure in Linux kernel versions using vdpa/mlx5.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-17
Original CVE updated
2026-10-19
Advisory published
2026-09-17
Advisory updated
2026-10-19

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux systems with vdpa/mlx5 functionality should be aware of this vulnerability. They should verify patch application, assess exposure in Linux kernel versions, and prioritize remediation accordingly. Linux kernel developers and maintainers should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Linux system  

Why it matters

CVE-2026-90128 is a vulnerability in the Linux kernel's vdpa/mlx5 that has been addressed. Defenders should verify patch application, assess exposure in Linux kernel versions, and prioritize remediation accordingly.

  • Verification of patch application is necessary to prevent potential resource leaks.
  • Defenders should assess exposure in Linux kernel versions using vdpa/mlx5.
  • Remediation priority is medium due to the specific conditions required for exploitation.

Technical summary

The Linux kernel's vdpa/mlx5 had a vulnerability where the add_direct_chain error path incorrectly iterated over the wrong list. This has been fixed by correcting the list iteration in the error path. The fix prevents potential resource leaks and ensures proper cleanup. The vulnerability was addressed by modifying the error path to iterate over the correct list, thereby preventing incorrect cleanup and resource leaks. Defenders should verify patch application and assess exposure in Linux kernel versions using vdpa/mlx5.

Defensive priority

Medium

Recommended defensive actions

  • Review Linux kernel versions and ensure they are up-to-date with the latest security patches.
  • Verify that affected systems have been patched with the corrected version.
  • Monitor system logs for potential resource leaks or incorrect cleanup related to vdpa/mlx5.
  • Perform a thorough review of the Linux kernel's vdpa/mlx5 to identify potential exposure.
  • Assess the operational impact of the vulnerability on Linux systems with vdpa/mlx5 functionality.
  • Prioritize remediation based on the specific conditions required for exploitation.
  • Track exceptions and retest remediated assets to ensure the vulnerability is fully resolved.

Evidence notes

The CVE Program record and NVD vulnerability detail provide official information about this vulnerability. Multiple source references from the Linux kernel Git repository confirm the fix for this issue.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-90128 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-90128

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-90128 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90128

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • vdpa/mlx5: fix wrong list iterated in add_direct_chain error path

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/90xxx/CVE-2026-90128.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c93defccf5eb0a92bdafa43487be6ce0221a2477

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/ed3462365636df3bc63e34d7468f4faed3f70a4e

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/22d52af9e26a72bdfe2dcfb1419a091de4862cd9

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/eeac2ea4ad2654e3f160a9b608d05c9af31433a6

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/637d867530daea61898e3346975978b7f67fc2ac

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6ca752850de3b8162f030793cc15001aec85c4cf

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c678d04ac9e5a64c2559c43bce273e845fbd09eb

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.