Linux Kernel up to 6.17.10 intel_punit_ioc memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.15.196/6.1.158/6.6.118/6.12.60/6.17.10. Impacted is the function intel_punit_ioc. The manipulation leads to memory corruption. This vulnerability is traded as CVE-2025-68303. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.15.196/6.1.158/6.6.118/6.12.60/6.17.10. It has been rated as critical. This issue affects the function intel_punit_ioc. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-68303 since 12/16/2025. The exploitation is known to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/22/2026).

The vulnerability scanner Nessus provides a plugin with the ID 298924 (SUSE SLES12 : Recommended update for initial livepatch (SUSE-SU-2026:0473-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.15.197, 6.1.159, 6.6.119, 6.12.61 or 6.17.11 eliminates this vulnerability. Applying the patch 15d560cdf5b36c51fffec07ac2a983ab3bff4cb2/46e9d6f54184573dae1dcbcf6685a572ba6f4480/3e7442c5802146fd418ba3f68dcb9ca92b5cec83/a21615a4ac6fecbb586d59fe2206b63501021789/c2ee6d38996775a19bfdf20cb01a9b8698cb0baa/9b9c0adbc3f8a524d291baccc9d0c04097fb4869 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (298924) and CERT Bund (WID-SEC-2025-2868). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 298924
Nessus Name: SUSE SLES12 : Recommended update for initial livepatch (SUSE-SU-2026:0473-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.197/6.1.159/6.6.119/6.12.61/6.17.11
Patch: 15d560cdf5b36c51fffec07ac2a983ab3bff4cb2/46e9d6f54184573dae1dcbcf6685a572ba6f4480/3e7442c5802146fd418ba3f68dcb9ca92b5cec83/a21615a4ac6fecbb586d59fe2206b63501021789/c2ee6d38996775a19bfdf20cb01a9b8698cb0baa/9b9c0adbc3f8a524d291baccc9d0c04097fb4869

Timelineinfo

12/16/2025 Advisory disclosed
12/16/2025 +0 days CVE reserved
12/16/2025 +0 days VulDB entry created
02/22/2026 +68 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-68303 (🔒)
GCVE (CVE): GCVE-0-2025-68303
GCVE (VulDB): GCVE-100-336869
CERT Bund: WID-SEC-2025-2868 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 12/16/2025 17:51
Updated: 02/22/2026 07:33
Changes: 12/16/2025 17:51 (58), 02/14/2026 21:17 (2), 02/22/2026 07:33 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!