Heimdall Security Logo

CVE-2023-52989

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, 5.10.168, 6.1.11, 0, 5.4.232, 4.19.273, <531390a243ef47448f8bad01c186c2787666bf4d, <=5.10.*, <=4.14.*, 5.15.93, <2.6.33, <=5.4.*, <356ff89acdbe6a66019154bc7eb2d300f5b15103, <d5a2dcee53fa6e6e2822f93cb3f1b0cd23163bee, <53785fd9b315583cf029e39f72b73d23704a2253, 2.6.33, <=4.19.*, 4.14.306, <5f4543c9382ae2d5062f6aa4fecae0c9258d0b0e, 281e20323ab72180137824a298ee9e21e6f9acf6, <b2cd3947d116bb9ba7ff097b5fc747a8956764db, <=*, <=5.15.*, <c8bdc88216f09cb7387fedbdf613524367328616, 6.2

Description

In the Linux kernel, the following vulnerability has been resolved: firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region This patch is fix for Linux kernel v2.6.33 or later. For request subaction to IEC 61883-1 FCP region, Linux FireWire subsystem have had an issue of use-after-free. The subsystem allows multiple user space listeners to the region, while data of the payload was likely released before the listeners execute read(2) to access to it for copying to user space. The issue was fixed by a commit 281e20323ab7 ("firewire: core: fix use-after-free regression in FCP handler"). The object of payload is duplicated in kernel space for each listener. When the listener executes ioctl(2) with FW_CDEV_IOC_SEND_RESPONSE request, the object is going to be released. However, it causes memory leak since the commit relies on call of release_request() in drivers/firewire/core-cdev.c. Against the expectation, the function is never called due to the design of release_client_resource(). The function delegates release task to caller when called with non-NULL fourth argument. The implementation of ioctl_send_response() is the case. It should release the object explicitly. This commit fixes the bug.

Gravité et risque d'exploitation

CVE-2023-52989 obtient un score CVSS de 5.5/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.26 %, ce qui la place devant 16.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 5.10.168, 6.1.11, 0, 5.4.232, 4.19.273, <531390a243ef47448f8bad01c186c2787666bf4d, <=5.10.*, <=4.14.*, 5.15.93, <2.6.33, <=5.4.*, <356ff89acdbe6a66019154bc7eb2d300f5b15103, <d5a2dcee53fa6e6e2822f93cb3f1b0cd23163bee, <53785fd9b315583cf029e39f72b73d23704a2253, 2.6.33, <=4.19.*, 4.14.306, <5f4543c9382ae2d5062f6aa4fecae0c9258d0b0e, 281e20323ab72180137824a298ee9e21e6f9acf6, <b2cd3947d116bb9ba7ff097b5fc747a8956764db, <=*, <=5.15.*, <c8bdc88216f09cb7387fedbdf613524367328616, 6.2) 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