CVE-2026-72103
Last modified
CVE-2026-72103 is a high-severity vulnerability rated 7.3/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 ("md: port block device access to file") accidentally causes the caller's thread keyring to be kept alive long beyond the caller's lifetime. As a result, "cryptsetup luksSuspend" silently fails to wipe the LUKS volume key from memory. In detail: "cryptsetup luksOpen" uses its supposedly ephemeral thread keyring to pass the volume key to the kernel. dm-crypt's crypt_set_keyring_key() copies the key material into its own crypt_config structure and then drops its own reference to the key in the keyring with key_put(). With this fix, restoring pre-v6.9 behavior, the copy in the thread keyring is then promptly garbage collected, such that exactly one copy of the volume key remains. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 ("md: port block device access to file") accidentally causes the caller's thread keyring to be kept alive long beyond the caller's lifetime. As a result, "cryptsetup luksSuspend" silently fails to wipe the LUKS volume key from memory. In detail: "cryptsetup luksOpen" uses its supposedly ephemeral thread keyring to pass the volume key to the kernel. dm-crypt's crypt_set_keyring_key() copies the key material into its own crypt_config structure and then drops its own reference to the key in the keyring with key_put(). With this fix, restoring pre-v6.9 behavior, the copy in the thread keyring is then promptly garbage collected, such that exactly one copy of the volume key remains. This single copy is correctly wiped from memory on "cryptsetup luksSuspend". Without this fix, the thread keyring and the volume key in it remains. This second copy is only freed on "luksClose". "luksSuspend" neither knows about this copy nor has any way to remove it, so the key remains recoverable from RAM after a suspend that is documented to have wiped it. This fix should not introduce new security problems, as the code is anyway gated by CAP_SYS_ADMIN. The device-mapper core, not the calling task, is the legitimate owner of this long-lived file.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a28d893eb3270cf62c10dd8777af0d8452cdc072, < d3eb8451d529ea452740d1a2bc395a1d20c48133; >= a28d893eb3270cf62c10dd8777af0d8452cdc072, < 8ced1d242c34e342defcccdb00663354f212aae6; >= a28d893eb3270cf62c10dd8777af0d8452cdc072, < f00105be6a593920e9bc7949a069d4a116888851; >= a28d893eb3270cf62c10dd8777af0d8452cdc072, < 981ccd97f7153d310dfa92a534525bbaf46752c2 |
| Linux | Linux | 6.9 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72103?
How severe is CVE-2026-72103?
How do I fix CVE-2026-72103?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72098In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72099In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-7210`xml.parsers.expat` and `xml.etree.ElementTree` use insuffic…7.5
- CVE-2026-72100In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-72101In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72102In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72104In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72105In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72106In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72107In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-72108In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72109In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-72103?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
