# CVE-2026-74603: ptp: ocp: Fix board ID over-read

> A local attacker can read out-of-bounds memory from the kernel by exploiting a missing NUL terminator in the PTP OCP board ID field.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** BELL-CVE-2026-74603, DEBIAN-CVE-2026-74603, GHSA-9xcf-hcjx-rjfr, UBUNTU-CVE-2026-74603

## What is CVE-2026-74603?

CVE-2026-74603 is a high-severity vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-74603?


## How do I fix CVE-2026-74603?

Apply the vendor's patch.

## Is CVE-2026-74603 being exploited?

There is no known exploitation of CVE-2026-74603 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74603 and fix it if it is affected.

What it is: CVE-2026-74603 is a high-severity vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74603 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74603/ (Markdown: https://insights.sbomify.com/CVE-2026-74603/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74603
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74603
- OSV: https://osv.dev/vulnerability/CVE-2026-74603

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74603/
Summaries are generated and may contain mistakes; the official description above is the record.