# drm/amd/display: check if ext_caps is valid in BL setup

CVE record · `CVE-2026-31460`

- **Identifiers:** `CVE-2026-31460`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 22 Apr 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 22 Apr 2026, 13:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `1454642960b0a4fafd48b08919d39350ee2ac372 to before 60b0524bfb7d691ab378cdc788209f11cd34da89` (git)
  - affected: `1454642960b0a4fafd48b08919d39350ee2ac372 to before 9da4f9964abcaeb6e19797d5e3b10faad338a786` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `6.19.11 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel 6.19 is affected in the drm/amd/display backlight setup code, which used a pointer to extended backlight caps without checking it first, even though LVDS connectors do not have those caps. The source gives few details on how an attacker could reach this or what the impact is. Upgrade to Linux kernel 6.19.11 or later in the 6.19 series, or to 7.0 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 22 Apr 2026, 13:53 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-31460)
- 22 Apr 2026, 14:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31460)

## Sources

- [CVE List: CVE-2026-31460](https://www.cve.org/CVERecord?id=CVE-2026-31460)
- [NVD: CVE-2026-31460](https://nvd.nist.gov/vuln/detail/CVE-2026-31460)

### References from the CNA

- <https://git.kernel.org/stable/c/60b0524bfb7d691ab378cdc788209f11cd34da89>
- <https://git.kernel.org/stable/c/9da4f9964abcaeb6e19797d5e3b10faad338a786>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-31460>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-31460/>. Everything for agents: <https://agentprime.io/llms.txt>.
