https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 17:15:29 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/euvd-2026-311205 EUVD-2026-311205 https://cve.radiocsirt.org/vuln/euvd-2026-311205 https://cve.radiocsirt.org/vuln/fkie_cve-2022-50398 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm/dp: add atomic_check to bridge ops</p> <p>DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc-&gt;active is set before pushing a new frame downstream.</p> <p>There is a rare case that user space display manager issue an extra screen update immediately followed by close DRM device while down stream display interface is disabled. This extra screen update will timeout due to the downstream interface is disabled but will cause crtc-&gt;active be set. Hence the followed commit_tails() called by drm_release() will pass the disable downstream crtc/encoder/bridge conditions checking even downstream interface is disabled. This cause the crash to happen at dp_bridge_disable() due to it trying to access the main link register to push the idle pattern out while main link clocks is disabled.</p> <p>This patch adds atomic_check to prevent the extra frame will not be pushed down if display interface is down so that crtc-&gt;active will not be set neither. This will fail the conditions checking of disabling down stream crtc/encoder/bridge which prevent drm_release() from calling dp_bridge_disable() so that crash at dp_bridge_disable() prevented.</p> <p>There is no protection in the DRM framework to check if the display pipeline has been already disabled before trying again. The only check is the crtc_state-&gt;active but this is controlled by usermode using UAPI. Hence if the usermode sets this and…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm/dp: add atomic_check to bridge ops</p> <p>DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc-&gt;active is set before pushing a new frame downstream.</p> <p>There is a rare case that user space display manager issue an extra screen update immediately followed by close DRM device while down stream display interface is disabled. This extra screen update will timeout due to the downstream interface is disabled but will cause crtc-&gt;active be set. Hence the followed commit_tails() called by drm_release() will pass the disable downstream crtc/encoder/bridge conditions checking even downstream interface is disabled. This cause the crash to happen at dp_bridge_disable() due to it trying to access the main link register to push the idle pattern out while main link clocks is disabled.</p> <p>This patch adds atomic_check to prevent the extra frame will not be pushed down if display interface is down so that crtc-&gt;active will not be set neither. This will fail the conditions checking of disabling down stream crtc/encoder/bridge which prevent drm_release() from calling dp_bridge_disable() so that crash at dp_bridge_disable() prevented.</p> <p>There is no protection in the DRM framework to check if the display pipeline has been already disabled before trying again. The only check is the crtc_state-&gt;active but this is controlled by usermode using UAPI. Hence if the usermode sets this and…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-50398 https://cve.radiocsirt.org/vuln/ghsa-4xpg-w2c7-9vgm <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm/dp: add atomic_check to bridge ops</p> <p>DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc-&gt;active is set before pushing a new frame downstream.</p> <p>There is a rare case that user space display manager issue an extra screen update immediately followed by close DRM device while down stream display interface is disabled. This extra screen update will timeout due to the downstream interface is disabled but will cause crtc-&gt;active be set. Hence the followed commit_tails() called by drm_release() will pass the disable downstream crtc/encoder/bridge conditions checking even downstream interface is disabled. This cause the crash to happen at dp_bridge_disable() due to it trying to access the main link register to push the idle pattern out while main link clocks is disabled.</p> <p>This patch adds atomic_check to prevent the extra frame will not be pushed down if display interface is down so that crtc-&gt;active will not be set neither. This will fail the conditions checking of disabling down stream crtc/encoder/bridge which prevent drm_release() from calling dp_bridge_disable() so that crash at dp_bridge_disable() prevented.</p> <p>There is no protection in the DRM framework to check if the display pipeline has been already disabled before trying again. The only check is the crtc_state-&gt;active but this is controlled by usermode using UAPI. Hence if the usermode sets this and…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm/dp: add atomic_check to bridge ops</p> <p>DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc-&gt;active is set before pushing a new frame downstream.</p> <p>There is a rare case that user space display manager issue an extra screen update immediately followed by close DRM device while down stream display interface is disabled. This extra screen update will timeout due to the downstream interface is disabled but will cause crtc-&gt;active be set. Hence the followed commit_tails() called by drm_release() will pass the disable downstream crtc/encoder/bridge conditions checking even downstream interface is disabled. This cause the crash to happen at dp_bridge_disable() due to it trying to access the main link register to push the idle pattern out while main link clocks is disabled.</p> <p>This patch adds atomic_check to prevent the extra frame will not be pushed down if display interface is down so that crtc-&gt;active will not be set neither. This will fail the conditions checking of disabling down stream crtc/encoder/bridge which prevent drm_release() from calling dp_bridge_disable() so that crash at dp_bridge_disable() prevented.</p> <p>There is no protection in the DRM framework to check if the display pipeline has been already disabled before trying again. The only check is the crtc_state-&gt;active but this is controlled by usermode using UAPI. Hence if the usermode sets this and…</p> https://cve.radiocsirt.org/vuln/ghsa-4xpg-w2c7-9vgm https://cve.radiocsirt.org/vuln/suse-su-2025:03615-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:03615-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50398 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: add atomic_check to bridge ops DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc-&gt;active is set before pushing a new frame downstream. There is a rare case that user space display manager issue an extra screen update immediately followed by close DRM device while down stream display interface is disabled. This extra screen update will timeout due to the downstream interface is disabled but will cause crtc-&gt;active be set. Hence the followed commit_tails() called by drm_release() will pass the disable downstream crtc/encoder/bridge conditions checking even downstream interface is disabled. This cause the crash to happen at dp_bridge_disable() due to it trying to access the main link register to push the idle pattern out while main link clocks is disabled. This patch adds atomic_check to prevent the extra frame will not be pushed down if display interface is down so that crtc-&gt;active will not be set neither. This will fail the conditions checking of disabling down stream crtc/encoder/bridge which prevent drm_release() from calling dp_bridge_disable() so that crash at dp_bridge_disable() prevented. There is no protection in the DRM framework to check if the display pipeline has been already disabled before trying again. The only check is the crtc_state-&gt;active but this is controlled by usermode using UAPI. Hence if the usermode sets this and then…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: add atomic_check to bridge ops DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc-&gt;active is set before pushing a new frame downstream. There is a rare case that user space display manager issue an extra screen update immediately followed by close DRM device while down stream display interface is disabled. This extra screen update will timeout due to the downstream interface is disabled but will cause crtc-&gt;active be set. Hence the followed commit_tails() called by drm_release() will pass the disable downstream crtc/encoder/bridge conditions checking even downstream interface is disabled. This cause the crash to happen at dp_bridge_disable() due to it trying to access the main link register to push the idle pattern out while main link clocks is disabled. This patch adds atomic_check to prevent the extra frame will not be pushed down if display interface is down so that crtc-&gt;active will not be set neither. This will fail the conditions checking of disabling down stream crtc/encoder/bridge which prevent drm_release() from calling dp_bridge_disable() so that crash at dp_bridge_disable() prevented. There is no protection in the DRM framework to check if the display pipeline has been already disabled before trying again. The only check is the crtc_state-&gt;active but this is controlled by usermode using UAPI. Hence if the usermode sets this and then…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50398 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092