---
id: CVE-2025-68303
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  platform/x86: intel: punit_ipc: fix memory corruption

  This passes the address of the pointer "&punit_ipcdev" when the intent
  was to pass the pointer itself "punit_ipcd…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  platform/x86: intel: punit_ipc: fix memory corruption

  This passes the address of the pointer "&punit_ipcdev" when the intent
  was to pass the pointer itself "punit_ipcd…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
published: '2025-12-16'
updated: '2026-10-13'
sourceUpdated: '2026-10-13T19:10:00.193'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-68303'
references:
  - url: 'https://git.kernel.org/stable/c/15d560cdf5b36c51fffec07ac2a983ab3bff4cb2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/3e7442c5802146fd418ba3f68dcb9ca92b5cec83'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/46e9d6f54184573dae1dcbcf6685a572ba6f4480'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9b9c0adbc3f8a524d291baccc9d0c04097fb4869'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a21615a4ac6fecbb586d59fe2206b63501021789'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c2ee6d38996775a19bfdf20cb01a9b8698cb0baa'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00143
epssPercentile: 0.03151
ingestedAt: '2026-10-13T19:43:28.852Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

platform/x86: intel: punit_ipc: fix memory corruption

This passes the address of the pointer "&punit_ipcdev" when the intent
was to pass the pointer itself "punit_ipcdev" (without the ampersand).
This means that the:

	complete(&ipcdev->cmd_complete);

in intel_punit_ioc() will write to a wrong memory address corrupting it.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.