Heimdall Security Logo

CVE-2023-52925

Vulnérabilité moyenne dans Linux (Linux)

CVSS 6.2 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : bd156ce9553dcaf2d6ee2c825d1a5a1718e86524, <156369a702c33ad5434a19c3a689bfb836d4e0b8, 4.19.316, <7845914f45f066497ac75b30c50dbc735e84e884, 59dab3bf0b8fc08eb802721c0532f13dd89209b8, <59ee68c437c562170265194a99698c805a686bb3, 24138933b97b055d486e8064b4a1721702442a9b, <5.5, <af78b0489e8898a8c9449ffc0fdd2e181916f0d4, 1da4874d05da1526b11b82fc7f3c7ac38749ddf8, <4.20, <6.4.12, 6.4.11, 5.4.262, <891ca5dfe3b718b441fc786014a7ba8f517da188, b15ea4017af82011dd55225ce77cce3d4dfc169c, 94313a196b44184b5b52c1876da6a537701b425a, 7c7e658a36f8b1522bd3586d8137e5f93a25ddc5

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: don't fail inserts if duplicate has expired nftables selftests fail: run-tests.sh testcases/sets/0044interval_overlap_0 Expected: 0-2 . 0-3, got: W: [FAILED] ./testcases/sets/0044interval_overlap_0: got 1 Insertion must ignore duplicate but expired entries. Moreover, there is a strange asymmetry in nft_pipapo_activate: It refetches the current element, whereas the other ->activate callbacks (bitmap, hash, rhash, rbtree) use elem->priv. Same for .remove: other set implementations take elem->priv, nft_pipapo_remove fetches elem->priv, then does a relookup, remove this. I suspect this was the reason for the change that prompted the removal of the expired check in pipapo_get() in the first place, but skipping exired elements there makes no sense to me, this helper is used for normal get requests, insertions (duplicate check) and deactivate callback. In first two cases expired elements must be skipped. For ->deactivate(), this gets called for DELSETELEM, so it seems to me that expired elements should be skipped as well, i.e. delete request should fail with -ENOENT error.

Gravité et risque d'exploitation

CVE-2023-52925 obtient un score CVSS de 6.2/10, soit une gravité moyenne. 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.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions bd156ce9553dcaf2d6ee2c825d1a5a1718e86524, <156369a702c33ad5434a19c3a689bfb836d4e0b8, 4.19.316, <7845914f45f066497ac75b30c50dbc735e84e884, 59dab3bf0b8fc08eb802721c0532f13dd89209b8, <59ee68c437c562170265194a99698c805a686bb3, 24138933b97b055d486e8064b4a1721702442a9b, <5.5, <af78b0489e8898a8c9449ffc0fdd2e181916f0d4, 1da4874d05da1526b11b82fc7f3c7ac38749ddf8, <4.20, <6.4.12, 6.4.11, 5.4.262, <891ca5dfe3b718b441fc786014a7ba8f517da188, b15ea4017af82011dd55225ce77cce3d4dfc169c, 94313a196b44184b5b52c1876da6a537701b425a, 7c7e658a36f8b1522bd3586d8137e5f93a25ddc5) 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