Heimdall Security Logo

CVE-2026-63826

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.12.*, 6.6.144, <2c1c805c65fb7dc7524e20376d6987721e73a0b1, 2.6.12, 0, <=7.1.*, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <=6.6.*, 6.12.95, <c6765f39ed27014ff877b00a2efa494233404e17, <70f1e000b88cfa8ca3fd7f4d082647fc089a7769, <0d35f9f194a858567a21017d69318a51e3a822b9, <=6.18.*, <5267eab88fa4c684459504b8be577ad64953b9a6, 6.18.38, <=*, 7.1.3, 7.2

Description

In the Linux kernel, the following vulnerability has been resolved: fbdev: fix use-after-free in store_modes() store_modes() replaces a framebuffer's modelist with modes from userspace. On success it frees the old modelist with fb_destroy_modelist(). Two fields still point into that freed list. One pointer is fb_display[i].mode, the mode a console is using. fbcon_new_modelist() moves these pointers to the new list. It only does so for consoles still mapped to the framebuffer. An unmapped console is skipped and keeps its stale pointer. Unbinding fbcon, for example, sets con2fb_map[i] to -1 but leaves fb_display[i].mode set. An FBIOPUT_VSCREENINFO ioctl with FB_ACTIVATE_INV_MODE later reaches fbcon_mode_deleted(). That function reads the stale fb_display[i].mode through fb_mode_is_equal(). The read is a use-after-free. The other pointer is fb_info->mode, the current mode. It is set through the mode sysfs attribute. store_modes() does not update fb_info->mode, so it is left pointing into the freed list. show_mode(), the attribute's read handler, dereferences the stale fb_info->mode through mode_string(). The read is a use-after-free. Clear both pointers before freeing the list. Commit a1f305893074 ("fbcon: Set fb_display[i]->mode to NULL when the mode is released") added the helper fbcon_delete_modelist(). It clears every fb_display[i].mode that points into a given list. So far it is called only from the unregister path. Call it from store_modes() too, and set fb_info->mode to NULL.

Gravité et risque d'exploitation

CVE-2026-63826 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.17 %, ce qui la place devant 5.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.12.*, 6.6.144, <2c1c805c65fb7dc7524e20376d6987721e73a0b1, 2.6.12, 0, <=7.1.*, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <=6.6.*, 6.12.95, <c6765f39ed27014ff877b00a2efa494233404e17, <70f1e000b88cfa8ca3fd7f4d082647fc089a7769, <0d35f9f194a858567a21017d69318a51e3a822b9, <=6.18.*, <5267eab88fa4c684459504b8be577ad64953b9a6, 6.18.38, <=*, 7.1.3, 7.2) 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