CVE-2026-23410

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 0, 7.0, <6ef1f2926c41ab96952d9696d55a052f1b3a9418, <6b6ba87579c7e7c669e0bec91823e7fb693bc5df, <=5.10.*, <=6.6.*, <d9d8560b9b7932f8cffc4c068c14289220900f79, <=6.19.*, 6.1.169, 4.13, 5.15.203, 6.18.18, <a0b7091c4de45a7325c8780e6934a894f92ac86b, <=6.18.*, <f9761add6d100962a23996cb68f3d6abdd4d1815, <763e838adc3c7ec5a7df2990ce84cad951e42721, <4.13, <af782cc8871e3683ddd5a3cd2f7df526599863a9, <=*, 5.10.253, <=5.15.*, 6.12.77, 6.19.8, 6.6.130, <3b8e77c7abab40e6de9ad9de730d77984a498840, 5d5182cae40115c03933989473288e54afb39c7c

Description

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix race on rawdata dereference There is a race condition that leads to a use-after-free situation: because the rawdata inodes are not refcounted, an attacker can start open()ing one of the rawdata files, and at the same time remove the last reference to this rawdata (by removing the corresponding profile, for example), which frees its struct aa_loaddata; as a result, when seq_rawdata_open() is reached, i_private is a dangling pointer and freed memory is accessed. The rawdata inodes weren't refcounted to avoid a circular refcount and were supposed to be held by the profile rawdata reference. However during profile removal there is a window where the vfs and profile destruction race, resulting in the use after free. Fix this by moving to a double refcount scheme. Where the profile refcount on rawdata is used to break the circular dependency. Allowing for freeing of the rawdata once all inode references to the rawdata are put.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 0, 7.0, <6ef1f2926c41ab96952d9696d55a052f1b3a9418, <6b6ba87579c7e7c669e0bec91823e7fb693bc5df, <=5.10.*, <=6.6.*, <d9d8560b9b7932f8cffc4c068c14289220900f79, <=6.19.*, 6.1.169, 4.13, 5.15.203, 6.18.18, <a0b7091c4de45a7325c8780e6934a894f92ac86b, <=6.18.*, <f9761add6d100962a23996cb68f3d6abdd4d1815, <763e838adc3c7ec5a7df2990ce84cad951e42721, <4.13, <af782cc8871e3683ddd5a3cd2f7df526599863a9, <=*, 5.10.253, <=5.15.*, 6.12.77, 6.19.8, 6.6.130, <3b8e77c7abab40e6de9ad9de730d77984a498840, 5d5182cae40115c03933989473288e54afb39c7c) 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