net: ravb: avoid dereferencing an invalid PTP clock
In the Linux kernel, the following vulnerability has been resolved: net: ravb: avoid dereferencing an invalid PTP clock The PTP clock is unavailable before the first open, so querying its index can dereference a NULL pointer. Registration failures can also leave an error pointer in priv->ptp.clock. Cache the PHC index separately and report -1 while no clock is registered. Normalize registration errors to NULL and preserve the static timestamping capabilities.
- Published
- Sep 11, 2026
- Updated
- Sep 14, 2026
- EPSS
- 0.2% · 6th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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.2affected
- a0d2f20650e81407d8e51ad2cbdc492861c74e9c and later · before 29ffd972531f8e6e0edf4ea3496190acff9fc9c2affected · git
- a0d2f20650e81407d8e51ad2cbdc492861c74e9c and later · before bf3308416a2be85dcc9965b614a745b40beeff14affected · git
- a0d2f20650e81407d8e51ad2cbdc492861c74e9c and later · before fc710f89a644e030a7ca15343176ca862fd61b9daffected · git
- a0d2f20650e81407d8e51ad2cbdc492861c74e9c and later · before 8d4d06d6e2b501cb8e30ed3b1924c470358e8052affected · git
- a0d2f20650e81407d8e51ad2cbdc492861c74e9c and later · before 0aaa53936419cf0c19c670387fc6d431e042a1b6affected · git
- a0d2f20650e81407d8e51ad2cbdc492861c74e9c and later · before 1f77af0aaf277413ff32f6ff8c2c4282bd64c897affected · git
- before 4.2not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 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 | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 0aaa53936419cf0c19c670387fc6d431e042a1b6 | Vendor (CNA) |
| Linux Linux | 1f77af0aaf277413ff32f6ff8c2c4282bd64c897 | Vendor (CNA) |
| Linux Linux | 29ffd972531f8e6e0edf4ea3496190acff9fc9c2 | Vendor (CNA) |
| Linux Linux | 8d4d06d6e2b501cb8e30ed3b1924c470358e8052 | Vendor (CNA) |
| Linux Linux | bf3308416a2be85dcc9965b614a745b40beeff14 | Vendor (CNA) |
| Linux Linux | fc710f89a644e030a7ca15343176ca862fd61b9d | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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).
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0aaa53936419cf0c19c670387fc6d431e042a1b6
- git.kernel.org/stable/c/1f77af0aaf277413ff32f6ff8c2c4282bd64c897
- git.kernel.org/stable/c/29ffd972531f8e6e0edf4ea3496190acff9fc9c2
- git.kernel.org/stable/c/8d4d06d6e2b501cb8e30ed3b1924c470358e8052
- git.kernel.org/stable/c/bf3308416a2be85dcc9965b614a745b40beeff14
- git.kernel.org/stable/c/fc710f89a644e030a7ca15343176ca862fd61b9d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.