5.8

CVE-2022-50675: arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored

Deferred
AliasesUBUNTU-CVE-2022-50675DEBIAN-CVE-2022-50675
Published 09-12-2025Last modified 11-05-2026

Vulnerability summary

CVE-2022-50675 is a medium (CVSS 5.8) vulnerability in linux. EPSS estimates a 0.24% chance of exploitation in the next 30 days, higher than 15.3% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.8, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.8/10
010
Medium · v4.0 (OSV · Ubuntu), selected by version preference
EPSS score
0.24%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 5 · Related 4

Timeline

  1. 09-12-2025
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

Description

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. However, the side-effect was that any page with a PTE that looked like swap (or migration) was getting PG_mte_tagged set automatically. A subsequent page copy (e.g. migration) copied the tags to the destination page even if the tags were owned by KASAN. This issue was masked by the page_kasan_tag_reset() call introduced in commit e5b8d9218951 ("arm64: mte: reset the page tag in page->flags"). When this commit was reverted (20794545c146), KASAN started reporting access faults because the overriding tags in a page did not match the original page->flags (with CONFIG_KASAN_HW_TAGS=y): BUG: KASAN: invalid-access in copy_page+0x10/0xd0 arch/arm64/lib/copy_page.S:26 Read at addr f5ff000017f2e000 by task syz-executor.1/2218 Pointer tag: [f5], memory tag: [f2] Move the PG_mte_tagged bit setting from mte_sync_tags() to the actual place where tags are cleared (mte_sync_page_tags()) or restored (mte_restore_tags()).

CVSS metrics

1 score · 1 source · 1 version

EPSS trend

Probability

0.24%

Chance of exploitation in the next 30 days

Percentile

15%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.24% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu104 products
  • linux< 5.15.0-67.74
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 5.15.0-1031.35
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian1 product
  • linux< 6.0.3-1
Linux1 product
  • linux≥ 69e3b846d8a753f9f279f29531ca56b0f7563ad0, < 918002bdbe4328c8c0164a22e8ebf2384b80dc23 | ≥ 69e3b846d8a753f9f279f29531ca56b0f7563ad0, < 749e9fc18b1e1a3f93a9512e91bd7f93002d2821 | ≥ 69e3b846d8a753f9f279f29531ca56b0f7563ad0, < a8e5e5146ad08d794c58252bab00b261045ef16d | 5.14

3 vendors · 106 products

References

7 links