CVE-2025-38467：drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling · Pull Request !17583 · openEuler/kernel

fix CVE CVE-2025-38467
issue link: https://gitee.com/src-openeuler/kernel/issues/ICOXOO

commit 14ac8fcb33068f4ffe8fbec56b9e1f2a798910ab (HEAD -> CVE-2025-38467, origin/CVE-2025-38467)
Author: Kaustabh Chakraborty <kauschluss@disroot.org>
Date:   Fri Jun 27 00:50:30 2025 +0530

drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling

stable inclusion
    from stable-v6.6.99
    commit 391e5ea5b877230b844c9bd8bbcd91b681b1ce2d
    category: bugfix
    bugzilla: https://gitee.com/src-openeuler/kernel/issues/ICOXOO
    CVE: CVE-2025-38467

Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/patch/?id=391e5ea5b877230b844c9bd8bbcd91b681b1ce2d

--------------------------------

commit b846350aa272de99bf6fecfa6b08e64ebfb13173 upstream.

If there's support for another console device (such as a TTY serial),
    the kernel occasionally panics during boot. The panic message and a
    relevant snippet of the call stack is as follows:

Unable to handle kernel NULL pointer dereference at virtual address 000000000000000
      Call trace:
        drm_crtc_handle_vblank+0x10/0x30 (P)
        decon_irq_handler+0x88/0xb4
        [...]

Otherwise, the panics don't happen. This indicates that it's some sort
    of race condition.

Add a check to validate if the drm device can handle vblanks before
    calling drm_crtc_handle_vblank() to avoid this.

Cc: stable@vger.kernel.org
    Fixes: 96976c3d9aff ("drm/exynos: Add DECON driver")
    Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Yu Wu <wuyu06@inspur.com>

GVPopenEuler/kernel

搜索帮助

GVP openEuler/kernel