CVE-2026-89896

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 5.15.221, 4.20, <79fd0b0161506fc9507bf7a6fe4c975a857a5be8, 50e761516f2b8c0cdeb31a8c6ca1b4ef98cd13f1, 5.10.270, 0, <729a1ffab968b3c493f61d1cd683f5bafec500ea, 6.1.188, 6.18.51, <9df2fbe563194da1967a5db083442186c1323efe, <4.20, <=5.10.*, <=6.6.*, <81aa608ac3a56cdd4aab0bd12442ed529a24ba31, 7.2.5, 6.6.157, <6fabacc3b79a528450aef4c32464da2ec681049e, <ce5693b6e3a693fcdc3800af309363f6250104c8, <=6.18.*, <22441be29ec27c693f40c1ef499093275ef529d1, 6.12.110, <=7.2.*, <=*, <=5.15.*, <f78cf36cabf911da348ea80e4e9f430d74f6905c, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: media: cedrus: fix memory leak in cedrus_init_ctrls() In cedrus_init_ctrls(), the V4L2 control handler is initialized before allocating memory for ctx->ctrls. If this allocation fails, the function returns -ENOMEM without freeing the previously allocated handler resources, leading to a memory leak. Fix this by calling v4l2_ctrl_handler_free() on the ctx->ctrls allocation failure path. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1.1. An x86_64 allyesconfig build showed no new warnings. As we do not have an Allwinner SoC or board with a Cedrus VPU available to test with, no runtime testing was able to be performed.

Gravité et risque d'exploitation

CVE-2026-89896 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 10.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 5.15.221, 4.20, <79fd0b0161506fc9507bf7a6fe4c975a857a5be8, 50e761516f2b8c0cdeb31a8c6ca1b4ef98cd13f1, 5.10.270, 0, <729a1ffab968b3c493f61d1cd683f5bafec500ea, 6.1.188, 6.18.51, <9df2fbe563194da1967a5db083442186c1323efe, <4.20, <=5.10.*, <=6.6.*, <81aa608ac3a56cdd4aab0bd12442ed529a24ba31, 7.2.5, 6.6.157, <6fabacc3b79a528450aef4c32464da2ec681049e, <ce5693b6e3a693fcdc3800af309363f6250104c8, <=6.18.*, <22441be29ec27c693f40c1ef499093275ef529d1, 6.12.110, <=7.2.*, <=*, <=5.15.*, <f78cf36cabf911da348ea80e4e9f430d74f6905c, 7.3) 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