CVE-2025-71274

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 0, 7.0, <2e4a70f3c30910427e5ea848b799066d67b963d5, <42023d4b6d2661a40ee2dcf7e1a3528a35c638ca, 6.1.165, 6.12.75, <90c8353f471821d7ccd4fe573a2402e056192494, <=5.10.*, <=6.6.*, <=6.19.*, <392c6b68334aa0e0ae9aba95c0a366bcb0d92f5d, <=6.18.*, <954557957177c3c13d7c655976665b1170da5e50, <7654e6e3cd6bdee9602f6063b3c670bd556d7e61, 6.19.6, 6.6.128, 5.10.252, <d66b8074c555e8abb0ae19eea1c9f3635498bdde, <4.18, 4.18, 6.18.16, <=*, <=5.15.*, <47615557447185917afa432b7958f87583c417cb, 5.15.202, 39e47767ec9b22f844c2a07c9d329256960d4021

Description

In the Linux kernel, the following vulnerability has been resolved: rpmsg: core: fix race in driver_override_show() and use core helper The driver_override_show function reads the driver_override string without holding the device_lock. However, the store function modifies and frees the string while holding the device_lock. This creates a race condition where the string can be freed by the store function while being read by the show function, leading to a use-after-free. To fix this, replace the rpmsg_string_attr macro with explicit show and store functions. The new driver_override_store uses the standard driver_set_override helper. Since the introduction of driver_set_override, the comments in include/linux/rpmsg.h have stated that this helper must be used to set or clear driver_override, but the implementation was not updated until now. Because driver_set_override modifies and frees the string while holding the device_lock, the new driver_override_show now correctly holds the device_lock during the read operation to prevent the race. Additionally, since rpmsg_string_attr has only ever been used for driver_override, removing the macro simplifies the code.

Gravité et risque d'exploitation

CVE-2025-71274 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.10 %, ce qui la place devant 0.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 0, 7.0, <2e4a70f3c30910427e5ea848b799066d67b963d5, <42023d4b6d2661a40ee2dcf7e1a3528a35c638ca, 6.1.165, 6.12.75, <90c8353f471821d7ccd4fe573a2402e056192494, <=5.10.*, <=6.6.*, <=6.19.*, <392c6b68334aa0e0ae9aba95c0a366bcb0d92f5d, <=6.18.*, <954557957177c3c13d7c655976665b1170da5e50, <7654e6e3cd6bdee9602f6063b3c670bd556d7e61, 6.19.6, 6.6.128, 5.10.252, <d66b8074c555e8abb0ae19eea1c9f3635498bdde, <4.18, 4.18, 6.18.16, <=*, <=5.15.*, <47615557447185917afa432b7958f87583c417cb, 5.15.202, 39e47767ec9b22f844c2a07c9d329256960d4021) 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