Heimdall Security Logo

CVE-2023-54232

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 4.19.280, <df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8, <54fa25ffab2b700df5abd58c136d64a912c53953, 2.6.18, 0, <1a6059f5ed57f48edfe7159404ff7d538d9d405b, 5.10.177, <8bf8d5dade4c5e1d8a2386f29253ed28b5d87735, <2.6.18, <=5.10.*, <=4.14.*, 6.3, <ec15405b80fc15ffc87a23d01378ae061c1aba07, <=5.4.*, 6.2.9, <e36a82bebbf7da814530d5a179bef9df5934b717, <=4.19.*, f2325ecebc5b7988fd49968bd3a660fd1594dc84, 4.14.312, <=6.2.*, 6.1.22, 5.15.105, 5.4.240, <=*, <=5.15.*, <2100e374251a8fc00cce1916cfc50f3cb652cbe3, <f55cb52ec98b22125f5bda36391edb8894f7e8cf

Description

In the Linux kernel, the following vulnerability has been resolved: m68k: Only force 030 bus error if PC not in exception table __get_kernel_nofault() does copy data in supervisor mode when forcing a task backtrace log through /proc/sysrq_trigger. This is expected cause a bus error exception on e.g. NULL pointer dereferencing when logging a kernel task has no workqueue associated. This bus error ought to be ignored. Our 030 bus error handler is ill equipped to deal with this: Whenever ssw indicates a kernel mode access on a data fault, we don't even attempt to handle the fault and instead always send a SEGV signal (or panic). As a result, the check for exception handling at the fault PC (buried in send_sig_fault() which gets called from do_page_fault() eventually) is never used. In contrast, both 040 and 060 access error handlers do not care whether a fault happened on supervisor mode access, and will call do_page_fault() on those, ultimately honoring the exception table. Add a check in bus_error030 to call do_page_fault() in case we do have an entry for the fault PC in our exception table. I had attempted a fix for this earlier in 2019 that did rely on testing pagefault_disabled() (see link below) to achieve the same thing, but this patch should be more generic. Tested on 030 Atari Falcon.

Gravité et risque d'exploitation

CVE-2023-54232 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.21 %, ce qui la place devant 10.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 4.19.280, <df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8, <54fa25ffab2b700df5abd58c136d64a912c53953, 2.6.18, 0, <1a6059f5ed57f48edfe7159404ff7d538d9d405b, 5.10.177, <8bf8d5dade4c5e1d8a2386f29253ed28b5d87735, <2.6.18, <=5.10.*, <=4.14.*, 6.3, <ec15405b80fc15ffc87a23d01378ae061c1aba07, <=5.4.*, 6.2.9, <e36a82bebbf7da814530d5a179bef9df5934b717, <=4.19.*, f2325ecebc5b7988fd49968bd3a660fd1594dc84, 4.14.312, <=6.2.*, 6.1.22, 5.15.105, 5.4.240, <=*, <=5.15.*, <2100e374251a8fc00cce1916cfc50f3cb652cbe3, <f55cb52ec98b22125f5bda36391edb8894f7e8cf) 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