Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68303: platform/x86: intel: punit_ipc: fix memory corruption

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 15d560cdf5b36c51fffec07ac2a983ab3bff4cb2, 3e7442c5802146fd418ba3f68dcb9ca92b5cec83, 46e9d6f54184573dae1dcbcf6685a572ba6f4480; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1.

Low priority for now. Upgrade to Linux Linux 15d560cdf5b36c51fffec07ac2a983ab3bff4cb2, 3e7442c5802146fd418ba3f68dcb9ca92b5cec83, 46e9d6f54184573dae1dcbcf6685a572ba6f4480; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 16, 2025
Updated
Oct 13, 2026
EPSS
0.1% · 3th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68303

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.5affected
    • fdca4f16f57da76a8e68047923588a87d1c01f0a and later · before 15d560cdf5b36c51fffec07ac2a983ab3bff4cb2affected · git
    • fdca4f16f57da76a8e68047923588a87d1c01f0a and later · before 46e9d6f54184573dae1dcbcf6685a572ba6f4480affected · git
    • fdca4f16f57da76a8e68047923588a87d1c01f0a and later · before 3e7442c5802146fd418ba3f68dcb9ca92b5cec83affected · git
    • fdca4f16f57da76a8e68047923588a87d1c01f0a and later · before a21615a4ac6fecbb586d59fe2206b63501021789affected · git
    • fdca4f16f57da76a8e68047923588a87d1c01f0a and later · before c2ee6d38996775a19bfdf20cb01a9b8698cb0baaaffected · git
    • fdca4f16f57da76a8e68047923588a87d1c01f0a and later · before 9b9c0adbc3f8a524d291baccc9d0c04097fb4869affected · git
    • before 4.5not affected · semver
    • 5.15.197 and later · up to and including 5.15.*not affected · semver
    • 6.1.159 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.11-16.17.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68301Dec 16, 2025 · net: atlantic: fix fragment overflow handling in RX path
    39Monitor
  • ← EarlierCVE-2025-68302Dec 16, 2025 · net: sxgbe: fix potential NULL dereference in sxgbe_rx()
    30Monitor
  • Later →CVE-2025-68304Dec 16, 2025 · Bluetooth: hci_core: lookup hci_conn on RX path on protocol side
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux15d560cdf5b36c51fffec07ac2a983ab3bff4cb2Vendor (CNA)
Linux Linux3e7442c5802146fd418ba3f68dcb9ca92b5cec83Vendor (CNA)
Linux Linux46e9d6f54184573dae1dcbcf6685a572ba6f4480Vendor (CNA)
Linux Linux9b9c0adbc3f8a524d291baccc9d0c04097fb4869Vendor (CNA)
Linux Linuxa21615a4ac6fecbb586d59fe2206b63501021789Vendor (CNA)
Linux Linuxc2ee6d38996775a19bfdf20cb01a9b8698cb0baaVendor (CNA)
azl3 kernel 6.6.117.1-1 on Azure Linux 3.06.6.119.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records