CVE-2026-68387

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

can: raw: add locking for raw flags bitfield

With commit 890e5198a6e5 ("can: raw: use bitfields to store flags in struct raw_sock") the formerly separate integer values have been integrated into a single bitfield. This led to a read-modify-write operation when changing a flag in raw_setsockopt() which now needs a locking to prevent concurrent access.

Instead of adding a lock/unlock hell in each of the flag manipulations this patch introduces a wrapper for a new raw_setsockopt_locked() function analogue to the isotp_setsockopt[_locked]() approach in net/can/isotp.c

[mkl: use Closes tag instead of Link]

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

can: raw: add locking for raw flags bitfield - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57791aab1129c9405f84bb0882de58967d8b44cd
generic

can: raw: add locking for raw flags bitfield - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e5185c090589f4146d728ab36417d8a5419f127
generic

can: raw: add locking for raw flags bitfield - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00ba4bf8798242253fefc1fa6a78db1d445fd024

Vendor Advisories for CVE-2026-68387(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 32× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 23:16 UTCEG score recompute
  2. 2026-08-20 23:16 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 10:36 UTCGHSA enrichment
  5. 2026-08-19 21:57 UTCEG score recompute
  6. 2026-08-19 21:57 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 09:17 UTCGHSA enrichment
  9. 2026-08-18 20:38 UTCEG score recompute
  10. 2026-08-18 20:38 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 07:59 UTCGHSA enrichment
  14. 2026-08-17 19:19 UTCEG score recompute
  15. 2026-08-17 19:19 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:31 UTCEG score recompute
  18. 2026-08-17 06:31 UTCGHSA enrichment
  19. 2026-08-17 05:36 UTCEG score recompute
  20. 2026-08-17 05:36 UTCGHSA enrichment
  21. 2026-08-17 03:37 UTCGHSA enrichment
  22. 2026-08-16 14:58 UTCEG score recompute
  23. 2026-08-16 14:58 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:19 UTCEG score recompute
Show 19 more
  1. 2026-08-16 02:19 UTCGHSA enrichment
  2. 2026-08-15 13:41 UTCEG score recompute
  3. 2026-08-15 13:41 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-15 01:02 UTCGHSA enrichment
  6. 2026-08-14 12:23 UTCEG score recompute
  7. 2026-08-14 12:23 UTCGHSA enrichment
  8. 2026-08-13 23:44 UTCEG score recompute
  9. 2026-08-13 23:44 UTCGHSA enrichment
  10. 2026-08-13 23:03 UTCEG score recompute▲ 7.80
  11. 2026-08-13 23:03 UTCGHSA enrichment
  12. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 10:35 UTCEG score recompute
  15. 2026-08-13 10:35 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-10 13:24 UTCNVD update
  18. 2026-08-10 12:18 UTCEG score recompute
  19. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68387?
CVE-2026-68387 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: can: raw: add locking for raw flags bitfield With commit 890e5198a6e5 ("can: raw: use bitfields to store flags in struct raw_sock") the formerly separate integer values have been integrated into a single bitfield. This led to a…
When was CVE-2026-68387 disclosed?
CVE-2026-68387 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68387 actively exploited?
CVE-2026-68387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68387?
CVE-2026-68387 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68387?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68387, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68387

Explore →

Is Your Infrastructure Affected by CVE-2026-68387?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs