BSOD 0xA (IRQL_NOT_LESS_OR_EQUAL): veracrypt.sys causes NULL Irp->UserEvent dereference in KeSetEvent during volume mount
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 42/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 静か
- 技術スタック
- c
調査の方向性
Start by examining the VeraCrypt driver’s synchronous I/O and completion paths related to volume mounting, then compare the 1.26.24 driver behavior with the release notes for 1.26.29. Use the supplied crash dumps to verify whether the reported UserEvent lifetime and timeout sequence matches the driver code. Done means identifying the faulty path and confirming a fix prevents the reported bugcheck; the issue provides no source file or test entry point.
索引モデルが issue の本文から書いたものです。
説明
In 4 of 5 dumps PROCESS_NAME is VeraCrypt.exe, with veracrypt+0x4e8cc as the direct caller of NtCreateFile. In the 5th dump, PROCESS_NAME is System, with the call coming from mountmgr!ReconcileThisDatabaseWithMasterWorker → mountmgr!OpenRemoteDatabase — Mount Manager reacting to the same volume-arrival event from a different thread.
WinDbg also reports *** WARNING: Unable to verify timestamp for veracrypt.sys in 4 of 5 dumps.
Suspected root cause: Irp->UserEvent is dereferenced at completion time while pointing to invalid/freed memory. This is consistent with a synchronous I/O request issued by veracrypt.sys using a short-lived (likely stack-allocated) KEVENT combined with a finite wait timeout: if the underlying storage stack does not complete the IRP before the timeout expires, veracrypt.sys's wait returns and the event's storage may be reused/invalidated — but without the IRP being cancelled. When the storage stack later does complete that IRP, IopCompleteRequest dereferences the now-invalid UserEvent pointer, causing the crash at DISPATCH_LEVEL (since storage completion typically happens via DPC).
All captured crashes show concurrent FLTMGR!FltpDoFilterNotificationForNewVolume activity (Windows attaching registered minifilters — in our case including a third-party disk-encryption filesystem filter — to the newly-arrived VeraCrypt volume). We believe this is not the root cause itself, but widens the race window described above (more registered minifilters → longer FltpInitInstance → higher chance the storage stack responds after veracrypt.sys's wait has already timed out).
Note: I noticed that 1.26.29 release notes mention "Improve driver I/O handling, including safer request completion" and "Fix rare BSOD issue affecting the VeraCrypt driver" — this may already address this issue. I am upgrading to test and will update this report with the result.
Steps to reproduce
- Install VeraCrypt 1.26.24 on a system that also has another disk-encryption
product's filesystem filter driver installed (in our case: Symantec/Broadcom
Encryption Desktop — PGPfsfd.sys, PGPwded.sys, Pgpwdefs.sys), on top of an
Intel VROC RAID storage stack (iaVROC.sys/mpi3drv.sys under storport.sys). - Use the system normally, mounting/dismounting VeraCrypt volumes as usual.
- No single specific action reliably triggers the crash — it occurred 5 times
over approximately 2 days of normal use, always within seconds of volume
mount/dismount activity (confirmed via PROCESS_NAME and stack trace in all
5 dumps), not on every single mount. - System bugchecks with IRQL_NOT_LESS_OR_EQUAL (0xA), consistently in
nt!KeSetEvent as described above.
We do not have a 100%-reliable single-step repro; this report is based on
5 independent crash dumps with identical signatures collected from the same
machine. We suspect the trigger is timing-dependent (a race between the
storage stack completing an I/O request and a synchronous wait timeout in
veracrypt.sys — see root cause analysis above), which would explain why it
doesn't reproduce on every mount.
Screenshots
N/A
122025-31640-01.dmp
122025-32406-01.dmp
122125-32281-01.dmp
122125-32640-01.dmp
122225-32531-01.dmp
Your Environment
Please tell us more about your environment
VeraCrypt version: 1.26.24 (driver timestamp: Thu May 29 09:43:28 2025)
Operating system and version: Windows 11, build 10.0.26100.7462 (24H2)
System type: 64-bit (x64), 24 logical processors, Hyper-V-enlightened guest
- 主要言語
- C
- スター
- 11.7k
- フォーク
- 1.4k
- 平均マージ
- 1日 1時間
- マージ済み PR（30日）
- 28
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
veracrypt/VeraCrypt のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 5/5 1週間以上 初心者へのやさしさ 32/100
veracrypt/VeraCrypt#1995 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
veracrypt/VeraCrypt#1993 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
veracrypt/VeraCrypt#1991 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
veracrypt/VeraCrypt の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
bug game: 01008BA02525A000 ios
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
area/ysql kind/bug priority/medium status/awaiting-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
yugabyte/yugabyte-db#37523 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
メンテナーはふだん 3 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
ly05010419/MacNativeGames#2079 ·
メンテナーはふだん 1 日以内に返信