CVE-2026-45876

NONECVSS 0.0

0.0

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

arm64/gcs: Fix error handling in arch_set_shadow_stack_status()

alloc_gcs() returns an error-encoded pointer on failure, which comes from do_mmap(), not NULL.

The current NULL check fails to detect errors, which could lead to using an invalid GCS address.

Use IS_ERR_VALUE() to properly detect errors, consistent with the check in gcs_alloc_thread_stack().

CVSS v3: —
EG Score: 0.0(none)
EPSS: 4.3%
KEV: Not listed

Published

May 27, 2026

Last Modified

May 27, 2026

References (3)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/53c998527ffa60f9deda8974a11ad39790684159
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a4741114c9622346c4bbb8cc2bbd88153616ffaf
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c787a235deb33be6eda40beee8f561da5fd8cb8c

Vendor Advisories for CVE-2026-45876(1)

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

GHSA-c8fp-ff95-66mv
GitHub Security Advisoriesunknown
In the Linux kernel, the following vulnerability has been resolved: arm64/gcs: Fix error...

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-27 14:19 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-45876?

CVE-2026-45876 is a none vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: arm64/gcs: Fix error handling in archsetshadowstackstatus() alloc_gcs() returns an error-encoded pointer on failure, which comes from do_mmap(), not NULL. The current NULL check fails to detect errors, which could lead to using an…

When was CVE-2026-45876 disclosed?

CVE-2026-45876 was first published in the National Vulnerability Database on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-45876 actively exploited?

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

How do I remediate CVE-2026-45876?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45876, 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-45876

Explore →

Is Your Infrastructure Affected by CVE-2026-45876?

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

Start Free Scan →Browse All CVEs

CVE-2026-45876

📅 Published

🔄 Last Modified

🔗 References (3)

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