high · 7.8

net: ravb: serialize PTP clock teardown

CVE-2026-80991 · published 11 Sept 2026

How serious is it

  • Severity: high, CVSS score 7.8 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-80991?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • Linux Linux: a0d2f20650e81407d8e51ad2cbdc492861c74e9c to < b917f37bfcce919a969d66a044580a95b11df31c, a0d2f20650e81407d8e51ad2cbdc492861c74e9c to < 695acb5534a9e366efb47b40c7487fc56488b09b, a0d2f20650e81407d8e51ad2cbdc492861c74e9c to < 67a82e6f886beed0de8f8da08bb767e68fba952d, a0d2f20650e81407d8e51ad2cbdc492861c74e9c to < 66b50c31419e7946e9aa325a468ad9b64c961a25
  • Linux Linux: 4.2

How to check

  1. Find out whether you run the affected product and which version, then compare it with the versions above.

How to fix

Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
  1. Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
  2. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

In the Linux kernel, the following vulnerability has been resolved: net: ravb: serialize PTP clock teardown ravb_ptp_interrupt() can race with ravb_ptp_stop() and pass the clock to ptp_clock_event() while ptp_clock_unregister() is freeing it. This can lead to a use-after-free. Use READ_ONCE() and WRITE_ONCE() for lockless access to the clock pointer. Atomically detach it with xchg() before disabling PTP interrupts, then synchronize all IRQs which can invoke ravb_ptp_interrupt() before unregistering the detached clock. A handler which read the old pointer completes before the clock is unregistered, while later handlers read NULL and skip the event.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON