CVE-2026-46199

HIGHNVD 7.1

7.1

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg

Check bounds against the end of the BO whenever we access the msg.

CVSS v3: 7.1
EG Score: 0.0(none)
EPSS: 1.8%
KEV: Not listed

Published

May 28, 2026

Last Modified

May 30, 2026

References (5)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/0a78f2bac1424deb7c9d5e09c6b8e849d8e8b648
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/3c817a60b09eaab926e475088e750936efcc95ae
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/63b51e8a9d54317d31cc3856c1e12407070d5fc2
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/7688143ca62edeecacb3ba0a2cea129dbd262a18
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c72a8b4dc6d598e3831ef3abd9c6527dfbf4810e

Vendor Advisories for CVE-2026-46199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

GHSA-v7cw-36xw-548q
GitHub Security AdvisoriesHigh
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn4: Prevent OOB...

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 10:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46199?

CVE-2026-46199 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg Check bounds against the end of the BO whenever we access the msg.

When was CVE-2026-46199 disclosed?

CVE-2026-46199 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on May 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-46199 actively exploited?

CVE-2026-46199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-46199?

CVE-2026-46199 has a CVSS v3 base score of 7.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.

How do I remediate CVE-2026-46199?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46199

Explore →

Is Your Infrastructure Affected by CVE-2026-46199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-46199

📅 Published

🔄 Last Modified

🔗 References (5)

📣 Vendor Advisories for CVE-2026-46199(1)