Heimdall Security Logo

CVE-2024-41042

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

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, 6.10, <3.13, 20a69341f2d00cd042e81c82289fba8a13c05a25, <cff3bd012a9512ac5ed858d38e6ed65f6391008c, 5.15.165, 0, <1947e4c3346faa8ac7e343652c0fd3b3e394202f, <=5.10.*, <8246b7466c8da49d0d9e85e26cbd69dd6d3e3d1e, <=6.6.*, <=6.9.*, <b6b6e430470e1c3c5513311cb35a15a205595abe, <9df785aeb7dcc8efd1d4110bb27d26005298ebae, <717c91c6ed73e248de6a15bc53adefb81446c9d0, 5.4.282, 6.9.10, <=5.4.*, <cd4348e0a50286282c314ad6d2b0740e7c812c24, <=4.19.*, 3.13, <31c35f9f89ef585f1edb53e17ac73a0ca4a9712b, 5.10.224, 6.1.105, <=*, 4.19.320, <=5.15.*, 6.6.46

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).

Gravité et risque d'exploitation

CVE-2024-41042 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.32 %, ce qui la place devant 23.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 6.10, <3.13, 20a69341f2d00cd042e81c82289fba8a13c05a25, <cff3bd012a9512ac5ed858d38e6ed65f6391008c, 5.15.165, 0, <1947e4c3346faa8ac7e343652c0fd3b3e394202f, <=5.10.*, <8246b7466c8da49d0d9e85e26cbd69dd6d3e3d1e, <=6.6.*, <=6.9.*, <b6b6e430470e1c3c5513311cb35a15a205595abe, <9df785aeb7dcc8efd1d4110bb27d26005298ebae, <717c91c6ed73e248de6a15bc53adefb81446c9d0, 5.4.282, 6.9.10, <=5.4.*, <cd4348e0a50286282c314ad6d2b0740e7c812c24, <=4.19.*, 3.13, <31c35f9f89ef585f1edb53e17ac73a0ca4a9712b, 5.10.224, 6.1.105, <=*, 4.19.320, <=5.15.*, 6.6.46) 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