Heimdall Security Logo

CVE-2026-43421

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 6.12.78, 3.11, <93f116c3393a22acab96ad1bef12b2572eb80ca4, <3.11, 0, 7.0, <85acaba2f42b557499bab3608307f17bf13beb69, 6.1.176, 6.18.19, <=6.6.*, <ec35c1969650e7cb6c8a91020e568ed46e3551b0, <=6.19.*, <36c41e9724c9a7a7cda37f5a4e9d94f25c8031c4, 6.19.9, <=6.18.*, <7c97366f5dac5255e60a317ffe3a5b18f3745547, <=*, 6.6.143, 40d133d7f542616cf9538508a372306e626a16e9, <e584cb58a2ea7ff4d3a4bc43d5ca512ed3ecb77d

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix net_device lifecycle with device_move The network device outlived its parent gadget device during disconnection, resulting in dangling sysfs links and null pointer dereference problems. A prior attempt to solve this by removing SET_NETDEV_DEV entirely [1] was reverted due to power management ordering concerns and a NO-CARRIER regression. A subsequent attempt to defer net_device allocation to bind [2] broke 1:1 mapping between function instance and network device, making it impossible for configfs to report the resolved interface name. This results in a regression where the DHCP server fails on pmOS. Use device_move to reparent the net_device between the gadget device and /sys/devices/virtual/ across bind/unbind cycles. This preserves the network interface across USB reconnection, allowing the DHCP server to retain their binding. Introduce gether_attach_gadget()/gether_detach_gadget() helpers and use __free(detach_gadget) macro to undo attachment on bind failure. The bind_count ensures device_move executes only on the first bind. [1] https://lore.kernel.org/lkml/f2a4f9847617a0929d62025748384092e5f35cce.camel@crapouillou.net/ [2] https://lore.kernel.org/linux-usb/795ea759-7eaf-4f78-81f4-01ffbf2d7961@ixit.cz/

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.12.78, 3.11, <93f116c3393a22acab96ad1bef12b2572eb80ca4, <3.11, 0, 7.0, <85acaba2f42b557499bab3608307f17bf13beb69, 6.1.176, 6.18.19, <=6.6.*, <ec35c1969650e7cb6c8a91020e568ed46e3551b0, <=6.19.*, <36c41e9724c9a7a7cda37f5a4e9d94f25c8031c4, 6.19.9, <=6.18.*, <7c97366f5dac5255e60a317ffe3a5b18f3745547, <=*, 6.6.143, 40d133d7f542616cf9538508a372306e626a16e9, <e584cb58a2ea7ff4d3a4bc43d5ca512ed3ecb77d) 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