Heimdall Security Logo

CVE-2022-50731

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

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : <779a9930f3e152c82699feb389a0e6d6644e747e, 78a0324f4a5328088fea9426cfe1d1851276c475, 5.2, 0, 5.4.220, <=5.10.*, <5.2, <=6.0.*, <f9058178597059d6307efe96a7916600f8ede08c, <=5.4.*, <85bc736a18b872f54912e8bb70682d11770aece0, 6.1, 5.19.17, <95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e, <=*, <=5.15.*, 6.0.3, <=5.19.*, 5.15.75, <bc155c6c188c2f0c5749993b1405673d25a80389, <a1354bdd191d533211b7cb723aa76a66f516f197, 5.10.150

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: akcipher - default implementation for setting a private key Changes from v1: * removed the default implementation from set_pub_key: it is assumed that an implementation must always have this callback defined as there are no use case for an algorithm, which doesn't need a public key Many akcipher implementations (like ECDSA) support only signature verifications, so they don't have all callbacks defined. Commit 78a0324f4a53 ("crypto: akcipher - default implementations for request callbacks") introduced default callbacks for sign/verify operations, which just return an error code. However, these are not enough, because before calling sign the caller would likely call set_priv_key first on the instantiated transform (as the in-kernel testmgr does). This function does not have a default stub, so the kernel crashes, when trying to set a private key on an akcipher, which doesn't support signature generation. I've noticed this, when trying to add a KAT vector for ECDSA signature to the testmgr. With this patch the testmgr returns an error in dmesg (as it should) instead of crashing the kernel NULL ptr dereference.

Gravité et risque d'exploitation

CVE-2022-50731 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.25 %, ce qui la place devant 15.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <779a9930f3e152c82699feb389a0e6d6644e747e, 78a0324f4a5328088fea9426cfe1d1851276c475, 5.2, 0, 5.4.220, <=5.10.*, <5.2, <=6.0.*, <f9058178597059d6307efe96a7916600f8ede08c, <=5.4.*, <85bc736a18b872f54912e8bb70682d11770aece0, 6.1, 5.19.17, <95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e, <=*, <=5.15.*, 6.0.3, <=5.19.*, 5.15.75, <bc155c6c188c2f0c5749993b1405673d25a80389, <a1354bdd191d533211b7cb723aa76a66f516f197, 5.10.150) 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