CVE-2026-72313
In the Linux kernel, the following vulnerability has been resolved:
drm/fb-helper: Only consider active CRTCs for vblank sync
Only synchronize fbdev output to the vblank of an active CRTC. Go over the list of CRTCs and pick the first that matches. Fixes warnings as the one shown below
This currently happens if the fbdev output is not on CRTC 0.
Atomic and non-atomic drivers require distinct code paths. As for other fbdev operations, implement both and select the correct one at runtime.
Not finding an active CRTC is not a bug. Do not wait in this case, but flush the display update as before.
v4: - avoid possible deadlocks with locking context (Sashiko) v3: - drop excessive state validation (Jani) - acquire plane and CRTC mutices (Sashiko) v2: - move look-up code into separate helper - support drivers with legacy modesetting v1: - see https://lore.kernel.org/dri-devel/1c9e0e24-9c4a-4259-8700-cf9e5fd60ca3@suse.de/
Detalles técnicos trazas, registros y código del informe original
[ 77.201354] WARNING: drivers/gpu/drm/drm_vblank.c:1320 at drm_crtc_wait_one_vblank+0x194/0x1cc [drm], CPU#1: kworker/1:7/1867 [ 77.201354] omapdrm omapdrm.0: [drm] vblank wait timed out on crtc 0
CVSS
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.20%
- Percentil entre todas las CVEs puntuadas: 9
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-72313",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "d8c4bddcd8bcb41885d3db2ba18c840c411564c2",
"lessThan": "7d84acf641afb68aa8efe40815ef43779ddb12fd",
"versionType": "git"
},
{
"status": "affected",
"version": "d8c4bddcd8bcb41885d3db2ba18c840c411564c2",
"lessThan": "06c2b8d7ea2bcb014dd974fc3bc6d128d65d7477",
"versionType": "git"
}
],
"programFiles": [
"drivers/gpu/drm/drm_fb_helper.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.19",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver",
"lessThanOrEqual": "7.1.*"
},
{
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/gpu/drm/drm_fb_helper.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-08-15T06:22:04.123",
"references": [
{
"url": "https://git.kernel.org/stable/c/06c2b8d7ea2bcb014dd974fc3bc6d128d65d7477",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7d84acf641afb68aa8efe40815ef43779ddb12fd",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/fb-helper: Only consider active CRTCs for vblank sync\n\nOnly synchronize fbdev output to the vblank of an active CRTC. Go over\nthe list of CRTCs and pick the first that matches. Fixes warnings as\nthe one shown below\n\n[ 77.201354] WARNING: drivers/gpu/drm/drm_vblank.c:1320 at drm_crtc_wait_one_vblank+0x194/0x1cc [drm], CPU#1: kworker/1:7/1867\n[ 77.201354] omapdrm omapdrm.0: [drm] vblank wait timed out on crtc 0\n\nThis currently happens if the fbdev output is not on CRTC 0.\n\nAtomic and non-atomic drivers require distinct code paths. As for other\nfbdev operations, implement both and select the correct one at runtime.\n\nNot finding an active CRTC is not a bug. Do not wait in this case, but\nflush the display update as before.\n\nv4:\n- avoid possible deadlocks with locking context (Sashiko)\nv3:\n- drop excessive state validation (Jani)\n- acquire plane and CRTC mutices (Sashiko)\nv2:\n- move look-up code into separate helper\n- support drivers with legacy modesetting\nv1:\n- see https://lore.kernel.org/dri-devel/1c9e0e24-9c4a-4259-8700-cf9e5fd60ca3@suse.de/"
}
],
"lastModified": "2026-08-17T06:18:34.437",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}