PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-97899 Linux CVE debrief

A memory leak vulnerability has been identified in the Linux kernel's drm/i915 component. Specifically, the query_perf_config_list() function fails to free the original oa_config_ids when krealloc() fails, leading to a memory leak. This issue has been resolved through a commit that ensures proper memory management. The vulnerability affects Linux kernel developers and maintainers who use the drm/i915 component. The issue requires patching to prevent potential memory leaks. The CVE record and source references indicate a memory leak vulnerability in the Linux kernel's drm/i915 component.

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

Who should care

Linux kernel developers and maintainers, as well as users of the drm/i915 component, should be aware of this vulnerability and apply the patch to prevent potential memory leaks. The vulnerability affects Linux kernel developers and maintainers who use the drm/i915 component. Affected operator, platform, vulnerability-management, and security-team impact should be considered.

Why it matters

A memory leak vulnerability in the Linux kernel's drm/i915 component requires patching to prevent potential issues. Linux kernel developers and maintainers should be aware of this vulnerability and apply the patch.

  • Memory leak vulnerability requires patching to prevent potential denial-of-service (DoS) or information disclosure.
  • Successful exploitation requires specific conditions to be met, and the impact is currently unknown.

Technical summary

The query_perf_config_list() function in the Linux kernel's drm/i915 component has a memory leak vulnerability. When krealloc() fails, the original oa_config_ids are not freed, leading to a memory leak. This issue has been resolved through a commit that ensures proper memory management. The vulnerability requires specific conditions to be met and has been patched. Linux kernel developers and maintainers should be aware of this vulnerability and apply the patch to prevent potential memory leaks. The issue is related to the drm/i915 component and requires patching to prevent potential denial-of-service (DoS) or information disclosure.

Defensive priority

Low priority, as the vulnerability requires specific conditions to be met and has been patched.

Recommended defensive actions

  • Review and apply the patch to ensure the memory leak is fixed.
  • Monitor the Linux kernel and drm/i915 component for any related updates or advisories.
  • Perform regular vulnerability assessments to identify potential issues.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and source references indicate a memory leak vulnerability in the Linux kernel's drm/i915 component. The issue has been patched, and the CVE record provides links to the relevant commits.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-97899 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-97899 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

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

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/59e0a04d95e160547065ab3704bd809ddf3f0e1e

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/9ac6db531abe98adfd395fea25c00fee37de8154

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

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

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

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

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

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.