Vulnerability · CVE-2022-50675
In the Linux kernel, the following vulnerability has been resolved: arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored Prior to commit 69e3b846d8a7 ("arm64: mte
Published Dec 9, 2025 · catalog updated May 11, 2026 · Linux Linux
Last checked Nov 1, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2022-50675. EPSS is 0.24%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-99164 · High
- CVE-2026-99158 · Unknown
- CVE-2026-99157 · Unknown
- CVE-2026-99154 · Critical
- CVE-2026-99123 · High
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.24%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux 69e3b846d8a753f9f279f29531ca56b0f7563ad0 <a8e5e5146ad08d794c58252bab00b261045ef16d
In the Linux kernel, the following vulnerability has been resolved: arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored Prior to commit 69e3b846d8a7 ("arm64: mte: Sync tags for pages where PTE is untagged"), mte_sync_tags() was only called for pte_tagged() entries (those mapped with PROT_MTE). Therefore mte_sync_tags() could safely use test_and_set_bit(PG_mte_tagged, &page->flags) without inadvertently setting PG_mte_tagged on an untagged page. The above commit was required as guests may enable MTE without any control at the stage 2 mapping, nor a PROT_MTE mapping in the VMM
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux 69e3b846d8a753f9f279f29531ca56b0f7563ad0 <a8e5e5146ad08d794c58252bab00b261045ef16d69e3b846d8a753f9f279f29531ca56b0f7563ad0 <a8e5e5146ad08d794c58252bab00b261045ef16d
How to fix CVE-2022-50675
Upgrade
CVE-2022-50675 lists a fix boundary at a8e5e5146ad08d794c58252bab00b261045ef16d. Compare the installed build with that boundary before you change production.
Version check
Seen in 69e3b846d8a753f9f279f29531ca56b0f7563ad0 <a8e5e5146ad08d794c58252bab00b261045ef16d
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2022-50675. EPSS is 0.24%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Linux Linux 69e3b846d8a753f9f279f29531ca56b0f7563ad0 <a8e5e5146ad08d794c58252bab00b261045ef16d 69e3b846d8a753f9f279f29531ca56b0f7563ad0 <a8e5e5146ad08d794c58252bab00b261045ef16d. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Dec 9, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored Prior to commit 69e3b846d8a7 ("arm64: mte: Sync tags for pages where PTE is untagged"), mte_sync_tags() was only called for pte_tagged() entries (those mapped with PROT_MTE). Therefore mte_sync_tags() could safely use test_and_set_bit(PG_mte_tagged, &page->flag
May 11, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored Prior to commit 69e3b846d8a7 ("arm64: mte: Sync tags for pages where PTE is untagged"), mte_sync_tags() was only called for pte_tagged() entries (those mapped with PROT_MTE). Therefore mte_sync_tags() could safely use test_and_set_bit(PG_mte_tagged, &page->flag
Sources
- CVE.orgVulnerability recordCVE-2022-50675
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2022-50675
30-day exploitation probability 0.24%
first.org - EUVDVulnerability recordEUVD-2022-55730
In the Linux kernel, the following vulnerability has been resolved: arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored Prior to commit 69e3b846d8a7 ("arm64: mte: Sync tags for pages where PTE is untagged"), mte_sync_tags() was only called for pte_tagged() entr
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 1, 2026
- CVE.orgOct 26, 2026
- EUVDOct 26, 2026