CVE-2025-40008
Vulnérabilité non évaluée dans Linux (Linux)
Description
In the Linux kernel, the following vulnerability has been resolved: kmsan: fix out-of-bounds access to shadow memory Running sha224_kunit on a KMSAN-enabled kernel results in a crash in kmsan_internal_set_shadow_origin(): BUG: unable to handle page fault for address: ffffbc3840291000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 1810067 P4D 1810067 PUD 192d067 PMD 3c17067 PTE 0 Oops: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 81 Comm: kunit_try_catch Tainted: G N 6.17.0-rc3 #10 PREEMPT(voluntary) Tainted: [N]=TEST Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 RIP: 0010:kmsan_internal_set_shadow_origin+0x91/0x100 [...] Call Trace: <TASK> __msan_memset+0xee/0x1a0 sha224_final+0x9e/0x350 test_hash_buffer_overruns+0x46f/0x5f0 ? kmsan_get_shadow_origin_ptr+0x46/0xa0 ? __pfx_test_hash_buffer_overruns+0x10/0x10 kunit_try_run_case+0x198/0xa00 This occurs when memset() is called on a buffer that is not 4-byte aligned and extends to the end of a guard page, i.e. the next page is unmapped. The bug is that the loop at the end of kmsan_internal_set_shadow_origin() accesses the wrong shadow memory bytes when the address is not 4-byte aligned. Since each 4 bytes are associated with an origin, it rounds the address and size so that it can access all the origins that contain the buffer. However, when it checks the corresponding shadow bytes for a particular origin, it incorrectly uses the original unrounded shadow address. This results in reads from shadow memory beyond the end of the buffer's shadow memory, which crashes when that memory is not mapped. To fix this, correctly align the shadow address before accessing the 4 shadow bytes corresponding to each origin.
Gravité et risque d'exploitation
CVE-2025-40008 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.25 %, ce qui la place devant 14.8 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions <6.1.155, <=6.1.*, 19e85d939001946671643f4c16e1de8c633a6ce0, <=6.12.*, 6.6.109, 6.10, 9ff078f5bad8990091f1639347de5e02636e9536, <=6.16.*, 2ef3cec44c60ae171b287db7fc2aa341586d65ba, 6.17, 0, <6.10, <5855792c6bb9a825607845db3feaddaff0414ec3, 6.12.50, 6.1.94, <6.6.109, 6.9.5, <85e1ff61060a765d91ee62dc5606d4d547d9d105, <=6.6.*, <f84e48707051812289b6c2684d4df2daa9d3bfbc, abeede7011da6c88e83ed260b909c140b8c9c250, <df1fa034c0fc229a63d01ffb20bb919b839cb576, 6.1.155, <=*, <e6684ed39edc35401a3341f85b1ab50a6f89a45d, 6.6.34, 6.16.10) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- https://git.kernel.org/stable/c/e6684ed39edc35401a3341f85b1ab50a6f89a45d
- https://git.kernel.org/stable/c/df1fa034c0fc229a63d01ffb20bb919b839cb576
- https://git.kernel.org/stable/c/f84e48707051812289b6c2684d4df2daa9d3bfbc
- https://git.kernel.org/stable/c/5855792c6bb9a825607845db3feaddaff0414ec3
- https://git.kernel.org/stable/c/85e1ff61060a765d91ee62dc5606d4d547d9d105
