CVE-2026-74603

What it is

In the Linux kernel, the following vulnerability has been resolved: ptp: ocp: Fix board ID over-read The EEPROM board ID is a fixed 13-byte field and is not guaranteed to contain a NUL terminator. Passing it directly to devlink_info_version_fixed_put() treats it as a C string and may read beyond the field. Format at most OCP_BOARD_ID_LEN bytes into the existing local buffer before reporting the ID. Use a precision limit because the snprintf() output size alone does not bound the source string scan.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2026-08-15 05:44 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-08-22 16:16 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-10-14 13:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 7.1 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2026-08-22 16:16 UTC

Last modified

2026-10-14 13:10 UTC

Exploit probability

0.1% · EPSS, next 30 days

Record status

Received

Attack profile CVSS 3.1 · 7.1

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-74603.md and follow it. Check whether this project is affected by CVE-2026-74603. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge