CVE-2026-68150

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

fs/super: fix emergency thaw double-unlock of s_umount

do_thaw_all() iterates over all superblocks via __iterate_supers() with SUPER_ITER_EXCL, which acquires s_umount exclusively before calling the callback and releases it afterwards. However, the callback do_thaw_all_callback() calls thaw_super_locked() which unconditionally releases s_umount on every code path. This results in a second unlock attempt in __iterate_supers() that corrupts the rwsem state, triggering a DEBUG_RWSEMS warning:

[ 182.601148] sysrq: Emergency Thaw of all frozen filesystems [ 182.601865] ------------[ cut here ]------------ [ 182.602375] DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff99b1011e5870, owner = 0x0, curr 0xffff99b101b06c80, list not empty [ 182.603817] WARNING: kernel/locking/rwsem.c:1412 at up_write+0xa3/0x170, CPU#2: kworker/2:1/53 [ 182.604578] Modules linked in: [ 182.604864] CPU: 2 UID: 0 PID: 53 Comm: kworker/2:1 Not tainted 7.2.0-rc4-00001-gbd3bd93ea98a-dirty #4 PREEMPT(lazy) [ 182.605711] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1kylin1 04/01/2014 [ 182.606417] Workqueue: events do_thaw_all [ 182.606750] RIP: 0010:up_write+0xaf/0x170 [ 182.607076] Code: 19 3a 92 48 0f 44 c2 48 8b 55 08 48 8b 55 00 4c 8b 45 08 48 8b 55 00 48 8d 3d ad 91 e0 01 48 8b 4d 20 50 48 c7 c6 f0 8c 26 92 <67> 48 0f b9 3a e8 d7 93 4e 00 58 eb 81 48 83 7f 18 00 48 c7 c2 8d [ 182.608563] RSP: 0018:ffffb670001d7e08 EFLAGS: 00010246 [ 182.609007] RAX: ffffffff92349e8d RBX: 0000000000000000 RCX: ffff99b1011e5870 [ 182.609595] RDX: 0000000000000000 RSI: ffffffff92268cf0 RDI: ffffffff92914d10 [ 182.610283] RBP: ffff99b1011e5870 R08: 0000000000000000 R09: ffff99b101b06c80 [ 182.610847] R10: ffff99b10139a808 R11: fefefefefefefeff R12: 0000000000000000 [ 182.611414] R13: ffffffff90cf74d0 R14: 0000000000000000 R15: ffff99b1011e5800 [ 182.612009] FS: 0000000000000000(0000) GS:ffff99b1eaaee000(0000) knlGS:0000000000000000 [ 182.612670] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 182.613146] CR2: 00000000005c631c CR3: 00000000013ee000 CR4: 00000000000006f0 [ 182.613722] Call Trace: [ 182.613946] [ 182.614130] __iterate_supers+0x128/0x150 [ 182.614463] do_thaw_all+0x1b/0x30 [ 182.614759] process_scheduled_works+0xbb/0x3f0 [ 182.615150] ? __pfx_worker_thread+0x10/0x10 [ 182.615499] worker_thread+0x129/0x270 [ 182.615816] ? __pfx_worker_thread+0x10/0x10 [ 182.616201] kthread+0xe2/0x120 [ 182.616469] ? __pfx_kthread+0x10/0x10 [ 182.616792] ret_from_fork+0x15b/0x240 [ 182.617115] ? __pfx_kthread+0x10/0x10 [ 182.617426] ret_from_fork_asm+0x1a/0x30 [ 182.617761] [ 182.617968] ---[ end trace 0000000000000000 ]--- [ 182.618412] Emergency Thaw complete

Fix this by switching to SUPER_ITER_UNLOCKED and acquiring s_umount in the callback via super_lock_excl() before calling thaw_super_locked(). This matches the locking pattern expected by thaw_super_locked() and eliminates the double unlock.

While at it, remove the dead 'return;' at the end of do_thaw_all_callback().

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

August 23, 2026

References (4)

Vendor Advisories for CVE-2026-68150(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-18 03:20 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-12 15:45 UTCEG score recompute
  11. 2026-10-11 19:30 UTCEG score recompute
  12. 2026-10-11 16:45 UTCEG score recompute
  13. 2026-10-11 14:06 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-04 05:26 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 63 more
  1. 2026-09-30 22:42 UTCEG score recompute
  2. 2026-09-30 22:42 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-27 16:58 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-09-23 22:30 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-09-20 20:21 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-09-17 15:03 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  14. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-09-14 08:54 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  17. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-09-11 06:46 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  20. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-08 04:38 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  22. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-09-05 02:07 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  26. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  28. 2026-09-01 23:04 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  29. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  30. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  31. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  32. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-08-29 20:54 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  34. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  35. 2026-08-26 15:29 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  36. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  37. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  38. 2026-08-23 13:21 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  39. 2026-08-23 13:19 UTCNVD update
  40. 2026-08-23 13:08 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  41. 2026-08-23 13:05 UTCMITRE cvelistV5
  42. 2026-08-23 09:56 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-08-20 07:48 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  47. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  48. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  49. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-08-17 05:40 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  51. 2026-08-17 05:26 UTCNVD update
  52. 2026-08-17 05:11 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  53. 2026-08-17 05:05 UTCMITRE cvelistV5
  54. 2026-08-16 17:45 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  55. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  57. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-08-13 15:36 UTCEG score recompute
  59. 2026-08-13 15:36 UTCGHSA enrichmentGHSA-6c2j-3829-2wpv
  60. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  61. 2026-08-10 13:24 UTCNVD update
  62. 2026-08-10 12:21 UTCEG score recompute
  63. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68150?
CVE-2026-68150 is a vulnerability whose severity is not yet rated; its CVE record was published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: fs/super: fix emergency thaw double-unlock of s_umount dothawall() iterates over all superblocks via iterate_supers() with SUPERITEREXCL, which acquires s_umount exclusively before calling the callback and releases it afterwards.…
When was the CVE record for CVE-2026-68150 published?
The CVE record for CVE-2026-68150 was published on August 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 23, 2026; the record at its source may have been updated since.
Is CVE-2026-68150 actively exploited?
CVE-2026-68150 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-68150?
A fix for CVE-2026-68150 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68150 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68150

Explore →

Is Your Infrastructure Affected by CVE-2026-68150?

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

Book a Demo →Browse All CVEs