CVE-2026-31571 (GCVE-0-2026-31571)

Vulnerability from cvelistv5 – Published: 2026-04-24 14:35 – Updated: 2026-04-24 14:35
VLAI?
Title
drm/i915: Unlink NV12 planes earlier
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/i915: Unlink NV12 planes earlier unlink_nv12_plane() will clobber parts of the plane state potentially already set up by plane_atomic_check(), so we must make sure not to call the two in the wrong order. The problem happens when a plane previously selected as a Y plane is now configured as a normal plane by user space. plane_atomic_check() will first compute the proper plane state based on the userspace request, and unlink_nv12_plane() later clears some of the state. This used to work on account of unlink_nv12_plane() skipping the state clearing based on the plane visibility. But I removed that check, thinking it was an impossible situation. Now when that situation happens unlink_nv12_plane() will just WARN and proceed to clobber the state. Rather than reverting to the old way of doing things, I think it's more clear if we unlink the NV12 planes before we even compute the new plane state. (cherry picked from commit 017ecd04985573eeeb0745fa2c23896fb22ee0cc)
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 6a01df2f1b2a3b29721143729a3feff816bc0083 , < 70e2eb91cb6310a3508439f6f2539dfffa0abf77 (git)
Affected: 6a01df2f1b2a3b29721143729a3feff816bc0083 , < 12f3b6cbab8fbeb95097685b40f0147406cf9746 (git)
Affected: 6a01df2f1b2a3b29721143729a3feff816bc0083 , < bfa71b7a9dc6b5b8af157686e03308291141d00c (git)
Create a notification for this product.
    Linux Linux Affected: 6.15
Unaffected: 0 , < 6.15 (semver)
Unaffected: 6.18.21 , ≤ 6.18.* (semver)
Unaffected: 6.19.11 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/i915/display/intel_plane.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "70e2eb91cb6310a3508439f6f2539dfffa0abf77",
              "status": "affected",
              "version": "6a01df2f1b2a3b29721143729a3feff816bc0083",
              "versionType": "git"
            },
            {
              "lessThan": "12f3b6cbab8fbeb95097685b40f0147406cf9746",
              "status": "affected",
              "version": "6a01df2f1b2a3b29721143729a3feff816bc0083",
              "versionType": "git"
            },
            {
              "lessThan": "bfa71b7a9dc6b5b8af157686e03308291141d00c",
              "status": "affected",
              "version": "6a01df2f1b2a3b29721143729a3feff816bc0083",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/i915/display/intel_plane.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.15"
            },
            {
              "lessThan": "6.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.21",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.21",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.11",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915: Unlink NV12 planes earlier\n\nunlink_nv12_plane() will clobber parts of the plane state\npotentially already set up by plane_atomic_check(), so we\nmust make sure not to call the two in the wrong order.\nThe problem happens when a plane previously selected as\na Y plane is now configured as a normal plane by user space.\nplane_atomic_check() will first compute the proper plane\nstate based on the userspace request, and unlink_nv12_plane()\nlater clears some of the state.\n\nThis used to work on account of unlink_nv12_plane() skipping\nthe state clearing based on the plane visibility. But I removed\nthat check, thinking it was an impossible situation. Now when\nthat situation happens unlink_nv12_plane() will just WARN\nand proceed to clobber the state.\n\nRather than reverting to the old way of doing things, I think\nit\u0027s more clear if we unlink the NV12 planes before we even\ncompute the new plane state.\n\n(cherry picked from commit 017ecd04985573eeeb0745fa2c23896fb22ee0cc)"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-04-24T14:35:50.094Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/70e2eb91cb6310a3508439f6f2539dfffa0abf77"
        },
        {
          "url": "https://git.kernel.org/stable/c/12f3b6cbab8fbeb95097685b40f0147406cf9746"
        },
        {
          "url": "https://git.kernel.org/stable/c/bfa71b7a9dc6b5b8af157686e03308291141d00c"
        }
      ],
      "title": "drm/i915: Unlink NV12 planes earlier",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-31571",
    "datePublished": "2026-04-24T14:35:50.094Z",
    "dateReserved": "2026-03-09T15:48:24.117Z",
    "dateUpdated": "2026-04-24T14:35:50.094Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-31571",
      "date": "2026-04-25",
      "epss": "0.00017",
      "percentile": "0.04073"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-31571\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-04-24T15:16:31.653\",\"lastModified\":\"2026-04-24T17:51:40.810\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/i915: Unlink NV12 planes earlier\\n\\nunlink_nv12_plane() will clobber parts of the plane state\\npotentially already set up by plane_atomic_check(), so we\\nmust make sure not to call the two in the wrong order.\\nThe problem happens when a plane previously selected as\\na Y plane is now configured as a normal plane by user space.\\nplane_atomic_check() will first compute the proper plane\\nstate based on the userspace request, and unlink_nv12_plane()\\nlater clears some of the state.\\n\\nThis used to work on account of unlink_nv12_plane() skipping\\nthe state clearing based on the plane visibility. But I removed\\nthat check, thinking it was an impossible situation. Now when\\nthat situation happens unlink_nv12_plane() will just WARN\\nand proceed to clobber the state.\\n\\nRather than reverting to the old way of doing things, I think\\nit\u0027s more clear if we unlink the NV12 planes before we even\\ncompute the new plane state.\\n\\n(cherry picked from commit 017ecd04985573eeeb0745fa2c23896fb22ee0cc)\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/12f3b6cbab8fbeb95097685b40f0147406cf9746\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/70e2eb91cb6310a3508439f6f2539dfffa0abf77\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bfa71b7a9dc6b5b8af157686e03308291141d00c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.