CVE-2026-74603: ptp: ocp: Fix board ID over-read
Noroxi assessment
Priority: Monitor (action score 28/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.12% (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 3d965811be78473654e6e8cc8e4fb7b6b87aa6c1, 5fd91dd4a143479b0575fb1f202ec1c501e71fd5, 6b69f2ef10cdb018c0b127a7cab88e590bbddba4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3d965811be78473654e6e8cc8e4fb7b6b87aa6c1, 5fd91dd4a143479b0575fb1f202ec1c501e71fd5, 6b69f2ef10cdb018c0b127a7cab88e590bbddba4 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: 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.
- Published
- Aug 22, 2026
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- 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.
Is your version affected? Check itNoroxi 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 helpAffected 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
- 5.18affected
- 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and later · before 72ef3ce80078199bfad32f98d055f44ba7cd0c3daffected · git
- 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and later · before 3d965811be78473654e6e8cc8e4fb7b6b87aa6c1affected · git
- 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and later · before f92558bbe78d6284fedd053900f82a70f0aa8707affected · git
- 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and later · before 5fd91dd4a143479b0575fb1f202ec1c501e71fd5affected · git
- 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and later · before f8d7e5751267637190eff887c971d5b468106213affected · git
- 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and later · before 6b69f2ef10cdb018c0b127a7cab88e590bbddba4affected · git
- before 5.18not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
- 6.6.152 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74601Aug 22, 2026 · ring-buffer: Use current_context for safe per-CPU buffer swap31Monitor
- ← EarlierCVE-2026-74602Aug 22, 2026 · ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()0Monitor
- Later →CVE-2026-74604Aug 22, 2026 · Revert "thermal/drivers/hwmon: Cleanup coding style a bit"33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3d965811be78473654e6e8cc8e4fb7b6b87aa6c1 | Vendor (CNA) |
| Linux Linux | 5fd91dd4a143479b0575fb1f202ec1c501e71fd5 | Vendor (CNA) |
| Linux Linux | 6b69f2ef10cdb018c0b127a7cab88e590bbddba4 | Vendor (CNA) |
| Linux Linux | 72ef3ce80078199bfad32f98d055f44ba7cd0c3d | Vendor (CNA) |
| Linux Linux | f8d7e5751267637190eff887c971d5b468106213 | Vendor (CNA) |
| Linux Linux | f92558bbe78d6284fedd053900f82a70f0aa8707 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- 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
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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)Show less
- git.kernel.org/stable/c/5fd91dd4a143479b0575fb1f202ec1c501e71fd5
- git.kernel.org/stable/c/6b69f2ef10cdb018c0b127a7cab88e590bbddba4
- git.kernel.org/stable/c/72ef3ce80078199bfad32f98d055f44ba7cd0c3d
- git.kernel.org/stable/c/f8d7e5751267637190eff887c971d5b468106213
- git.kernel.org/stable/c/f92558bbe78d6284fedd053900f82a70f0aa8707
Vendor advisories and official records. Exploit/PoC links are deliberately left out.