Heimdall Security Logo

CVE-2026-80834

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 5eb7e946888493959b1c393144934afcbcd0cfc1, <011556f71d094da61379ae3672692cae2795304e, 0, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <ce641e75e0fc912acd4bf661367617561bc7c63f, 6.1.189, <8e4f9110aba3127024646ef7a8999dcfcc03f516, <5.10, <=6.18.*, 5.15.222, <=7.2.*, <7bb9e6060710eb7b59491d9826169190297adace, <b69af40720cabd13da763575022a3d4430b02dfc, <=*, <=5.15.*, <19588f78db582ba4c47b4001bb27f39bb19dc432, <2c8fa2299789282db1aac566a60c2012a5ba8ea8, <1017f987c5f0841f00408a78f947990c9d84b346, 6.18.50, 6.12.109, 5.10, 7.2.3, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: sun8i-ce - Remove crypto_rng interface Since the crypto_rng interface for hardware PRNGs is unused and is redundant with hwrng and the actual Linux RNG, it's being phased out. Most drivers for it were already removed. Go ahead and remove the sun8i-ce support which is one of the only remaining ones. Note that the sun8i-ce support for hwrng remains in place. That is the interface that actually matters. As usual for crypto_rng, this driver was also buggy: its ->generate() function had a use-after-free vulnerability due to using wait_for_completion_interruptible_timeout() without handling shutting down the DMA operation if a signal is sent. There's no point in fixing this separately only to remove the code anyway, so this commit is marked with Fixes and Cc stable.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 5eb7e946888493959b1c393144934afcbcd0cfc1, <011556f71d094da61379ae3672692cae2795304e, 0, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <ce641e75e0fc912acd4bf661367617561bc7c63f, 6.1.189, <8e4f9110aba3127024646ef7a8999dcfcc03f516, <5.10, <=6.18.*, 5.15.222, <=7.2.*, <7bb9e6060710eb7b59491d9826169190297adace, <b69af40720cabd13da763575022a3d4430b02dfc, <=*, <=5.15.*, <19588f78db582ba4c47b4001bb27f39bb19dc432, <2c8fa2299789282db1aac566a60c2012a5ba8ea8, <1017f987c5f0841f00408a78f947990c9d84b346, 6.18.50, 6.12.109, 5.10, 7.2.3, 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

Rechercher une autre CVE