Linux Kernel up to 6.6.18/6.7.6 display infinite loop

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 6.6.18/6.7.6. This affects an unknown part of the component display. This manipulation causes infinite loop. This vulnerability is handled as CVE-2024-26767. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.18/6.7.6. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component display. The manipulation with an unknown input leads to a infinite loop vulnerability. The CWE definition for the vulnerability is CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. As an impact it is known to affect availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fixed integer types and null check locations [why]: issues fixed: - comparison with wider integer type in loop condition which can cause infinite loops - pointer dereference before null check

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2024-26767 since 02/19/2024. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 208720 (SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:3587-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.6.19, 6.7.7 or 6.8 eliminates this vulnerability. Applying the patch 71783d1ff652/beea9ab9080c/0484e05d048b is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (208720) and CERT Bund (WID-SEC-2024-0773). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• IBM InfoSphere Guardium
• Oracle Linux
• NetApp FAS
• EMC Avamar
• Oracle VM
• NetApp AFF
• Dell NetWorker
• IBM Security Guardium
• RESF Rocky Linux
• Open Source Linux Kernel
• SolarWinds Security Event Manager
• Broadcom Brocade SANnav
• IBM Business Automation Workflow
• IBM Spectrum Protect Plus
• IBM QRadar SIEM
• Juniper Junos Space
• IBM DB2
• IBM Storage Scale System

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.6.0
• 6.6.1
• 6.6.2
• 6.6.3
• 6.6.4
• 6.6.5
• 6.6.6
• 6.6.7
• 6.6.8
• 6.6.9
• 6.6.10
• 6.6.11
• 6.6.12
• 6.6.13
• 6.6.14
• 6.6.15
• 6.6.16
• 6.6.17
• 6.6.18
• 6.7.0
• 6.7.1
• 6.7.2
• 6.7.3
• 6.7.4
• 6.7.5
• 6.7.6

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion