Heimdall Security Logo

CVE-2025-71102

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : 6.12.64, <=6.1.*, <=6.12.*, <1727e8bd69103a68963a5613a0ddb6d8d37df5d3, 6.1.160, 0, <5.8, 6.6.120, <a19fb3611e4c06624fc0f83ef19f4fb8d57d4751, 5.15.198, <=5.10.*, <=6.6.*, 6.18.3, <062774439d442882b44f5eab8c256ad3423ef284, <=6.18.*, <9ef28943471a16e4f9646bc3e8e2de148e7d8d7b, <57ba40b001be27786d0570dd292289df748b306b, 5.10.248, <08bd4c46d5e63b78e77f2605283874bbe868ab19, <cfdf6250b63b953b1d8e60814c8ca96c6f9d1c8c, <=*, <=5.15.*, 6.19, 5.8, 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2

Description

In the Linux kernel, the following vulnerability has been resolved: scs: fix a wrong parameter in __scs_magic __scs_magic() needs a 'void *' variable, but a 'struct task_struct *' is given. 'task_scs(tsk)' is the starting address of the task's shadow call stack, and '__scs_magic(task_scs(tsk))' is the end address of the task's shadow call stack. Here should be '__scs_magic(task_scs(tsk))'. The user-visible effect of this bug is that when CONFIG_DEBUG_STACK_USAGE is enabled, the shadow call stack usage checking function (scs_check_usage) would scan an incorrect memory range. This could lead 1. **Inaccurate stack usage reporting**: The function would calculate wrong usage statistics for the shadow call stack, potentially showing incorrect value in kmsg. 2. **Potential kernel crash**: If the value of __scs_magic(tsk)is greater than that of __scs_magic(task_scs(tsk)), the for loop may access unmapped memory, potentially causing a kernel panic. However, this scenario is unlikely because task_struct is allocated via the slab allocator (which typically returns lower addresses), while the shadow call stack returned by task_scs(tsk) is allocated via vmalloc(which typically returns higher addresses). However, since this is purely a debugging feature (CONFIG_DEBUG_STACK_USAGE), normal production systems should be not unaffected. The bug only impacts developers and testers who are actively debugging stack usage with this configuration enabled.

Gravité et risque d'exploitation

CVE-2025-71102 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.15 %, ce qui la place devant 3.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12.64, <=6.1.*, <=6.12.*, <1727e8bd69103a68963a5613a0ddb6d8d37df5d3, 6.1.160, 0, <5.8, 6.6.120, <a19fb3611e4c06624fc0f83ef19f4fb8d57d4751, 5.15.198, <=5.10.*, <=6.6.*, 6.18.3, <062774439d442882b44f5eab8c256ad3423ef284, <=6.18.*, <9ef28943471a16e4f9646bc3e8e2de148e7d8d7b, <57ba40b001be27786d0570dd292289df748b306b, 5.10.248, <08bd4c46d5e63b78e77f2605283874bbe868ab19, <cfdf6250b63b953b1d8e60814c8ca96c6f9d1c8c, <=*, <=5.15.*, 6.19, 5.8, 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2) 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

Rechercher une autre CVE