CVE-2026-74438

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 0, <306ded31bfa00a69d25823a60d7c797170bfb4f8, <e4b7b9819811c4c51064c3d3d3c02f0be7491707, <=7.1.*, <ee2458f8188732aa53a5d42f56e87bfad288b44e, b8ae5c7387ad075ee61e8c8774ce2bca46bc9236, 6.1.178, 6.12.97, <=6.6.*, <2eafecaba1b46bb9774eaf3556619fd5b6a17c1c, <=6.18.*, 5.15.212, 6.6.145, <b2c41fa9dd8fc740c489e060b199165771f268d1, <9c8086d9511189c34dfa3f9e3a03f2bee12f56a5, <=*, <4.14, <=5.15.*, <c401492e01c7bfd38cf14c94d85c7efafe7d1a25, 7.2, 4.14

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: sun4i-ss - Remove insecure and unused rng_alg Remove sun4i_ss_rng, as it is insecure and unused: - It has multiple vulnerabilities. sun4i_ss_prng_seed() is missing locking and has a buffer overflow. sun4i_ss_prng_generate() fails to fill the entire buffer with cryptographic random bytes, because it rounds the destination length down and also doesn't actually wait for the hardware to be ready before pulling bytes from it. - No user of this code is known. It's usable only theoretically via the "rng" algorithm type of AF_ALG. But userspace actually just uses the actual Linux RNG (/dev/random etc) instead. And rng_algs don't contribute entropy to the actual Linux RNG either. (This may have been confused with hwrng, which does contribute entropy.) The sun4i_ss_prng_seed() buffer overflow was reported by Tianchu Chen and discovered by Atuin - Automated Vulnerability Discovery Engine There's no point in fixing all these vulnerabilities individually when this is unused code, so let's just remove it.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 0, <306ded31bfa00a69d25823a60d7c797170bfb4f8, <e4b7b9819811c4c51064c3d3d3c02f0be7491707, <=7.1.*, <ee2458f8188732aa53a5d42f56e87bfad288b44e, b8ae5c7387ad075ee61e8c8774ce2bca46bc9236, 6.1.178, 6.12.97, <=6.6.*, <2eafecaba1b46bb9774eaf3556619fd5b6a17c1c, <=6.18.*, 5.15.212, 6.6.145, <b2c41fa9dd8fc740c489e060b199165771f268d1, <9c8086d9511189c34dfa3f9e3a03f2bee12f56a5, <=*, <4.14, <=5.15.*, <c401492e01c7bfd38cf14c94d85c7efafe7d1a25, 7.2, 4.14) 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