# drm/bridge: megachips: Fix a null pointer dereference bug

CVE record · `CVE-2022-50317`

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

Published by the CVE Program (CNA: Linux) at 15 Sept 2025, 14:48 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: `7649972d97fb98578fbc4a351416cf72895e7c4d to before aaa512ad1e59f2edf8a9e4f2b167a44b24670679` (git)
  - affected: `16e3827904932eccfba0915f0c93b519de3536ac to before 5bc20bafcd87ba0858ab772cefc7047cb51bc249` (git)
  - affected: `50ad94f8654a53ec9ca3604a7a23cbaf166e0119 to before 1daf69228e310938177119c4eadcd30fc75c81e0` (git)
  - affected: `b8d10f601f226f055df8b5368d7ea7f369136cd5 to before 877e92e9b1bdeb580b31a46061005936be902cd4` (git)
  - affected: `405856460d3e7aefb7c1aef047ec88fc4ef2e2a5 to before 4610e7a4111fa3f3ce27c09d6d94008c55f1cd31` (git)
  - affected: `11632d4aa2b3f126790e81a4415d6c23103cf8bb to before 21764467ab396d9f08921e0a5ffa1214244e1ad9` (git)
  - affected: `11632d4aa2b3f126790e81a4415d6c23103cf8bb to before 7371fad5cfe6eada6bb5523c895fd6074b15c2b9` (git)
  - affected: `11632d4aa2b3f126790e81a4415d6c23103cf8bb to before 1ff673333d46d2c1b053ebd0c1c7c7c79e36943e` (git)
  - affected: `e449461989f0674f188d30494ffd3f5ba74c1a05` (git)
  - affected: `4.14.263 to before 4.14.296` (semver)
  - affected: `4.19.226 to before 4.19.262` (semver)
  - affected: `5.4.174 to before 5.4.220` (semver)
  - and 3 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.17`
  - unaffected: `before 5.17` (semver)
  - unaffected: `4.14.296 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.262 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.220 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.150 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.75 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.17 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0.3 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 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.

> The Linux kernel's drm/bridge megachips driver is affected in the 5.17 series and in the commit ranges the CNA listed. Unloading the megachips bridge module can cause a null pointer dereference and a kernel crash, and the source gives no details on attacker access. Upgrade to a fixed kernel, such as 5.10.150 or later on the 5.10 branch, or to the matching stable release for your series. No workaround is listed.

Written 16 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.0017, the 5th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 15 Sept 2025, 14:48 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50317)
- 15 Sept 2025, 15:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50317)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/aaa512ad1e59f2edf8a9e4f2b167a44b24670679>
- <https://git.kernel.org/stable/c/5bc20bafcd87ba0858ab772cefc7047cb51bc249>
- <https://git.kernel.org/stable/c/1daf69228e310938177119c4eadcd30fc75c81e0>
- <https://git.kernel.org/stable/c/877e92e9b1bdeb580b31a46061005936be902cd4>
- <https://git.kernel.org/stable/c/4610e7a4111fa3f3ce27c09d6d94008c55f1cd31>
- <https://git.kernel.org/stable/c/21764467ab396d9f08921e0a5ffa1214244e1ad9>
- <https://git.kernel.org/stable/c/7371fad5cfe6eada6bb5523c895fd6074b15c2b9>
- <https://git.kernel.org/stable/c/1ff673333d46d2c1b053ebd0c1c7c7c79e36943e>

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-2022-50317>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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