CVE-2025-68296

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 6.17.11, <=*, <=6.12.*, <05814c389b53d2f3a0b9eeb90ba7a05ba77c4c2a, <=6.17.*, 6.18, <482330f8261b4bea8146d9bd69c1199e5dfcbb5c, 6.6.143, <=6.6.*, <eb76d0f5553575599561010f24c277cc5b31d003, 0, 6.12.61, 6a9ee8af344e3bd7dbd61e67037096cdf7f83289, <711ebd961190def4c69ea24b2f0be75e995af24a, 2.6.34, <2.6.34

Description

In the Linux kernel, the following vulnerability has been resolved: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup Protect vga_switcheroo_client_fb_set() with console lock. Avoids OOB access in fbcon_remap_all(). Without holding the console lock the call races with switching outputs. VGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon function uses struct fb_info.node, which is set by register_framebuffer(). As the fb-helper code currently sets up VGA switcheroo before registering the framebuffer, the value of node is -1 and therefore not a legal value. For example, fbcon uses the value within set_con2fb_map() [1] as an index into an array. Moving vga_switcheroo_client_fb_set() after register_framebuffer() can result in VGA switching that does not switch fbcon correctly. Therefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(), which already holds the console lock. Fbdev calls fbcon_fb_registered() from within register_framebuffer(). Serializes the helper with VGA switcheroo's call to fbcon_remap_all(). Although vga_switcheroo_client_fb_set() takes an instance of struct fb_info as parameter, it really only needs the contained fbcon state. Moving the call to fbcon initialization is therefore cleaner than before. Only amdgpu, i915, nouveau and radeon support vga_switcheroo. For all other drivers, this change does nothing.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.17.11, <=*, <=6.12.*, <05814c389b53d2f3a0b9eeb90ba7a05ba77c4c2a, <=6.17.*, 6.18, <482330f8261b4bea8146d9bd69c1199e5dfcbb5c, 6.6.143, <=6.6.*, <eb76d0f5553575599561010f24c277cc5b31d003, 0, 6.12.61, 6a9ee8af344e3bd7dbd61e67037096cdf7f83289, <711ebd961190def4c69ea24b2f0be75e995af24a, 2.6.34, <2.6.34) 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