MTE tag fault via stale KASAN pointer tag
Published Nov 25, 2024 · Updated May 23, 2026
A KASAN tag-handling flaw in the Linux kernel allows local users to trigger a false MTE tag fault through memory reallocation. The __do_krealloc path zeroes spare memory with memset without first resetting the KASAN pointer tag, so the pointer and allocation tags differ. Exploitation requires an arm64 MTE system with tag-based KASAN; panic-on-warning can crash the kernel, while normal handling disables MTE checking after the first report.
Summary
What happened
A KASAN tag-handling flaw in the Linux kernel allows local users to trigger a false MTE tag fault through memory reallocation. The __do_krealloc path zeroes spare memory with memset without first resetting the KASAN pointer tag, so the pointer and allocation tags differ. Exploitation requires an arm64 MTE system with tag-based KASAN; panic-on-warning can crash the kernel, while normal handling disables MTE checking after the first report.
The record
- CVE
- CVE-2024-53097
- Published
- Nov 25, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 25, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1a83a716ec233990e1fd5b6fbb1200ade63bf450 <704573851b51808b45dae2d62059d1d8189138a2
- Affected versionversion=3e9a65a38706866bf93e19f5b4936465188add10 <3dfb40da84f26dd35dd9bbaf626a2424565b8406
- Affected versionversion=44f79667fefd52945a44d2a57a2cd3c554d7f4e0 <d43f1430d47c22a0727c05b6f156ed25fecdfeb4
- Affected versionversion=5.10.227 <5.10.230
- Affected versionversion=5.15.168 <5.15.173
- Affected versionversion=6.10.14 <6.11
- Affected versionversion=6.1.113 <6.1.118
- Affected versionversion=6.11.3 <6.11.9
- Affected versionversion=6.6.55 <6.6.62
- Affected versionversion=73388659ef0eea51747350530afdeadf8809ce9c
- Affected versionversion=a543785856249a5ba8c20468098601c0c33b1224 <d02492863023431c31f85d570f718433c22b9311
- Affected versionversion=c383263ee82a01a5a9bc1a466025ccde39a38cae <8ebee7565effdeae6085458f8f8463363120a871
- Affected versionversion=e3a9fc1520a6606c6121aca8d6679c6b93de7fd8 <71548fada7ee0eb50cc6ccda82dff010c745f92c
- Affected versionversion=f8767d10bcbc2529540eb906906c0058e15cd918 <486aeb5f1855c75dd810c25036134961bd2a6722
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo